TL;DR
Install Postgres 9.6, and then:
sudo pg_dropcluster 9.6 main --stop
sudo pg_upgradecluster 9.5 main
sudo pg_dropcluster 9.5 main
TL;DR
Install Postgres 9.6, and then:
sudo pg_dropcluster 9.6 main --stop
sudo pg_upgradecluster 9.5 main
sudo pg_dropcluster 9.5 main
# | |
# Would this be useful to Phoenix? | |
# | |
# In controllers, it'd be nice to be able to refer to status codes as atoms instead of integers. | |
# | |
defmodule Phoenix.Controller.StatusCodes do | |
@http_status_codes %{ |
// Use Gists to store code you would like to remember later on | |
console.log(window); // log the "window" object to the console |
# http://guides.rubygems.org/command-reference/#gem-environment | |
--- | |
gem: --no-ri --no-rdoc | |
benchmark: false | |
verbose: true | |
update_sources: true | |
backtrace: true | |
bulk_threshold: 1000 |
#!/usr/bin/env ruby | |
# Pow Port | |
# | |
# Quickly and easily change the port that Pow is running on. This allows | |
# you too run Apache and Pow side-by-side (on different ports of course). | |
# | |
# WARNING: This will OVERWRITE your ~/.powconfig file. If you have custom | |
# configurations in there, please back it up first. | |
# |
function rake { | |
if [ -e Gemfile ]; then | |
bundle exec rake $@ | |
else | |
`which rake` $@ | |
fi | |
} | |
function rspec { | |
if [ -e Gemfile ]; then |