On Mar 20, 4:30 pm, cdempsey <cdal...@gmail.com> wrote: > I've been poking around using my search-fu to look for a way to run > code after Rails 3 has initialised but before any requests are > services. I was thinking of scenarios like migrating the database or > forcing administrators to set values to new application configuration > properties and things like that.
How about in boot.rb or is that too early ? I wouldn't recommend using that kind of process for migrations though, you could have bad side effects, for instances if two instances of rails get started up (by accident, crash recovery mechanism, etc.) and both attempt to perform the migration. Katie -- http://www.coderstack.co.uk/ruby-developer-jobs -- 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.
