Skip to main content

A Buildout recipe to install and configure thredds server with Anaconda.

Project description

Travis Build

Introduction

birdhousebuilder.recipe.thredds is a Buildout recipe to install and configure Thredds server with Anaconda. This recipe is used by the Birdhouse project.

Usage

The recipe requires that Anaconda is already installed. It assumes that the default Anaconda location is in your home directory ~/anaconda. Otherwise you need to set the ANACONDA_HOME environment variable or the Buildout option anaconda-home.

It installs the thredds and apache-tomcat package from a conda channel in a conda enviroment named birdhouse. The location of the birdhouse environment is .conda/envs/birdhouse. It deploys a Supervisor configuration for Tomcat in ~/.conda/envs/birdhouse/etc/supervisor/conf.d/tomcat.conf. Supervisor can be started with ~/.conda/envs/birdhouse/etc/init.d/supervisord start.

By default Thredds will be available on http://localhost:8080/thredds.

The recipe depends on birdhousebuilder.recipe.conda, birdhousebuilder.recipe.supervisor and birdhousebuilder.recipe.tomcat.

Supported options

This recipe supports the following options:

anaconda-home

Buildout option with the root folder of the Anaconda installation. Default: $HOME/anaconda. The default location can also be set with the environment variable ANACONDA_HOME. Example:

export ANACONDA_HOME=/opt/anaconda

Search priority is:

  1. anaconda-home in buildout.cfg

  2. $ANACONDA_HOME

  3. $HOME/anaconda

data_root

Root Path of data files (NetCDF) for Thredds. Default: ~/.conda/envs/birdhouse/var/lib/pywps/output

organisation

The name of your organisation. Default: Birdhouse

website

The URL of your organisation. Default: None

allow_wms

If set to true Web Mapping Service will be enabled. Default: true.

allow_wcs

If set to true Web Coverage Service will be enabled. Default: false.

allow_nciso

If set to true ISO generator Service will be enabled. Default: false.

Example usage

The following example buildout.cfg installs Thredds with Anaconda and given data_root directory:

[buildout]
parts = thredds

anaconda-home = /home/myself/anaconda

[thredds]
recipe = birdhousebuilder.recipe.thredds
data_root = /var/lib/thredds/data_root
organisation = Birdhouse
allow_wms = true

Authors

Carsten Ehbrecht ehbrecht at dkrz.de

Changes

0.2.3 (2015-12-08)

  • remove config files on uninstall.

0.2.2 (2015-06-17)

  • using tomcat.content_root().

  • cleaned up default configs for thredds.

  • allow more configurations.

0.2.1 (2015-04-02)

  • updated docs.

0.2.0 (2015-02-24)

  • installing in conda enviroment birdhouse.

  • using $ANACONDA_HOME environment variable.

  • separation of anaconda-home and installation prefix.

0.1.4 (2014-12-06)

  • Don’t update conda on buildout update.

0.1.3 (2014-08-27)

  • Added web.xml config template.

0.1.2 (2014-08-01)

  • Updated documentation.

0.1.1 (2014-07-22)

  • Fixed deployment of thredds config.

0.1.0 (2014-07-10)

  • Initial Release.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

File details

Details for the file birdhousebuilder.recipe.thredds-0.2.3.tar.gz.

File metadata

File hashes

Hashes for birdhousebuilder.recipe.thredds-0.2.3.tar.gz
Algorithm Hash digest
SHA256 bbd8df9640a2fa7eb0b20a487fd9d09bf3629e07f9d6e9df5cb1ad7830aea7eb
MD5 a0b78a2506523c8559b3cc7f221900bc
BLAKE2b-256 70987ad9dc731f018f4d1acf9dfc15a818d1e00844bd1b4b45b473c1df36cd69

See more details on using hashes here.

Provenance

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page