# Can't seem to get Debain to understand "Production" **URL:** \ **Category:** Deployment\ **Created:** [November 26, 2007, 6:12am UTC](https://www.ruby-forum.com/t/cant-seem-to-get-debain-to-understand-production/121257 "2007-11-26T06:12:15Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [November 26, 2007, 6:12am UTC](https://www.ruby-forum.com/t/cant-seem-to-get-debain-to-understand-production/121257/1 "2007-11-26T06:12:15Z")
Hey all, I’ve just moved my rails app to a freshly-configured Debian Etch box, running rails 1.2.6, and I’ve run into a quandary. It seems that nothing I do (setting it in the environment.rb file, in the mongrel\_cluster.yml file, erasing all development and test data, restarting Apache and the mongrels) is making it clear to Debian that I want my app run in production mode. The thing is just hell-bent on development mode and for the life of me I can’t figure out how to change its mind. Possible issues: I developed the app on Rails 1.2.3 and am trying to run it on 1.2.6. I am getting routing and database connection errors mostly. The app is trying to connect using “root” without a password even though NEITHER my development nor my production environments use root and BOTH use passwords. Strange. I double-checked my routes file, and everything, despite the routing errors, is up-to-speed and it all runs great locally in the production environment. Anybody know what I’m doing wrong here? Thanks sean ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [November 26, 2007, 8:03am UTC](https://www.ruby-forum.com/t/cant-seem-to-get-debain-to-understand-production/121257/2 "2007-11-26T08:03:46Z")
Just want to add one more thing: even the standard default Rails “Welcome Aboard!” page seems to be suffering from this odd routing error. When I click on the “About your application’s environment” link, I get an error message: Routing Error no route found to match “/rails/info/properties” with {:method=\>:get} So the problem isn’t with my app; it has something to do with how Rails is set up on the server, I think. But what mistake that I could make would destroy Rails’ ability to route altogether? Curiouser and curiouser… ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [January 6, 2008, 4:00pm UTC](https://www.ruby-forum.com/t/cant-seem-to-get-debain-to-understand-production/121257/3 "2008-01-06T16:00:15Z")
Sean C. wrote: > Just want to add one more thing: even the standard default Rails > “Welcome Aboard!” page seems to be suffering from this odd routing > error. When I click on the “About your application’s environment” link, > I get an error message: > > Routing Error > > no route found to match “/rails/info/properties” with {:method=\>:get} > > So the problem isn’t with my app; it has something to do with how Rails > is set up on the server, I think. But what mistake that I could make > would destroy Rails’ ability to route altogether? > > Curiouser and curiouser… Hi Sean, I seem to be having exactly the same problem as you did. And these are my settings Ruby version 1.8.6 (i386-mswin32) RubyGems version 0.9.4 Rails version 2.0.2 Active Record version 2.0.2 Action Pack version 2.0.2 Active Resource version 2.0.2 Action Mailer version 2.0.2 Active Support version 2.0.2 Application root C:/work/Prj\_ROR/RailsApplication1 Environment development Database adapter mysql Did you every manage to get this working in Production mode? Regards, Ellils ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [January 7, 2008, 1:42am UTC](https://www.ruby-forum.com/t/cant-seem-to-get-debain-to-understand-production/121257/4 "2008-01-07T01:42:13Z")
Rails 2.0 is a whole new bag of worms. I did get the Rails app to work, eventually, though i can’t remember exactly how I did it. And this was before 2.0 came out. I think it had something to do with my Apache settings. This always happens to me: I get something working then totally forget how I fixed it when I run into the same problem three months down the road. Just go through everything until you feel like you’re losing your sanity. Right before you do, the problem will seem to fix itself in an instant and you’ll be fine. That’s how it seems to work with me. 😉