On Tuesday, December 3, 2013 1:30:21 PM UTC-8, Attila Gulyas wrote: > > Thanks a lot! I put that line at the end of production.rb and works like a > charm. I > realized that you suggested the same solution on stack but I got confused > where > to put it. In development.rb I still use the YAML.load version and the > initializer got ditched. > > Once on heroku there was an error in the views about the model objects > being undefined. > After putting "Sequel::Model.plugin :active_model" at the end of > production.rb it was ok. > Is this how you would configure sequel (in separate environment files) or > is there a > better/conventional way? I understand that this is a more rails-specific > question and sequel > is a tool for any ruby app using databases. Although now that everything > is on track this is > not that vital. >
If you want exactly the same database configuration in all environments, putting it in config/environment.rb should also work (just guessing, I didn't test that). I don't know enough about the rails internals to determine if there is a better place. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/groups/opt_out.
