This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

python-django-repomgmt

This Django app implements everything you need to create APT repositories, buildd infrastructure as well as automatic package building.

It expects access to an OpenStack Compute cloud to perform builds and uses reprepro on the backend to manage the APT repositories, process incoming, etc.

Setting it up should be fairly simple.

You need Django, django-tastypie, django-celery, sbuild and devscripts installed.

These are the configuration options you need to add to your settings.py:

APT_REPO_BASE_URL

The base URL by which your repositories will be reachable.

E.g. if set to http://apt.example.com/, it’s assumed that your web server is configured to expose e.g. the “cisco” repository under http://apt.example.com/cisco

POST_MK_SBUILD_CUSTOMISATION

An argv to be executed in the schroot after mk-sbuild is done.

E.g. to avoid using a proxy for a apt.example.com, you can do something like:

POST_MK_SBUILD_CUSTOMISATION = [‘bash’, ‘-c’, ‘echo ‘Acquire::HTTP::Proxy::apt.example.com “DIRECT”;’ > /etc/apt/apt.conf.d/99noproxy’]

BASE_URL

The base URL of the repomgmt app. This is used to construct URLs where build nodes can fetch their puppet manifest.

BASE_TARBALL_URL

A URL where the generated tarballs can be found. The tarballs generally land in /var/lib/schroot/tarballs, so you should configure a web server to serve that directory at this URL.

BASE_REPO_DIR

The base directory where the repositories should be kept. Each repository will be represented by a subdirectory here.

It is also expected that django-celery is already configured. This should be as simple as adding something like this near the end of your settings.py:

INSTALLED_APPS += (“djcelery”, ) import djcelery djcelery.setup_loader()

BROKER_URL = ‘amqp://guest:guest@localhost:5672/’

Release History

Release History

0.1.1

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

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
django-repomgmt-0.1.1.tar.gz (106.4 kB) Copy SHA256 Checksum SHA256 Source Nov 2, 2012

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development 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