In a recent twitch stream, Gary Bernhardt showed a bit of behind-the-scenes in how he prepares his development environment for recording a screencast. One of the tools he showed in passing was gem_home by Hal Brodigan. gem_home is a simple script that manipulates Ruby’s GEM_HOME and GEM_PATH environmental variables in order to keep separate ruby gem locations. By using gem_home, there is no longer a requirement to prefix all ruby commands with bundle exec.

vim-rails is enabled only if config/environment.rb is present in the Rails working directory. At work, we have an engine based working directory that does not contain this file (as there’s an embedded application within the engine.) To enable vim-rails, I need to do: echo "load ::File.expand_path('../../embedded-app/config/environment.rb',__FILE__)" >> config/environment.rb mkdir -p .git/info echo "config/environment.rb" >> .git/info/exclude Within the repo to enable vim-rails support.

Today I needed to prove that my Rails controller method deleted a cookie. After Googling for the answer (without success), I came up with the following. Within your controller: cookies.delete('cookie-to-delete') In your controller spec you can check that the cookie was deleted with: expect(response.cookies).to include('cookie-to-delete' => nil) Rails sets the cookies to be deleted to a value of nil. By checking for the presence of both the cookie name with a value of nil, you can ensure your controller code deleted the cookie.