On Feb 12, 2008 5:25 PM, Joshua Miller <[EMAIL PROTECTED]> wrote:
> Developing on a central server is nice for dmz'd db access, and it saves
> each dev from installing all the perl libs, apache, etc, on their own box
> (or vm).
There's also CGI::Application::Server (which uses
HTTP::Server::Simple
Developing on a central server is nice for dmz'd db access, and it saves
each dev from installing all the perl libs, apache, etc, on their own box
(or vm).
However, you'll have issues with multiple versions of libraries if running
like:
> http://www.our.server/cgi-bin/developer1/my-app.cgi
> http
Barry Moore said:
> Hi all,
>
> I've been developing web apps with cgi-app for several years now, but
> for the first time I'm coordinating a project that will involve
> several developers, and I'm trying to think about how best to
> structure things - particularly in regards to version control.
>
Hi all,
I've been developing web apps with cgi-app for several years now, but
for the first time I'm coordinating a project that will involve
several developers, and I'm trying to think about how best to
structure things - particularly in regards to version control.
I've got three develop
On Mon, 2008-02-11 at 10:03 +, Mark Knoop wrote:
Hi Mark
> Ok. This is as I thought but it is very useful to have it confirmed in such
> a clear and concise manner.
Thanx.
> stuff so I would be interested to know if this is a common practice or if it
> is considered overkill. I have gone
