Forum: Ruby on Rails Rails App, Going Live

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
B20f60d4dae0d5f372c73caf1418565a?d=identicon&s=25 Jason Stirman (stirman)
on 2006-06-08 23:56
I built my rails app locally, and just today put it all online.

Getting a "Application error (Rails)" when trying to submit some form
parameters to the db.

What needs to be done with going from local development to live?

I'm not sure if/where I need to set my app to "production" status.

Also, is there any way to debug "Application error (Rails)"??

Thanks,
stirman
D0cd6b10e01bacb976b3b815a9c660bc?d=identicon&s=25 Alex Wayne (Guest)
on 2006-06-09 00:18
Jason Stirman wrote:
> I built my rails app locally, and just today put it all online.
>
> Getting a "Application error (Rails)" when trying to submit some form
> parameters to the db.
>
> What needs to be done with going from local development to live?
>
> I'm not sure if/where I need to set my app to "production" status.
>
> Also, is there any way to debug "Application error (Rails)"??
>
> Thanks,
> stirman

Look in the log files.  It should tell you what the error is.  If you
are seeing that messge you are in production mode, so look in
log/production.log.  The environment is set via variable passed from the
webserver config, or from config/evironment.rb.  You should see a
commented few lines in there:

# Uncomment below to force Rails into production mode when
# you don't control web/app server and can't set it the proper way
# ENV['RAILS_ENV'] ||= 'production'

That will set it to production mode, although it should ideally be set
by the web server.
30ee518e6fdc5b07e060775b5a542bdb?d=identicon&s=25 Jón Borgþórsson (jongretar)
on 2006-06-09 01:52
(Received via mailing list)
3 possible reasons:
 1) Rights Issue. The webserver is unable to write to tmp or log. To
test this you can type in from the rails root the command "chmod -R
777 log/ tmp/". A dirty way to do things but it will at least tell you
if that was the problem,
 2) public/.htaccess points to dispatch.cgi instead of distpatch.fcgi.
 3) ruby is in non standard location. Type in the command "which
ruby". Compare the ruby location to the one in dispatch.fcgi.
 4) rinse and repeat.

On 6/8/06, Jason Stirman <stirman@gmail.com> wrote:
>
> Thanks,
> stirman
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>


--
B20f60d4dae0d5f372c73caf1418565a?d=identicon&s=25 Jason Stirman (stirman)
on 2006-06-09 03:32
Great suggestions, going to try them right now.

Many thanks for the help!!!

-stirman
This topic is locked and can not be replied to.