As I've been working on rewriting the deployment documentation, I've
wound up with quite a few changes/enhancements to modwsgi_deploy. The
changes:
* parameterized to allow most options to be configured on the
command line
o logging on/off
o virtualenv (location)
o baseline virtualenv (location)
o deployment path (location)
o mount-point (web url for the app)
o virtual host (i.e. the vhost name)
o embedded mode (should someone need it)
o config-file name
* supports generation for any Python version (and you can override
to generate for a different Python version), basically a bug-fix
* shorter templates with a single base pattern that is tweaked by
the parameters
o less text in the final files, so hopefully easier to understand
* reports missing configured elements with basic instructions on how
to create the missing elements (virtualenvs, config-files)
So, if you're using (or have used) modwsgi_deploy, please consider
checking out and installing this branch (in your virtualenv, of course):
bzr branch
http://bazaar.launchpad.net/~mcfletch/modwsgideploy/parameterized/
cd parameterized/trunk
python setup.py develop
paster modwsgi_deploy --help
You'll want to make sure your project/apache/ directory is version
controlled before you actually generate any configurations.
I tend to use a bog-standard Apache VirtualEnv + BaseLine + VirtualHost
environment, so I could use help testing from people who:
* use system-python packages (likely RHEL users)
* use virtualenv, but don't use a baseline
* use non-Debian/Ubuntu hosts
* mount their applications at /application instead of as the root of
a site
The package won't work properly on Win32 at the moment (just due to
using '/' in the default file paths). I'm guessing that Win32 users
generally don't use Apache much anyway, so it's likely not worth fixing
that. The goal of the branch is to make the documented "standard"
installation process simple enough that I'm not writing pages and pages
of dense prose just to describe something that takes a few lines of
Python to automate. I would *like* it to be possible to say:
install this package
run this script with --help to see options
run this script with your desired options
look for warnings, follow their guidance
now copy the file into the apache folders and run a2ensite
and have the whole thing work for the "normal" case (i.e. a virgin
Apache install on a virgin Linux host).
Thanks all,
Mike
--
________________________________________________
Mike C. Fletcher
Designer, VR Plumber, Coder
http://www.vrplumber.com
http://blog.vrplumber.com
--
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en.
