| # You don't need Fog in Ruby or some other library to upload to S3 -- shell works perfectly fine | |
| # This is how I upload my new Sol Trader builds (http://soltrader.net) | |
| # Based on a modified script from here: http://tmont.com/blargh/2014/1/uploading-to-s3-in-bash | |
| S3KEY="my aws key" | |
| S3SECRET="my aws secret" # pass these in | |
| function putS3 | |
| { | |
| path=$1 |
| var AWS = require('aws-sdk'), | |
| fs = require('fs'); | |
| // For dev purposes only | |
| AWS.config.update({ accessKeyId: '...', secretAccessKey: '...' }); | |
| // Read in the file, convert it to base64, store to S3 | |
| fs.readFile('del.txt', function (err, data) { | |
| if (err) { throw err; } |
| # Change YOUR_TOKEN to your prerender token | |
| # Change example.com (server_name) to your website url | |
| # Change /path/to/your/root to the correct value | |
| server { | |
| listen 80; | |
| server_name example.com; | |
| root /path/to/your/root; | |
| index index.html; |
| Installing AutoConf and Fixing Phpize on OSX 10.9 |
| // Boring | |
| if (isThisAwesome) { | |
| alert('yes'); // it's not | |
| } | |
| // Awesome | |
| isThisAwesome && alert('yes'); | |
| // Also cool for guarding your code | |
| var aCoolFunction = undefined; |
| /*jslint continue:true*/ | |
| /** | |
| * Adapted from {@link http://www.bulgaria-web-developers.com/projects/javascript/serialize/} | |
| * Changes: | |
| * Ensures proper URL encoding of name as well as value | |
| * Preserves element order | |
| * XHTML and JSLint-friendly | |
| * Disallows disabled form elements and reset buttons as per HTML4 [successful controls]{@link http://www.w3.org/TR/html401/interact/forms.html#h-17.13.2} | |
| * (as used in jQuery). Note: This does not serialize <object> | |
| * elements (even those without a declare attribute) or |
I've done the same process every couple years since 2013 (Mountain Lion, Mavericks, High Sierra, Catalina) and I updated the Gist each time I've done it.
I kinda regret for not using something like Boxen (or anything similar) to automate the process, but TBH I only actually needed to these steps once every couple years...
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
| /*! = $rembase: 14px | |
| -------------------------------------------------------------- | |
| * hmtl { font-size: 87.5%; } | |
| * body { font-size: 14px; font-size: 1rem; line-height: 1; } | |
| * 4px 0.28571429rem | |
| * 8px 0.571428571rem | |
| * 12px 0.857142857rem | |
| * 13px 0.928571429rem | |
| * 14px 1rem | |
| * 16px 1.142857143rem |
| var runner = require('child_process'); | |
| runner.exec( | |
| 'php -r \'include("settings.php"); print json_encode($databases);\'', | |
| function (err, stdout, stderr) { | |
| var connection = JSON.parse(stdout).default.default; | |
| console.log(connection.database); | |
| // result botdb | |
| } |
