Deployment Plans

Zine has a very flexible deployment so that it should run everywhere (even if it does not do that currently). It tries to integrate well into different environments and for that matter we have an abstraction for all deployment specific things. Currently the following deploy schemes exist:

• POSIX. If installed with make install Zine goes into POSIX deployment mode. It will install itself into $PREFIX/lib/zine and put shared data such as the default templates and htdocs into $PREFIX/share/zine.
• Development. This is the "deployment mode" for developers. It sticks to what you know from normal Python. Everything is stored inside the zine package and you can move it around on the $PYTHONPATH as you like. Deployment mode is selected if Zine finds the sahred data inside the zine package.

The following deployment modes will follow in future releases:

• DMG. We don't know how useful this is as the POSIX deployment works for OS X as well but a .dmg installation would be possible. So OS X Server administrators only have to drag the .app in the .dmg somewhere, open up the application and a configuration wizard appears to create Zine instances and configure the Apache.
• Kitchen Sink. For shared hosting and similar stripped-down environments it would be neat to create a package for Zine and upload that to the server with all dependencies. Biggest problem for that are currently database drivers and lxml which are binary packages as well as figuring out how to hook into the webserver.

If you want to add a new deployment mode have a look into environment.py and extend it.