This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Project Description

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.

To configure tomcat see the options in the tomcat recipe. For example:

http_port
HTTP Port for Tomcat service. Default: 8080

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
# ncwms
data_root = /var/lib/thredds/data_root
organisation = Birdhouse
allow_wms = true
# tomcat
http_port = 8080

Authors

Carsten Ehbrecht ehbrecht at dkrz.de

Changes

0.3.0 (2015-12-17)

  • install tomcat.

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.
Release History

Release History

0.3.0

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.4

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

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

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
birdhousebuilder.recipe.thredds-0.3.0-py2-none-any.whl (11.9 kB) Copy SHA256 Checksum SHA256 py2 Wheel Dec 17, 2015
birdhousebuilder.recipe.thredds-0.3.0.tar.gz (8.2 kB) Copy SHA256 Checksum SHA256 Source Dec 17, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting