Stop your running postgres server (your plist name may or may not have specified the version in it, mine had 94 in the name)
launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.postgresql94.plist
Upgrade to 9.6
brew update && brew upgrade postgresql
Check your version
| class BottomlessHash < Hash | |
| def initialize | |
| super &-> h, k { h[k] = self.class.new } | |
| end | |
| def self.from_hash(hash) | |
| new.merge(hash) | |
| end | |
| end |
I fell in love with CoffeeScript a couple of years ago. Javascript has always seemed something of an interesting curiosity to me and I was happy to see the meteoric rise of Node.js, but coming from a background of Python I really preferred a cleaner syntax.
In any fast moving community it is inevitable that things will change, and so today we see a big shift toward ES6, the new version of Javascript. It incorporates a handful of the nicer features from CoffeeScript and is usable today through tools like Babel. Here are some of my thoughts and issues on moving away from CoffeeScript in favor of ES6.
While reading I suggest keeping open a tab to Babel's learning ES6 page. The examples there are great.
Holy punctuation, Batman! Say goodbye to your whitespace and hello to parenthesis, curly braces, and semicolons again. Even with the advanced ES6 syntax you'll find yourself writing a lot more punctuatio
| VAGRANTFILE_API_VERSION = '2' | |
| $install = <<SCRIPT | |
| curl -L https://github.com/docker/fig/releases/download/1.0.1/fig-`uname -s`-`uname -m` > /usr/local/bin/fig | |
| chmod +x /usr/local/bin/fig | |
| SCRIPT | |
| $build = <<SCRIPT | |
| cd /vagrant | |
| fig build |
| require "net/http" | |
| def start_server | |
| # Remove the X to enable the parameters for tuning. | |
| # These are the default values as of Ruby 2.2.0. | |
| @child = spawn(<<-EOC.split.join(" ")) | |
| XRUBY_GC_HEAP_FREE_SLOTS=4096 | |
| XRUBY_GC_HEAP_INIT_SLOTS=10000 | |
| XRUBY_GC_HEAP_GROWTH_FACTOR=1.8 | |
| XRUBY_GC_HEAP_GROWTH_MAX_SLOTS=0 |
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
| gem 'jekyll', '~> 2.0.0.alpha' | |
| gem 'nokogiri' | |
| gem 'redcarpet' | |
| gem 'rouge' |
| <?php | |
| class SecureSessionHandler extends SessionHandler { | |
| protected $key, $name, $cookie; | |
| public function __construct($key, $name = 'MY_SESSION', $cookie = []) | |
| { | |
| $this->key = $key; | |
| $this->name = $name; |
| Composer doesn't work with GitHub Two Factor Authentication. | |
| You have to generate a token (with "repo" scope at least) at https://github.com/settings/applications | |
| Copy the token and keep it somewhere safe. | |
| Run: composer config -g github-oauth.github.com paste-your-token-here |
| require 'spec/support/grep_matcher' | |
| describe do | |
| disallow_presence_of pattern: "send(.*#", | |
| location: "app/", | |
| description: "Do not use dynamic method invocations", | |
| failure: "Please change dynamic method call to something more sane." | |
| end |