John Merlino wrote in post #965993: > I can't help notice that while development.log always updates, > production.log is completely empty. There's no runtime errors currently > locally or on server. But in both cases, production.log is empty.
Are you sure your server is actually running in the production environment (RAILS_ENV=production)? > Also, speaking of production and development, why should you use both a > production and development database (e.g. database_development, > database_production) when both will contain the same fields? It seems > like duplicate work. There should be three databases at least. Development, test & production. It's not duplicate work migrations take care of moving the schema forward (at least for ActiveRecord). Having separate development and production database allow you to experiment in the development database without affecting production data. The test database is there solely to support automated unit testing. This database should be emptied between each test case. You wouldn't want that to happen to the development or certainly not the production database. -- 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.
