Search results

Actually the permissions issue had to do with me not correctly setting group write access on the public directory, so my application wasn't able to writing out cache files. D'oh! :rolleyes: Everything is working great! -- DeLynn Berry delynn@gmail.com http://delynnberry.com

Just wanted to let you know that I was able to get everything (including Capistrano and it's maintenance page) working with the 2.2 release. For reference all I had to do was create my own restart task in deploy.rb and have it call the following: sudo "/usr/local/lsws/bin/lswsctrl restart" Then...

I was wondering if that might not be the case. I just didn't get a chance to find/install/configure/etc the spawn-fcgi script. Capistrano does have the capability to execute commands as a sudo user, so talking to lswsctrl shouldn't be a problem. I'm excited to see the new features in 2.2...

Forgive me, but I totally forgot to post back here. I ended up briefly trying to get LSAPI and Capistrano to work nicely, and then went on a trip last week, and then have been busy trying to catch up at work so far this week. I only played with this briefly, but what I did discover was that...

Cool. I'll give it a shot tonight or tomorrow and report back here with my findings!

Yeah, this makes a ton more sense. Sorry I didn't think of that last night, but it had been a long day dealing with Capistrano and I just wasn't thinking. Hmm, that answers my next question. Do you know if anyone has attempted using the Spinner/Spawner/Reaper scripts with the LSAPI dispatcher...

mistwang, thanks for all your help so far. I may be on to something here on my end though. I pulled all the Rewrite Rules out of my LiteSpeed Virtual Host configuration, and since I'm still seeing the same results, I'm beginning to think that the problem must have something to do with my...

Strange indeed. I did a double check on the VHOST log file as well as the server error log file and in both instances the last entry when making a request to "/" is: [REWRITE] Last Rule, stop! I'm not aware of Capistrano doing anything to change the document root, but if I get some time...

I'm having trouble getting LiteSpeed to properly display the maintenance page that Capistrano creates while performing an update. The 404.html page that is found in my RAILS_ROOT/public directory is always served unless I specifically make a request for /system/maintenance.html. Here is what...