I have a pretty complex model with many modules and I have been trying to keep it clean, but I find that loading the model in development mode using WebBrick is much more lenient than production mode with lighttpd/fcgi. For instance, if I neglect to create a dedicated file that declares the module then I run everything in development mode it works fine, but as soon as it is deployed I get ''uninitialized constant'' exceptions for the model. Does anyone know how to get the development mode to more closely reflect the production mode? -John -- John Smilanick Computing Staff - Webmaster Kavli Institute for Theoretical Physics University of California, Santa Barbara jsmilani@kitp.ucsb.edu (805) 893-6307 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060522/c02a805a/attachment.html
John Smilanick wrote:> I have a pretty complex model with many modules and I have been > trying to keep it clean, but I find that loading the model in > development mode using WebBrick is much more lenient than production > mode with lighttpd/fcgi. For instance, if I neglect to create a > dedicated file that declares the module then I run everything in > development mode it works fine, but as soon as it is deployed I get > ''uninitialized constant'' exceptions for the model. Does anyone know > how to get the development mode to more closely reflect the > production mode? > > -John > > -- > John Smilanick > Computing Staff - Webmaster > Kavli Institute for Theoretical Physics > University of California, Santa Barbara > jsmilani@kitp.ucsb.edu > (805) 893-6307Sounds like your files are not being properly loaded due to production caching. Always be sure to restart the webserver after every deploy to production. -- Posted via http://www.ruby-forum.com/.