Hi Jason,

Thank you very much for your extensive overview. I'll try to give my
thoughts on the subjects mentioned.

I've seperated all modules to administration, backend and frontend
modules. The administration modules are for us, the backend modules
basically are the CMS system and the frontend modules will provide the
datamodel for the website. Because of this separation, an error in a
backend module generally won't affect a frontend module. Right now the
real meat is in the backend modules and the frontend modules are
basically "dumb" data generators. The website will decide what to do
with the data it has received from a frontend module.

Every website will indeed get its own database. I've made a general
datamodel that will gracefully allow updates.

I also use git quite a lot, but currently don't see it as a good
update/package management tool for my needs. I'm not looking forward
to going through all the websites manually and doing a pull/update of
the submodules. Maybe I am missing the knowledge of some git features
to grasp its usefulness in this regard. Could you please elaborate on
your git usage?
My idea was to build a simple version control system into the CMS
itself. Each module has different versions like 'stable', 'testing',
'dev', '1.0' etc. That way I can manage the versions though some
management interface in the CMS. All websites get the 'stable' version
of some module, but I can make an exception for site A, which gets
'dev', the one I am working on currently. When the 'dev' version is
stable enough it gets pushed to 'stable' and the current stable will
be pushed to 'deprecated' or 'old' or something. This is a sort of
rolling release system with per site exceptions.

I should point out that I strive for very contained modules. Except
for some data, they don't have dependencies.

Daan

--

You received this message because you are subscribed to the Google Groups 
"modwsgi" 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/modwsgi?hl=.


Reply via email to