Ah, as is usually the way with these things, I found out what was going
wrong just after sending this.
I''d forgotten to change the socket path in the FCGI setup as well. Doh!
Cheers
Luke
On 11/22/05, Luke Redpath
<contact-5bSlq4ThgqCxcuGT1ypO+1pr/1R2p/CL@public.gmane.org>
wrote:>
> I have two instances of lighttpd running on my server, both running the
> same RubyOnRails app. The configuration for each instance of lighttpd is
> exactly the same except for the first is running on port 8080 and RAILS_ENV
> is set to "production" in the FCGI setup, and the other is
running on port
> 8081 with RAILS_ENV set to "development". This is so my clients
can play
> around with the system without messing up the production database which is
> due to be put into use shortly.
>
> I can confirm that both instances are using the correct Rails environment
> by going to a non-existant page - the server on port 8080 brings up the
> proper 404 error page, whilst the server on port 8081 brings up a Rails
> routing error, consistent with production/development behaviour.
>
> However, for some reason, they are both using the production database! My
> database.yml is configured properly, with both environments set to use
> databasename_<ENVIRONMENTNAME>. Both databases exist.
>
> Any ideas? Help is much appreciated.
>
> Cheers
> Luke
>
_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails