Yaknow how you're waiting for waiting for Rails to start and other people overhear you say "Go Go Go Go!" to your computer?
Install the gem (no need to put it in your Gemfile):
gem install gogo
Make sure you're in your Rails project and then run:
That will launch you into a pseudo-shell with the Rails test environment reloaded. If you want to use gogo for development commands such as
rake db:migrate, or
rails console, launch a separate shell and run:
$ gogo d
Now, run some commands. Ruby scripts that load Rails should start astronomically faster.
Don't "bundle exec" inside gogo. It will really exec and Rails will start as slow as before.
It is fishy. GoGo is a hack script.
I'm sharing it with the world because it's an incredibly useful hack, but I can't guarantee any level of maintenance on my part. If stuff breaks, you're probably on your own to fix it. Leave your experience in the wiki to help others.
GoGo is a lot like Spork. GoGo preloads your rails environment. When you run a ruby command, the gogo process is forked and the command is loaded into that environment. Here's a performance comparison for a large project:
$ time bundle exec cucumber features/admin/dashboard.feature:0 real 0m30.457s user 0m27.300s sys 0m2.941s $ gogo Creating default Gofile for Rails... Loading application.rb...and environment.rb...and cucumber...and cucumber/rails...and webmock/cucumber...and ruby-debug...and factory_girl/step_definitions...and email_spec...and email_spec/cucumber...and capybara/firebug...and vcr...and rake...took 26.25 seconds. test $ cucumber features/admin/dashboard.feature:0 cucumber took 3.65 seconds. test $ cucumber features/admin/dashboard.feature:0 cucumber took 3.58 seconds.
The advantages over Spork are:
- No DRB weirdness
- Easy install -- little to no modification to test environment.
- Speeds up other rails commands: rake routes, rails g migration, rake db:seed
- Single tab, so you know when code reloads are complete.
- It's not a full shell. No aliases or boolean logic || && for commands.
- You're already in a bundled environment, so rake db:seed is going to apply to the test environment. You probably don't want that.
- Have to ctrl-D and reload after Gemfile changes.
- Uses some Mac OS X only features, but if you want to hack those out it shouldn't be too hard.
One advantage over even the shell is a per-project and per-environment command history.
To fix a problem or add a feature, use the standard pull request workflow:
# fork it on github, then clone: git clone email@example.com:YOUR_USERNAME/gogo.git # hack away git push # then make a pull request
Once you get a pull request accepted, I'll add you so you can commit directly to the repository.
git clone firstname.lastname@example.org:brianhempel/gogo.git # hack away git push
Public domain; no restrictions.
And certainly: no warrantee of fitness for any purpose. It's a hack. Use at your own risk.