Buildout

by Zope Foundation

Python-based build system for creating and deploying applications

Rate Now

(0 Ratings)

Helps with: Build Automation

Similar to:

More...

Source Type: Open

License Types:

Other

Supported OS:

Languages:

Save Unsave Compare

What is it all about?

Buildout is a Python-based build system for creating, assembling and deploying applications from multiple parts, some of which may be non-Python-based. It lets you create a buildout configuration and reproduce the same software later. It implements a principle of separation of configuration from the scripts that do the setting up. Buildout is primarily used to download and set up dependencies in Python eggs format of the software being developed or deployed.

Key Features

* Main Features - Configuration files are INI format. Support for setuptools and eggs Plugin support through Buildout recipes * Buildout is a project designed to solve 2 problems: * Application-centric assembly and deployment * Assembly runs the gamut from stitching together libraries to create a running program, to production deployment configuration of applications, and associated systems and tools (e.g. run-control scripts, cron jobs, logs, service registration, etc.). * Buildout might be confused with build tools like make or ant, but it is a little higher level and might invoke systems like make or ant to get its work done. * Buildout might be confused with systems like puppet or chef, but it is more application focused. Systems like puppet or chef might use buildout to get their work done. * Buildout is also somewhat Python-centric, even though it can be used to assemble and deploy non-python applications. It has some special features for assembling Python programs. It's scripted with Python, unlike, say puppet or chef, which are scripted with Ruby. * Repeatable assembly of programs from Python software distributions * Buildout puts great effort toward making program assembly a highly repeatable process, whether in a very open-ended development mode, where dependency versions aren't locked down, or in a deployment environment where dependency versions are fully specified. You should be able to check buildout into a VCS and later check it out. Two checkouts built at the same time in the same environment should always give the same result, regardless of their history. Among other things, after a buildout, all dependencies should be at the most recent version consistent with any version specifications expressed in the buildout. * Buildout supports applications consisting of multiple programs, with different programs in an application free to use different versions of Python distributions. This is in contrast with a Python installation (real or virtual), where, for any given distribution, there can only be one installed.