Hi all, I have a collocated server where I have set up Apache with FCGI. I and a friend use it for testing and showing work to clients. He does PHP mostly so I am in effect the only Rails user on this machine. Rails runs under FCGI. So far I have always developed locally and rsync-ed any changes to the server. If I happen to have changed models or such I have restarted apache for rails to pick up the changes. I am root, so I can do that. Now I also want to fix a colleague of mine with some space and the ability to run rails apps. How should I best handle this? Should I tell him to always run apps as CGI as opposed to FCGI? Is there a way to use FCGI and avoid constant reloading of the httpd server (as he obviously cannot restart the server)? Many thanks in advance for an ideas! Nicky
For development you should let him runt through CGI or WEBbrick... You could then give him rights to restart apache (if he runs the app live with FCGI) via sudo. Hope this helps :) /Dan On 6/15/05, Nickolay Kolev <nmkolev-OhoefBWHl6Eb1SvskN2V4Q@public.gmane.org> wrote:> Hi all, > > I have a collocated server where I have set up Apache with FCGI. I > and a friend use it for testing and showing work to clients. He does > PHP mostly so I am in effect the only Rails user on this machine. > Rails runs under FCGI. > > So far I have always developed locally and rsync-ed any changes to > the server. If I happen to have changed models or such I have > restarted apache for rails to pick up the changes. I am root, so I > can do that. > > Now I also want to fix a colleague of mine with some space and the > ability to run rails apps. How should I best handle this? Should I > tell him to always run apps as CGI as opposed to FCGI? Is there a way > to use FCGI and avoid constant reloading of the httpd server (as he > obviously cannot restart the server)? > > Many thanks in advance for an ideas! > > Nicky > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
> For development you should let him runt through CGI or WEBbrick... You > could then give him rights to restart apache (if he runs the app live > with FCGI) via sudo.This is a possible solution, although I would like him to have full FCGI speed all the time if possible. I wonder how commercial hosters do this? Anyone with Textdrive experience want to say a few words on the set-up? Is it CGI or FCGI? Nicky
TxD is apache/cgi by default. To use fastcgi you''ll need to do some configuration in the shell. lighttpd seems to be the standard for running fastcgi on TxD. On Jun 17, 2005, at 3:00 AM, Nickolay Kolev wrote:>> For development you should let him runt through CGI or WEBbrick... You >> could then give him rights to restart apache (if he runs the app live >> with FCGI) via sudo. > > This is a possible solution, although I would like him to have full > FCGI speed all the time if possible. I wonder how commercial hosters > do this? Anyone with Textdrive experience want to say a few words on > the set-up? Is it CGI or FCGI? > > Nicky > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
> This is a possible solution, although I would like him to have full > FCGI speed all the time if possible. I wonder how commercial > hosters do this? Anyone with Textdrive experience want to say a few > words on the set-up? Is it CGI or FCGI? > > NickyWe use Subversion at our shop, like many Railers. Each developer has a full "server" as their own computer where apache, mysql etc. are installed. Developers update their own copy of the source each day, modify as necessary to get done what they need to, and then commit the changes back to the repository. Then when we want to publish our work to the outside world, we just do an "svn update" on the public server and all of our changes go live. Duane Johnson (canadaduane) _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
Duane Johnson <duane.johnson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:> Then when we want to publish our work to the outside world, we just > do an "svn update" on the public server and all of our changes go > live.If you''re using fcgi do you bounce apache at this point? -- doug-jGAhs73c5XxeoWH0uzbU5w@public.gmane.org
On Jun 17, 2005, at 1:26 PM, Doug Alcorn wrote:>> Then when we want to publish our work to the outside world, we just >> do an "svn update" on the public server and all of our changes go >> live. >> > > If you''re using fcgi do you bounce apache at this point?We have a public development server as well as a production server. I''ve found that quite often, we don''t need to bounce apache on the development server for the changes to work; however, in production mode (on our production server) I''ve had to restart it after an upgrade to get everything right. (If anyone knows of a better solution, I''d like to hear from you). Duane Johnson (canadaduane)
On 15-jun-2005, at 15:25, Nickolay Kolev wrote:> Hi all, > > I have a collocated server where I have set up Apache with FCGI. I > and a friend use it for testing and showing work to clients. He > does PHP mostly so I am in effect the only Rails user on this > machine. Rails runs under FCGI. > > So far I have always developed locally and rsync-ed any changes to > the server. If I happen to have changed models or such I have > restarted apache for rails to pick up the changes. I am root, so I > can do that. > > Now I also want to fix a colleague of mine with some space and the > ability to run rails apps. How should I best handle this? Should I > tell him to always run apps as CGI as opposed to FCGI? Is there a > way to use FCGI and avoid constant reloading of the httpd server > (as he obviously cannot restart the server)? > > Many thanks in advance for an ideas!Do it like it is done on TextDrive. Let him run his own lighttpd and restart it on a privileged port, then proxy it to the main apache instance. -- Julian "Julik" Tarkhanov
This sounds like a good setup. Actually, I did it exactly the same way, but ran into a problem: how can I proxy all subdomains in apache? Now I have: ProxyPass / http://subdomain.hostname.com:1234/ ProxyPassReverse / http://subdomain.hostname.com:1234/ Where 1234 is the port Lighttpd runs on. Anyone an idea how I could "preserve" the "subdomain" while proxying? Thanks in advance, Flurin Egger Julian ''Julik'' Tarkhanov wrote:> > On 15-jun-2005, at 15:25, Nickolay Kolev wrote: > >> Hi all, >> >> I have a collocated server where I have set up Apache with FCGI. I >> and a friend use it for testing and showing work to clients. He does >> PHP mostly so I am in effect the only Rails user on this machine. >> Rails runs under FCGI. >> >> So far I have always developed locally and rsync-ed any changes to >> the server. If I happen to have changed models or such I have >> restarted apache for rails to pick up the changes. I am root, so I >> can do that. >> >> Now I also want to fix a colleague of mine with some space and the >> ability to run rails apps. How should I best handle this? Should I >> tell him to always run apps as CGI as opposed to FCGI? Is there a >> way to use FCGI and avoid constant reloading of the httpd server (as >> he obviously cannot restart the server)? >> >> Many thanks in advance for an ideas! > > > Do it like it is done on TextDrive. Let him run his own lighttpd and > restart it on a privileged port, then proxy it to the main apache > instance. >
On Jun 19, 2005, at 2:33 AM, Flurin Egger wrote:> This sounds like a good setup. Actually, I did it exactly the same > way, but ran into a problem: how can I proxy all subdomains in > apache? Now I have: > > ProxyPass / http://subdomain.hostname.com:1234/ > ProxyPassReverse / http://subdomain.hostname.com:1234/ > > Where 1234 is the port Lighttpd runs on. Anyone an idea how I could > "preserve" the "subdomain" while proxying? > > Thanks in advance, > Flurin EggerProxyPreserveHost On http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#proxypreservehost - Jason
Excellent! Thank you, Flurin Jason A. Hoffman wrote:> > On Jun 19, 2005, at 2:33 AM, Flurin Egger wrote: > >> This sounds like a good setup. Actually, I did it exactly the same >> way, but ran into a problem: how can I proxy all subdomains in >> apache? Now I have: >> >> ProxyPass / http://subdomain.hostname.com:1234/ >> ProxyPassReverse / http://subdomain.hostname.com:1234/ >> >> Where 1234 is the port Lighttpd runs on. Anyone an idea how I could >> "preserve" the "subdomain" while proxying? >> >> Thanks in advance, >> Flurin Egger > > > > ProxyPreserveHost On > > http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#proxypreservehost > > - Jason > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails
> Now I also want to fix a colleague of mine with some space and the > ability to run rails apps. How should I best handle this? Should I > tell him to always run apps as CGI as opposed to FCGI? Is there a > way to use FCGI and avoid constant reloading of the httpd server > (as he obviously cannot restart the server)?On my apache dev box, I''ve always worked around this by killing the dispatch.fcgi process from the shell (it''s running via suexec, so I have permission to it). Since apparently, I''m the only person who does things that way, I gather it must be a bad idea. Is it? :P Tyler