Okay, this is starting to seem like the most likely answer, but I have
never before had issues deploying Rails apps with a similar config.
I have added the AllowOverride none to the virtual host, but I am not
sure if it is correct. As I still get the same error.
I think you were on to the
On 10.08.2008, at 20:46, Alan Peabody wrote:
Alan Peabody wrote:
Andrew Neil wrote:
On 9 Aug 2008, at 19:04, Alan Peabody wrote:
I have checked the logs. the apache logs show nothing but that it
is serving a 500 error and the rails logs show nothing.
Does the apache process have
On 9 Aug 2008, at 19:04, Alan Peabody wrote:
I seem to be getting a 500 error no matter how I deploy my radiant
site.
That is an internal server error. You might get an idea of what is
going on if you can look at the log files on your server. I had a
similar problem recently, and when I
Andrew Neil wrote:
On 9 Aug 2008, at 19:04, Alan Peabody wrote:
I seem to be getting a 500 error no matter how I deploy my radiant site.
That is an internal server error. You might get an idea of what is
going on if you can look at the log files on your server. I had a
similar problem
Alan,
My guess is that your Apache config is still trying to read .htaccess in
the public folder. Make sure to have AllowOverride none in your Apache
config that sets up the reverse proxy (inside the Directory or
VirtualHost).
Sean
Alan Peabody wrote:
Andrew Neil wrote:
On 9 Aug 2008,
