I'm fairly certain this is an easy question to answer but I like to make things more complicated than they need to be.
I notice that a lot of people have: RAILS_ENV=production .. in their environment.rb files I don't have this in mine on production but passenger/apache startup my app just fine in production mode. So, is it really necessary? I also noticed that in order to do rake tasks against the production server I had to type: RAILS_ENV=production rake foo with foo being the task to perform. Is this due to the fact that I don't have RAILS_ENV=production in my environment.db? Or, is this normal default behavior that I should get used to understanding? And, lastly, is there any commands that I've been using in development that will definitely change in production? Rake was one of them. Any others? A possible cheat sheet around? Many thanks. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
