[Nix-dev] Fwd: Web applications

[Bryce L Nordgren]

Whoops, the list fell off the CC at some point. Sorry.

On Wed, 13 Jun 2012 23:40:52 +0000, Bryce L Nordgren <bnordgren at gmail.com>
wrote:
> On Wed, Jun 13, 2012 at 11:17 PM, Florian Friesdorf <flo at chaoflow.net
>wrote:
>
> > Did you see:
> >
> > /etc/nixos/nixos/modules/services/web-servers/apache-httpd/
> >
> > e.g. trac.nix? What web application are you looking for?
> >
> >
> Actually, I never went into the "apache-httpd" directory because I thought
> it was just the webserver. Does this mean that to deploy trac under any of
> the four alternative webservers, you need to write one nix expression per
> webserver?

It depends how you want to deploy trac. In case of a standalone server:
no; in case of integration with a webserver, e.g. via mod_python, web
server specific config is needed.

> I'm trying to package geonetwork-opensource, which will require a java
> servelet container (any of {tomcat, jboss, jetty, ...}) I'd like to not do
> it more than once if possible.

Is the config specific to tomcat, jboss, jetty?
Yes: pick the one you like
No: create a nix function that can be used with all of them

---------- Forwarded message ----------
From: Bryce L Nordgren <bnordgren at gmail.com>
Date: Thu, Jun 14, 2012 at 4:51 PM
Subject: Re: [Nix-dev] Web applications
To: Florian Friesdorf <flo at chaoflow.net>




> servelet container (any of {tomcat, jboss, jetty, ...}) I'd like to not do
> > it more than once if possible.
>
> Is the config specific to tomcat, jboss, jetty?
> Yes: pick the one you like
> No: create a nix function that can be used with all of them
>
>
The answer is ideally "no", but usually yes. Things like backend
connections to the database, user store (LDAP/AD/Kerberos) and
configuration of items specific to the application are independent of the
container. Things like "deploy this WARfile (or directory) to this URL" are
usually container specific, but common enough that I can envision a
standard interface implemented by all servers of a particular type. Then
there's highly specific things like adding to the apache/tomcat/jetty/jboss
configuration (merging the configuration snippets with snippets from other
webapps, of course).

The trick would be to separate the common stuff from the container-specific
stuff, and getting the container to aggregate configuration from all of the
webapps deployed in it.

Bryce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20120614/2939ec2b/attachment-0001.html