Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Package and ship relocatable python virtualenvs, like a boss.
Python Makefile

Merge pull request #55 from PolicyStat/use-travis-env

Parallelize the travis build
latest commit b18fad6a09
@winhamwr winhamwr authored
Failed to load latest commit information.
docs added docs to describe how to upload your terrarium environments onto
requirements Refs #46. Added testing requirements
terrarium
tests added unittest to detect if it will notify user gcloud installation
.gitignore Refs #46. Added docs/_build
.travis.yml Parallelize the travis build
AUTHORS Github profiles are good AUTHOR links
CHANGELOG.rst Changelog for #53
LICENSE Added AUTHORS and LICENSE
MANIFEST.in Refs #49. Added requirements
README.rst Refs #49. Removed several trailing spaces and added a link to the qui…
setup.py Refs #49. Use the README now for pypi's long description
tox.ini Refs #49. Updated docs build to use sphinx-build instead of make html

README.rst

Terrarium

https://pypip.in/v/terrarium/badge.png https://secure.travis-ci.org/PolicyStat/terrarium.png?branch=master

Package and ship relocatable python virtual environments, like a boss.

Terrarium will package up and compress a virtualenv for you based on pip requirements and then let you ship that environment around. Do the complex dependency math one time and then every subsequent install is basically at the speed of file transfer + decompression.

The Problem Terrarium Solves

Pip and virtualenv are awesome, but pip is not designed to allow consistent and reproducible updates of existing environments. Pip is also a general installation tool, meaning that it's not near as fast as shipping around compressed source code. This means that even if you have well-made requirements files, your pip-based deploys are either slow or inconsistent.

To get started using terrarium, see the Quick Start guide.

Something went wrong with that request. Please try again.