How to get Rails 3 to run in production mode on server w/ Passenger -
Hi, I'm turning Passenger / Occasions / Rail 3.2 (with an active record or mysql) with a Capistrano deployment script.
I'm trying to run my app in production mode on my Linux server.
I have the following in my Apache configuration file ...
& lt; VirtualHost *: 80 & gt; ServerName example.com ServerAlive www.example.com DocumentRoot /srv/www/example.com/current/public Error Log /srv/www/example.com/current/log/error.log CustomLog /srv/www/example.com / Current / log / access.log combined passenger default user www-data & lt; Directory /srv/www/test.example.com/current/public> Allow all options - Multi-view & lt; / Directory & gt; RailsEnv production & lt; / VirtualHost & gt; Edit: My environment. I do not have the following in the RB file ...
Railway_NV = "production" RAILS_ENV.freeze In my Capistrano deploy.rb I have the following ...
set: rails_env, "output" edit: but when I deployed via capistrano or Restart a sudo service apache2 It says that Apache is restarted, but the server never comes when I reach the URL.
An unusual problem. I have deployed many applications with the same or similar stack without incident.
Try it:
- Please remove any custom code from your environment .bb file (related to this problem)
- rails_env from your deployment file Remove the variable
- Be sure to leave "Railsenveve production" inside your Apache virtual host config
- SSH in server and restart Apache manually
I will check in the morning, but I believe that the mod_rails will be reworked It's not good, put me think that I manually restart Apache after deployment. Sure, why think about doing this with the fact that "current_path" is just a symmetric or perhaps "passenger insistence" is stopping new passenger thread from modified sponge code. All speculation.
Comments
Post a Comment