If it's a pain to get the databases set up, then the quickest way to get into production mode is such:
config/database.yml -- set production database to development database config/environment.rb -- manually set RAILS_ENV to production Restart your server and you're in production mode. Jason On 9/24/07, Max Williams <[EMAIL PROTECTED]> wrote: > > > Question - My rails project is due in in a few hours. It's running on > the net in development mode, on a Bluehost shared server. Because its > in dev mode, if anything goes wrong you get the nasty rails crash info > (useful for me, bad for users). > > Maybe it's the coffee, but i've got a sudden urge to get it running in > production mode so i can do some nice 'error' pages for the 404 and 500. > Getting it working in dev mode required quite a lot of work on several > people's parts just due to the vagaries of Bluehost mainly. > > So - switching to production mode. Have i lost it? Should i stick with > what i've got? Or go for it? How do i go about doing it if i want to? > I've got the production database set up - do i need anything else? > -- > Posted via http://www.ruby-forum.com/. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
