| newpg=9.6.1 # set to new PG version number | |
| oldpg=`pg_config --version | cut -d' ' -f2` | |
| # PG 96. upgrades the readline to v7, which breaks anything linked against readline v6, like ruby via ruby-build. | |
| # I *think* this should prevent it from installing v7. But if weird shit happens with various rubies, | |
| # you'll have to reinstall them. | |
| brew pin readline | |
| # Stop current Postgres server | |
| brew services stop postgresql |
After reading Code Climate's Rails' Insecure Defaults I realized I was guilty of breaking rule 3. Versioned Secret Tokens. Here's how I fixed it.
Use dotenv in development and test environments:
# Gemfile
gem 'dotenv-rails', groups: [:development, :test]
| # As a general rule, I despise all things SEO with it's witchery and voodoo ways. | |
| # However, these two practices are confirmed semi-non-witchcraft SEO best practice. | |
| # | |
| # 1. Serve your content from a consistent domain (www vs. non-www, Doesn't matter. Just be consistent) | |
| # In addition this is nice for Heroku and other cloud based deployment environments that leave your app | |
| # accessible from a url like http://myapp.herokuapp.com | |
| # | |
| # 2. Believe it or not, trailing slashes matter. The google machine interprets http://domain.com/about | |
| # as a different page than domain.com/about/ | |
| # (source: http://googlewebmastercentral.blogspot.com/2010/04/to-slash-or-not-to-slash.html ) |
| # file: /etc/xdg/lxsession/LXDE/autostart | |
| # sudo raspi-config # Enable Boot To Desktop | |
| # idea via: http://lokir.wordpress.com/2012/09/16/raspberry-pi-kiosk-mode-with-chromium/ | |
| @lxpanel --profile LXDE | |
| @pcmanfm --desktop --profile LXDE | |
| # @xscreensaver -no-splash | |
| @xset s off |
When running specs I often see this output before the specs start to run.
> rspec spec
Time: 0.288 ms
Time: 0.110 ms
Time: 0.084 ms
Time: 0.095 ms
Time: 0.105 ms
Time: 0.115 ms
When dealing with legacy data it's been pretty common to run into malformed / illegal byte sequences in files. Figuring out what's causing the issue is often really difficult, especially when the file has thousands of rows.
Here's a trick I pretty much stumpbled upon:
nl file.txt | sort
sort: string comparison failed: Illegal byte sequence
sort: Set LC_ALL='C' to work around the problem.
Heroku's docs on this are now the definitive source. I just followed their instructions to update my apps and they're much better than they were when I made this gist. Here's the previous revision if you need still need it. Good luck!
| #= require support/jasmine-given | |
| class Geolocation | |
| getCurrentPosition: -> | |
| options = | |
| maximumAge: 0 | |
| timeout: 1*10*1000 | |
| enableHighAccuracy: true | |
| navigator.geolocation.getCurrentPosition(@success, @failure, options) |
| 1.9.3-p327 → rspec spec/requests/ | |
| WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.7.8 | |
| Rack::File headers parameter replaces cache_control after Rack 1.5. | |
| ...^CF^C | |
| An error occurred in an after hook | |
| Errno::EPIPE: Broken pipe | |
| occurred at /Users/cjolly/.rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/gems/poltergeist-1.0.2/lib/capybara/poltergeist/web_socket_server.rb:144:in `write' | |
| F | |
| An error occurred in an after hook |
>> ps.cancel_at
=> Fri, 05 Oct 2012 00:00:00 UTC +00:00
>> ps.cancel_at.class
=> ActiveSupport::TimeWithZone
>> ps.cancel_at = DateTime.new 2012, 11, 05
=> Mon, 05 Nov 2012 00:00:00 +0000
>> ps.save
(0.2ms) BEGIN
Entity Load (0.5ms) SELECT "entities".* FROM "entities" WHERE "entities"."id" = 2485 LIMIT 1