It appears my http setup is working but I am getting an error when I try
to use a web browser to connect.
All I have done so far is to change the setting from what was working in
httpd.conf and move it to ssl.conf (adding some ssl things) and I am
using the same directory/set of files that was working for development.
The error...
Ruby on Rails application could not be started
Phusion Passenger has listed more information on the error below
These are the possible causes:
* There may be a syntax error in the application''s code. Please
check for such errors and fix them.
* A required library may not installed. Please install all libraries
that this application requires.
* The application may not be properly configured. Please check
whether all configuration files are written correctly, fix any incorrect
configurations, and restart this application.
* A service that the application relies on (such as the database
server or the Ferret search engine server) may not have been started.
Please start that service.
Further information about the error may have been written to the
application''s log file. Please check it in order to analyse the
problem.
Error message:
uninitialized constant Tabnav
Exception class:
NameError
Application root:
/home/craig/railserp
Backtrace:
# File Line Location
I''ll leave off the backtrace for now.
Was there somewhere inside the rails root that I was supposed to tell
Rails to use production instead of development?
The weird thing is even if I just switch it from production to
development in ssl.conf, it works, no errors.
Can anyone toss me a bone here?
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Craig White
2009-Aug-04 05:35 UTC
Re: SOLVED Passenger, switching from development to production
On Mon, 2009-08-03 at 21:26 -0700, Craig White wrote:> It appears my http setup is working but I am getting an error when I try > to use a web browser to connect. > > All I have done so far is to change the setting from what was working in > httpd.conf and move it to ssl.conf (adding some ssl things) and I am > using the same directory/set of files that was working for development. > > The error... > > Ruby on Rails application could not be started > Phusion Passenger has listed more information on the error below >---- never mind - I had to remove some old files I had stashed in a folder inside of app/models - apparently development ignores them but production does not ignore them. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Rick DeNatale
2009-Aug-06 20:13 UTC
Re: Passenger, switching from development to production
On Tue, Aug 4, 2009 at 12:26 AM, Craig White<craigwhite-BQ75lA0ptkhBDgjK7y7TUQ@public.gmane.org> wrote:> Was there somewhere inside the rails root that I was supposed to tell > Rails to use production instead of development?Assuming you are using passenger with apache, the RailsEnv directive, which should go in the apache vhost configuration tells passenger which rails environment to run under. e.g. <VirtualHost *:80> ServerName yourhostname.com DocumentRoot "/path/to/your/rails/app/public" RailsEnv production <directory "/path/to/your/rails/app/public"> Order allow,deny Allow from all </directory> I haven''t used passenger with Nginx, but there''s probably something similar. -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale