Setting up Dokku with DigitalOcean and Namecheap
..or how I made my own heroku in a few hours for $3.98.
This write-up is very out of date! You probably shouldn't use it.
#!/bin/bash | |
# Stop all containers | |
docker stop $(docker ps -a -q) | |
# Delete all containers | |
docker rm $(docker ps -a -q) | |
# Delete all images | |
docker rmi $(docker images -q) |
{ | |
// The plugin looks for a .jsbeautifyrc file in the same directory as the | |
// source file you're prettifying (or any directory above if it doesn't exist, | |
// or in your home folder if everything else fails) and uses those options | |
// along the default ones. | |
// Details: https://github.com/victorporof/Sublime-HTMLPrettify#using-your-own-jsbeautifyrc-options | |
// Documentation: https://github.com/einars/js-beautify/ | |
"html": { | |
"allowed_file_extensions": ["htm", "html", "xhtml", "shtml", "xml", "svg", "dust"], |
docker ps | awk {' print $1 '} | tail -n+2 > tmp.txt; for line in $(cat tmp.txt); do docker kill $line; done; rm tmp.txt |
Clearly ES6 is a huge improvement over ES5, and tools like [6to5][] allow us to use these cool features now. I was reading [Replace CoffeeScript with ES6][replace coffeescript] by [Blake Williams][] and thought it was a great summary of how ES6 solves many of the same problems that CoffeeScript solves; however I'd like to comment on a few of Blake's points and talk about why I'll be sticking with CoffeeScript.
Classes in ES6 (like many of the syntax changes in ES6) are very similar to the CoffeeScript equivalent. To support browsers that are not fully ES5 compliant (e.g. IE8-), however, we still can't really use getters/setters, so ignoring these the comparison is:
# If you worked with React and JSX you probably noticed that you can't use JS comments when inside JSX sections | |
# Add this to your Atom init script | |
# Then add 'ctrl-cmd-/': 'comment-jsx' to your keymap.cson | |
# Then when you are on a JS/JSX file, just press cmd+ctrl+/ to use JSX-style comments that work with JSX elements | |
# Is not the most efficient way, but it's the cleanest and reliable one | |
atom.commands.add 'atom-workspace', 'comment-jsx', -> | |
atom.config.set('editor.commentStart', '{/*', {scopeSelector: '.source.js.jsx'}) | |
atom.config.set('editor.commentEnd', '*/}', {scopeSelector: '.source.js.jsx'}) | |
for selection in atom.workspace.getActiveTextEditor().selections |
# If you worked with React and JSX you probably noticed that you can't use JS comments when inside JSX sections | |
# Add this to your Atom init script | |
# Then add 'ctrl-cmd-/': 'comment-jsx' to your keymap.cson | |
# Then when you are on a JS/JSX file, just press cmd+ctrl+/ to use JSX-style comments that work with JSX elements | |
# Is not the most efficient way, but it's the cleanest and reliable one | |
atom.commands.add 'atom-workspace', 'comment-jsx', -> | |
atom.config.set('editor.commentStart', '{/*', {scopeSelector: '.source.js.jsx'}) | |
atom.config.set('editor.commentEnd', '*/}', {scopeSelector: '.source.js.jsx'}) | |
for selection in atom.workspace.getActiveTextEditor().selections |
Edit 2015-10-29: Adding readline's history capacity Depending on posix compliant: could work on poor system with generic shell environments bash specific: using so called bashisms and if you want simple in line question / answer (generic solutions) pretty formated interfaces, like ncurses or more graphical using libgtk or libqt... use powerful readline history capability (new oct 2015)
disclaimer: this worked for me, your mileage may vary. Your Pi, your responsibility :)
After putting Arch Linux on a 16GB SD card using these instructions, I ended up with about 14GB of free space.
Arch Linux uses one primary partition (/dev/mmcblk0p1) and an extended partition (/dev/mmcblk0p2) containing one logical partition (/dev/mmcblk0p5). The primary partition is the boot partition and the logical partition is the root partition. Rather than adding another primary partition I just wanted to resize the root partition and filesystem.
According to this bugreport parted
no longer handles resizing of partitions and gparted needs a graphical environment to run. So I had to come up with something else to resize my partitions.
/** | |
* Simple authentication and authorization example with passport, node_acl, | |
* MongoDB and expressjs | |
* | |
* The example shown here uses local userdata and sessions to remember a | |
* logged in user. Roles are persistent all the way and applied to user | |
* after logging in. | |
* | |
* Usage: | |
* 1. Start this as server |