> An alternative approach would be to start separate processes for
> 'test' and 'development' environments, so they can both run the
> initializer to completion. This would give the maximum speedup, and as
> long as you set config.cache_classes = false in the test environment,
I decided to go with this approach, and it seems to work rather well.
For now, you need to specify the environment to use up-front: e.g.
RAILS_ENV=test frake test:units
RAILS_ENV=development fruby script/runner 'p Foo.first'
The reduction in startup time is quite startling.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
