[DRE-maint] Cruisecontrol.rb

[filipe]

On Thu, 19 Apr 2007 11:00:40 -0500, Gunnar Wolf <gwolf at gwolf.org> wrote:
>> These days the most common way to run a rails app is as a separate
>> mongrel process bound to a high port, then proxy requests from
>> apache/lighttpd. At this stage I just have it starting on port 8000 from
>> an init.d script, and there is no automatic configuration of the
>> webserver to proxy connections through.
>> 
>> Although the proxying approach suits me, I'm still new to packaging so
>> I'm unsure if it's suitable for the wider Debian community.
> 
> Again, I hope Filipe can share some insight on this - I think we could
> come to an approach such as:
> 
> - Installed rails apps register somewhere - Say, in
>   /etc/mongrel_cluster/apps_available (and are handled in a way
>   similar to Apache's /etc/apache2/sites_available / sites_enabled)

Yes :D

> - The mongrel package just installs mongrel, but does not start it at
>   all. 
> - The mongrel_cluster package, AIUI, is the one in charge for starting
>   and managing all the different Mongrel processes in the machine. It
>   will start a mongrel for each of said apps

Yeeeees ;D

> - Of course, a way must be found to bind the individual mongrels to
>   the different vhosts of the webserver. That's left for a later
>   moment ;-)

Yes :(

Well, the packages for mongrel and mongrel_cluster are almost ready. I´m just waiting for Zed to upload mongrel 1.0.2, because this release will contain a tgz file and so I can get rid of the code that deals with gem source package.

Also, the files in /etc/mongrel_cluster/sites_enabled are common mongrel_cluster configuration files. And ATM, I´m not creating a way to configure apache throught mongrel_cluster package. Maybe in the future ;)

So, when mongrel and mongrel_cluster be ready, you can depend on then and just configure a simple mongrel_cluster config file in /etc/mongrel_cluster/sites_available.

Bye,

Filipe