[Radiant] Configuring Radiant with Apache - Phusion Passenger
Bhupi Chate
I am having problem with configuring Radiant with Apache & Phusion
Passenger.
Can anybody help me in configuring Radiant with Apache & Phusion
Passenger. I am new at using Apache & Phusion Passenger.
Please help...
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
Radiant mailing list
Post: Rad...@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Keith Bingman
Passenger now and do all of my local testing with it. I haven't really
had an issues. Can you be a bit more specific?
Keith
Keith Bingman
Passenger now and do all of my local testing with it. I haven't really
had an issues. Can you be a bit more specific?
Keith
On Sep 16, 2008, at 1:33 PM, Bhupi Chate wrote:
Giovanni Intini
on passenger on a vps, but I guess I'll just reply in this thread.
When I start the site it works fine, until radiant tries to regenerate
the cache. When the cache expires I get a 500 error and the only
solution is to clean by hand the cache directory. The ownership is ok
(www-data:www-data) and the permissions are 0777.
2008/9/16 Keith Bingman <ke...@keithbingman.com>:
> What exactly is your problem? I have 5 or 6 sites running with Passenger now
> and do all of my local testing with it. I haven't really had an issues. Can
> you be a bit more specific?
Bhupendra Chaudhari
> What exactly is your problem? I have 5 or 6 sites running with
> Passenger now and do all of my local testing with it. I haven't really
> had an issues. Can you be a bit more specific?
>
> Keith
Can you please suggest is their any specific configuration under Apache
for using radiant site with the help of Phusion Passenger.
Josh Schairbaum
passenger:
<VirtualHost *:80>
ServerName server.com
ServerAlias www.server.com
DocumentRoot /home/user/public_html/server.com/radiant/current/public
ErrorLog /var/log/apache2/error.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog /var/log/apache2/access.log combined
</VirtualHost>
On Tue, Sep 16, 2008 at 7:49 AM, Bhupendra Chaudhari
<bhups...@gmail.com>wrote:
Josh Schairbaum
passenger:
<VirtualHost *:80>
ServerName server.com
ServerAlias www.server.com
DocumentRoot /home/user/public_html/server.com/radiant/current/public
ErrorLog /var/log/apache2/error.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog /var/log/apache2/access.log combined
</VirtualHost>
On Tue, Sep 16, 2008 at 7:49 AM, Bhupendra Chaudhari
<bhups...@gmail.com>wrote:
> Keith Bingman wrote:
Jay Levitt
> Make sure you kill the Rails .htaccess in /public. This works for me with
> passenger:
Like the others, I've had no problems with passenger 2.0.3. In fact, I
don't even have to do anything to the config; it "just works":
<VirtualHost *:80>
ServerName www.wellesleycarriagehouse.com
DocumentRoot /srv/www/sites/wellesleycarriagehouse.com/public
CustomLog /var/log/httpd/wellesleycarriagehouse.com.access.log combined
</VirtualHost>
Bhupi, what sort of errors are you seeing in the browser? What do the logs
say? (Depending on your Linux distro, Apache might be writing its logs to
/etc/httpd/logs or someplace equally odd, so be sure to look around.)
Jay Levitt
> Make sure you kill the Rails .htaccess in /public. This works for me with
> passenger:
Like the others, I've had no problems with passenger 2.0.3. In fact, I
don't even have to do anything to the config; it "just works":
<VirtualHost *:80>
ServerName www.wellesleycarriagehouse.com
DocumentRoot /srv/www/sites/wellesleycarriagehouse.com/public
CustomLog /var/log/httpd/wellesleycarriagehouse.com.access.log combined
</VirtualHost>
Bhupi, what sort of errors are you seeing in the browser? What do the logs
say? (Depending on your Linux distro, Apache might be writing its logs to
/etc/httpd/logs or someplace equally odd, so be sure to look around.)
Jay Levitt
> I was going to post a message about a problem I'm having with radiant
> on passenger on a vps, but I guess I'll just reply in this thread.
Actually, I suspect this thread might get a little confusing, so I forked
the subject line...
> When I start the site it works fine, until radiant tries to regenerate
> the cache. When the cache expires I get a 500 error and the only
> solution is to clean by hand the cache directory. The ownership is ok
> (www-data:www-data) and the permissions are 0777.
What errors do you see in the Apache logs when this happens? I've never
looked at Radiant's caching, since it Just Works for me; is there a way to
force the cache to expire, so I can see what happens on my (working) setup?
Jay Levitt