devpi-server 0.8.4

devpi-server: reliable fast pypi.python.org caching server

• issues: https://bitbucket.org/hpk42/devpi-server/issues

• IRC: #pylib on irc.freenode.net.

• repository: https://bitbucket.org/hpk42/devpi-server

• mailing list: https://groups.google.com/d/forum/devpi-dev

devpi-server is an easy-to-use caching proxy server for pypi.python.org, providing fast and reliable installs when used by pip or easy_install.

devpi-server offers features not found in other PyPI proxy servers:

• transparent caching of pypi.python.org index and release files on first access, including indexes and files from 3rd party sites. Automatic updating of cached indexes using using pypi’s changelog protocol, making sure you’ll always see an up-to-date view of what’s available.

• server-side crawling using pip’s link extraction allows client-side pip/easy_install/buildout tools to avoid all crawling, thus providing lightning-fast and reliable installation (on second access of a package). And repeatable offline installs.

• devpi-server --gendeploy=TARGETDIR creates a zero-configuration deployment for your (unixish) laptop or a server, fully contained in a virtualenv directory, controlled by TARGETDIR/bin/devpi-ctl, a thin wrapper around a dedicated supervisord. You’ll also find templates for nginx and a user crontab to start permanent deployment at system boot time under a nice looking URL.

• devpi-server contains an extensive automated test suite to help continued improvements without regressions.

To summarize, devpi-server aims to help you and your company handle all installation interactions with pypi.python.org in the most reliable and fastest way possible.

Getting started, trying it out

Simply install devpi-server via for example:

pip install devpi-server # or
easy_install devpi-server

Make sure you have the redis-server binary available and issue:

devpi-server

after which a http server is running on localhost:3141 and you can use the following index url with pip or easy_install:

pip install -i http://localhost:3141/ext/pypi/simple/ ...
easy_install -i http://localhost:3141/ext/pypi/simple/ ...

permanent pip configuration

To avoid having to re-type the URL, you can configure pip by setting:

• the index-url entry in your $HOME/.pip/pip.conf (posix) or $HOME/pip/pip.conf (windows):

  # content of pip.conf
  [global]
  index-url = http://localhost:3141/ext/pypi/simple/

• export PIP_INDEX_URL=http://localhost:3141/ext/pypi/simple/ in your .bashrc or a system-wide location.

Example timing

Here is a little screen session when using a fresh devpi-server instance, installing itself in a fresh virtualenv:

hpk@teta:~/p/devpi-server$ virtualenv devpi >/dev/null
hpk@teta:~/p/devpi-server$ source devpi/bin/activate
(devpi) hpk@teta:~/p/devpi-server$ time pip install -q \
            -i http://localhost:3141/ext/pypi/simple/ devpi-server

real 21.971s
user 1.564s
system 0.420s

So that took 21 seconds. Now lets remove the virtualenv, recreate it and install a second time:

(devpi) hpk@teta:~/p/devpi-server$ rm -rf devpi
(devpi) hpk@teta:~/p/devpi-server$ virtualenv devpi  >/dev/null
(devpi)hpk@teta:~/p/devpi-server$ time pip install -q -i http://localhost:3141/ext/pypi/simple/ devpi-server

real 1.716s
user 1.152s
system 0.472s

Ok, that was more than 10 times faster. The install of devpi-server (0.7) involves five packages btw: beautifulsoup4, bottle, py, redis, requests.

deploying permanently on your laptop

devpi-server is not only a fast pypi cache but since version 0.8 it comes with a zero-configuration way to deploy permanently on a laptop or even a server. If you type:

$ devpi-server --gendeploy=TARGETDIR [--port=httpport] [--redisport=port]

You will have a fully self-contained directory (a virtualenv in fact) which is configured for supervising a continued run of devpi-server. If you set an alias like this (in your .bashrc for permanence):

$ alias devpi-ctl=TARGETDIR/bin/devpi-ctl

you have a tool at your finger tips for controlling devpi-server deployment:

$ devpi-ctl status    # look at status of devpi processes

$ devpi-ctl stop all  # stop all processes

$ devpi-ctl start all # start devpi-server and redis-server

$ devpi-ctl tail devpi-server  # look at current logs

$ devpi-ctl shutdown  # shutdown all processes including supervisor

In fact, devpi-ctl is just a thin wrapper around supervisorctl which picks up the right configuration files and ensures its supervisord instance is running.

You can now uninstall devpi-server from the environment where you issued ``–gendeploy`` because the created environment contains all that is needed.

Lastly, if you want to have things running at system startup and you are using a standard cron, a modified copy of your user crontab has been amended which you may inspect and install with:

$ crontab TARGETDIR/etc/crontab

If you prepared your pip configuration, you will now benefit from a permanently fast pip installation experience, including when on travel with your laptop.

But wait, what if you want to install this on a server in your company? If you are using nginx, you may:

modify and copy TARGETDIR/etc/nginx-devpi.conf to
/etc/nginx/sites-enabled/

and serve your devpi-server deployment to the whole company under a nice looking url.

If you look into the TARGETDIR/etc/supervisord.conf and read up on supervisor, you can modify the configuration to your liking. If you prefer different schemes of deployment you may consider it “executable” documentation.

Compatibility and perequisites

Other than a few automatically installed python dependencies, devpi-server currently requires:

• Unix or Windows. Windows support is somewhat experimental and you need to configure your own deployment.

• python2.6 or python2.7.

• redis-server version 2.2 or later. Earlier versions may or may not work (untested). By default, devpi-server configures and starts its own redis instance. For this it needs to find a redis-server executable. On windows it will, in addition to the PATH variable, also check for c:\\program files\redis\redis-server.exe which is the default install location for the windows redis fork installer.

command line options

A list of all devpi-server options:

$ devpi-server -h
usage: devpi-server [-h] [--version] [--datadir DIR] [--port PORT]
                    [--refresh SECS] [--gendeploy DIR]
                    [--redismode auto|manual] [--redisport PORT]
                    [--bottleserver TYPE] [--debug]

Start an index server acting as a cache for pypi.python.org, suitable for
pip/easy_install usage. The server automatically refreshes the cache of all
indexes which have changed on the pypi.python.org side.

optional arguments:
  -h, --help            show this help message and exit

main:
  main options

  --version             show devpi_version (0.8.2)
  --datadir DIR         data directory for devpi-server [~/.devpi/serverdata]
  --port PORT           port to listen for http requests [3141]
  --refresh SECS        interval for consulting changelog api of
                        pypi.python.org [60]

deploy:
  deployment options

  --gendeploy DIR       (unix only) generate a pre-configured self-contained
                        virtualenv directory which puts devpi-server and
                        redis-server under supervisor control. Also provides
                        nginx/cron files to help with permanent deployment.
  --redismode auto|manual
                        whether to start redis as a sub process [auto]
  --redisport PORT      redis server port number [3142]
  --bottleserver TYPE   bottle server class, you may try eventlet or others
                        [wsgiref]
  --debug               run wsgi application with debug logging

Project status and next steps

devpi-server is considered beta because it just saw the first releases and still needs more diverse testing.

It is tested through tox and has all of its automated pytest suite passing for python2.7 and python2.6 on Ubuntu 12.04 and Windows 7.

devpi-server is actively developed and bound to see more releases in 2013, in particular for supporting private indexes and a new development and testing workflow system. You are very welcome to join, discuss and contribute, see the top of of this page for contact channels.

0.8.4

• use pip’s link parser rather than beautifulsoup to benefit from link parsing code tested out and maintained in the wild. Adapt README.

• skip a test if crontab command is not present

  (thanks Markus Zapke-Gruendemann)

• release 0.8.3 is not useable

0.8.2

• fix issue6 - some edge cases for link parsing uncovered by BeautifulSoup and CouchApp installs. Thanks Anton Baklanov.

• fix issue5 - require minimal versions for deps, thanks Andi Albrecht

• remove superflous include lines in MANIFEST.in

0.8.1

• fix: change gendeployed supervisord.conf to not autostart processes on “devpi-ctl” invocations. “devpi-ctl help” would autostart the processes after a shutdown which is not very intuitive. This is actually compatible with the documentation.

• refactor –gendeploy related code to be in gendeploy.py

• fix: fixate path of devpi-server in gendeployed configuration to point to the freshly installed devpi-server. also add a note to the README.

0.8

• introduce “–gendeploy=TARGETDIR” for generating a virtualenv directory with supervisor-based configuration in TARGETDIR/etc and a TARGETDIR/bin/devpi-ctl helper to control the running of devpi-server and redis-server processes.

• fix issue4: keep the “changelog” thread active across network/reachability errors. Thanks Laurent Brack.

• use argparse instead of optparse, simplify and group options

• fix python2.6 and simplify logging configuration

0.7

• Initial release