[DRE-maint] Re: Mongrel on Debian - wanna join forces?

[Filipe Lautert]

On Thursday 28 December 2006 22:47, Gunnar Wolf wrote:
> Gunnar Wolf dijo [Thu, Dec 28, 2006 at 05:08:23PM -0600]:
> > I see you are not shipping an orig.tar.gz plus your changes in a
> > .diff.gz (that means, you are building a native package). This makes
> > it harder to integrate, so my first step will be to make your package
> > build with the .orig.tar.gz - How will I do this if upstream ships
> > only as a gem? Please don't tell this to anybody, but a gem is just a
> > regular .tar file - So, if you look at my packaging, you will find my
> > debian/rules have some extra targets: Unpack, patch and unpatch. This
> > is because a gem is just a regular .tar file, containing data.tar.gz
> > (the whole contents) and metadata.gz (of course, the gem's
> > metadata). Having an .orig.tar.gz greatly helps keeping the package up
> > to date.
> > (...)
>
> Ok, you have done some nice work - I'll definitively use it! I have a
> question, though: Your init script mentions /usr/bin/pen, which is
> used for running several applications. Of course, your manpage refers
> to pen as well. Have you packaged pen? Or you are using it from a gem
> as well? I fear we will have to package it also...
>

I've been running some servers in sarge using pen and it was fine. But when I 
upgraded to etch and apache 2.2 with modproxy_balancer (so I didn't needed 
pen anymore), even removing the pen configuration port it still using pen for 
my first site configuration. So, how I'd no time when I'd this problem, I 
just removed pen and all went fine :D I think I'll patch this problem now and 
send this patch for you two.

I also have some patches on the init script so you can configure the 
environment you want to run your application (production or development) on 
the site configuration file, then it becomes easy to the system administrator 
to know and change an applications environment. I'll send this patch here 
too.

And more about pen... hum... well... mongrel just will be in etch+1. And so 
there is modproxy_balancer in apache, that replaces pen functionality. So, 
maybe we can strip away pen's configuration? Or maybe should it remain sarge 
and lighttpd compatible (I don't know if there is something like 
modproxy_balancer in lighttpd)?


> Greetings,


see ya

filipe