TL;DR
Create a backup:
pg_dumpall > mybackup.sqlPerform the upgrade:
sudo pg_dropcluster 9.4 main --stop| # be sure to comment out the require 'capistrano/deploy' line in your Capfile! | |
| # config valid only for Capistrano 3.1 | |
| lock '3.2.1' | |
| set :application, 'my-cool-application' | |
| # the base docker repo reference | |
| set :name, "johns-stuff/#{fetch(:application)}" |
TL;DR
Create a backup:
pg_dumpall > mybackup.sqlPerform the upgrade:
sudo pg_dropcluster 9.4 main --stopWhen the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
| #!/usr/bin/env ruby | |
| # | |
| # = Email Ping | |
| # | |
| # Check to see if an email address exists by looking up MX records and connecting | |
| # to the address's home SMTP server. It then starts to send a message to the address | |
| # but quits before the message is actually sent. | |
| require 'resolv' | |
| require 'net/smtp' |
| # Capistrano Laravel 4 Deployment Tasks | |
| # Watts Martin (layotl at gmail com) | |
| # https://gist.github.com/chipotle/5506641 | |
| # updated 14-Aug-2013 | |
| # Assumptions: | |
| # | |
| # - You are using a .gitignore similar to Laravel's default, so your | |
| # vendor directory and composer(.phar) are *not* under version control | |
| # - Composer is installed as an executable at /usr/local/bin/composer |
| #!/usr/bin/env ruby | |
| def changelog_for_gem(gem) | |
| changelogs = `bundle exec gem contents #{gem}`.lines.grep(/history|changelog|news/i) | |
| if changelogs.empty? | |
| puts "No changelog found for gem #{gem}" | |
| return nil | |
| end |