Download 
Lastest release
This recipe allows you to download, install and configure a Geoserver instance through zc.buildout.
Usage
This recipe exists to give you a way to have an integration set of directives to have a Geoserver instance ready into your buildout.
The basic usage of this recipe is as follows:
[buildout]
parts = geoserver
[geoserver] recipe = geoserver.recipe url = http://downloads.sourceforge.net/geoserver/geoserver-2.0.2-bin.zip server-port = 8099
As you see, in the basic usage you need just to specify the port you want the server to use.
Anyway, no tons of options are needed actually, but recipe infrastructure gives most of the flexibility you could need to improve it.
Links
- Code repository: http://gitorious.org/djc-recipe/djc-recipe
- Report bugs at http://open.abstract.it/it/progetti/rilasci-abstract/djc.recipe/issues
- Comments and questions at info@abstract.it
Detailed Documentation
General options
The present recipe downloads, installs and configures a geoserver (http://geoserver.org) instance.
It is based on two recipes:
It uses the former one to download and decompress the package, and the latter one to produce one of the configuration files geoserver uses, jetty.xml.
At this stage, the accepted options are:
url
This is the url of a binary version of Geoserver. Example:
url = http://downloads.sourceforge.net/geoserver/geoserver-2.0.2-bin.zip
server-port
This is the port you want the server to use. Example:
server-port = 10002
Template file
The template file is stored into the templates directory, named jetty.xml.template. The only parameter actually processed is server-port.
If you want to add some custom configuration to this file, you have to Contributors ********
Desiderata
Some of the future features can could be added:
In case of an explicit input variable in the part, we could give the recipe a different source template, to customize different setting.
Buildout configuration example:
[buildout] parts = geoserver
[geoserver] recipe = geoserver.recipe url = http://downloads.sourceforge.net/geoserver/geoserver-2.0.2-bin.zip server-port = 8099 realm-name = MYVAL input = path/to/geo_template.in
Snippet of template file example (geo_template.in):
<!-- =========================================================== --> <!-- Configure Realms --> <!-- =========================================================== --> <Set name="UserRealms"> <Array type="org.mortbay.jetty.security.UserRealm"> <Item> <New class="org.mortbay.jetty.security.HashUserRealm"> <Set name="name">${geoserver:realm-name}</Set> <Set name="config"><SystemProperty name="jetty.home" default="."/>/etc/realm.properties</Set> </New> </Item> </Array> </Set>
This would produce a new jetty.xml, giving the chance to map different variables to into the configuration file.
successful builds