Pylons apps on aspen
iGL
I have added another branch: iGL-aspylons that is to run pylons apps.
There are example configs in etc and aspylons.py in lib/python2.x.
README describes how to set up.
I test it against pylons doc's quickwiki - runs as it has to. The task
was simplified as pylons encourages to run its static content via app
server; therefore, no extra steps're required to serve static content.
Would you take a look and give me feedbacks?
greetings,
giorgi
Chad Whitacre
> I have added another branch: iGL-aspylons that is to run pylons apps.
> There are example configs in etc and aspylons.py in lib/python2.x.
Sweet! Thanks for your work!
I've been looking for a way to include adapters for popular
frameworks out of the box. I think we're discovering how to make
this work. Consider:
- an aspen.frameworks subpackage
- one module per framework: aspen/frameworks/django.py
- in each module, one WSGI callable per version, v0_96_1
- the WSGI app for the latest/default version should be 'wsgi'
- callables are aliased if unchanged: wsgi <= v0_96_1
- so instead of having separately-maintained shims for each
framework, we bundle as many as we can
- for each framework shim, we document aspen.conf settings
- site devs are then responsible for wiring up in apps.conf:
/ aspen.frameworks.django.v0_96_1
- and of course, the framework must be on PYTHONPATH
What do you think? Could this work?
chad
iGL
sounds nice. I guess it'll work ok.
giorgi