That’s good information. Thanks for that. I got Passenger working but as you
have indicated, managing vhosts would be much easier with a single local domain
reference. I will check it out.
Cheers
On Jan 25, 2014, at 8:14 AM, Frederick Cheung
wrote:
> It's RackEnv (which is an alias fo
On Friday, January 24, 2014 7:05:43 PM UTC+1, Walter Lee Davis wrote:
> >
>
> > Other than that I don’t know where to find other Passenger parameters. Is
> > there no way to use Passenger for a local development environment?
>
>
>
> Sure. You just need to read through the passenger docs to f
OK, with some reading I think I'll uninstall Passenger until I have some time
to dedicate time to it. I thought it was a simple solution for apache.
Thanks for the heads up.
On Jan 24, 2014, at 1:05 PM, Walter Lee Davis wrote:
> Sure. You just need to read through the passenger docs to fin
On Jan 24, 2014, at 12:59 PM, BeeRich wrote:
>
> On Jan 24, 2014, at 12:54 PM, Walter Lee Davis wrote:
>
>> If you're clearly in development, why are you hitting passenger? What does
>> your passenger configuration (in Apache or Nginx) look like? Did you set an
>> environment flag explicitly
On Jan 24, 2014, at 12:54 PM, Walter Lee Davis wrote:
> If you're clearly in development, why are you hitting passenger? What does
> your passenger configuration (in Apache or Nginx) look like? Did you set an
> environment flag explicitly to development? If not, I believe that passenger
> alw
On Jan 24, 2014, at 12:50 PM, BeeRich wrote:
> passenger (4.0.35)
> lib/phusion_passenger/rack/thread_handler_extension.rb:77:in `process_request'
> passenger (4.0.35)
> lib/phusion_passenger/request_handler/thread_handler.rb:142:in
> `accept_and_process_next_request'
> passenger (4.0.35)
On Jan 24, 2014, at 11:48 AM, Hassan Schroeder
wrote:
>> Turns out mysql is barfing.
>
> That's so sad; maybe some ginger ale and a bit of bed rest will help?
Hey that's funny.
> OR maybe post the actual error message/stack trace here?
>> My database.yml has my local mysql using a userna
On Fri, Jan 24, 2014 at 8:37 AM, BeeRich wrote:
> Turns out mysql is barfing.
That's so sad; maybe some ginger ale and a bit of bed rest will help?
OR maybe post the actual error message/stack trace here?
> My database.yml has my local mysql using a username and password set for all
> three m
Hi folks. New to Rails.
Got the following coming up using Passenger:
We're sorry, but something went wrong.
If you are the application owner check the logs for more information.
Turns out mysql is barfing. My database.yml has my local mysql using a
username and password set for all three mode
Bare with me on this one
We have a lot of read only data. And it is accessed a lot more then
the user created data at this stage. The datbase structure is (on
production):
production_user db
2 production_read_only databases behind HAProxy
So some models make a connection to the read_only
10 matches
Mail list logo
