Re: Deploying Plack apps
- To: email@example.com
- Subject: Re: Deploying Plack apps
- From: Kjetil Kjernsmo <firstname.lastname@example.org>
- Date: Thu, 08 Mar 2012 22:01:02 +0100
- Message-id: <1334114.katRl7mmpO@owl>
- In-reply-to: <CAKTje6GLAgKH4J15gam=Fi_U6V9wrqf6WtkvpDs54s4z1otfTg@mail.gmail.com>
- References: <3416810.09paTh2efV@owl> <CAKTje6GLAgKH4J15gam=Fi_U6V9wrqf6WtkvpDs54s4z1otfTg@mail.gmail.com>
On Wednesday 7. March 2012 07.34.19 Paul Wise wrote:
> There is wwwconfig-common, which was designed for the webserver side
> of your question.
So, that could in principle be extended to accommodate for all the different
deployment options of Plack apps?
> Here is my standard rant about web-based software & Debian, please consider
> There is no way to know which filesystem path, database names, domain
> name and HTTP path the sysadmin wants a web-based app to be run at.
> Ideally, in the upstream code there would be a script/command that can
> be used to setup an instance of the software at a particular URL, with
> data stored in particular locations.
> Ideally, in the relevant Debian package there should be debconf
> prompts that act as input about whether to run and how to run the
> upstream instance setup script.
Yeah, that'd be nice. I don't know how easy it would be to get upstreams
(beyond myself) to support something like that, but at least, it is worth
thinking about, especially if it is doable for Wheezy.