Re: zc.buildout for ZMS development
Niels Dettenbach <[email protected]> Tue, 18 Jan 2011 11:34:15 +0100
| Newsgroups | gmane.comp.cms.zms.devel |
|---|---|
| Organization | Syndicat IT&Internet |
| Message-ID | <[email protected]> |
Am Samstag 15 Januar 2011, 02:18:25 schrieben Sie: > is anybody on the list using zope 2.12.x or higher to run ZMS on it? Yes, we have several ZMS installations built on ZMS 2.12 and a few in "beta" status on 2.13. > My > intention is to use some zope2 packages, recently transformed to python > eggs, that would help ZMS in adopting the latest improvemens made by > zope core developers. Examples are packages that support pluggable > authentication, advanced indexing and querying and last but not least a > more recent version of ZODB with efficient support for binary large > objects (BLOBS). hmmm, im highly interested too here as it allows to "package" a Zope / ZMS installations and ZMS 2.12 / 2.13 brings very interesting new features we still rely on in different projects. Unfortunately it seems to me that there are a few things still not really stable within 2.13 and even 2.12 as in older versions - i.e. under longer high load (including ZMS writes - without workflow) there are ZOPE / ZODB crashes sometimes. It seems to that newer ZMS are more sensible here to programming bugs i.e. within own objects / extensions or templates as they may lead to a complete crash of the ZOPE / ZODB instance. Activating / using cache seems to rise such "collisions" too. Migrated ZMS instances to 2.13 or 2.12 often get a problem with the user / access management - it is not possible to edit / save any user record (i just get a field "content" with no error when try to save new or modified users). Fopr me it seems that the upgrade mechanism is not working properly in all cases here. There are a few other small things which could be a "bug" - i.e. the Explorer- Frame seems not work in any browser as before and there are some functions which seems not allow the usage of a non standard HTTP port (the port part is not processed properly within VirtualHost configs). May be this is related to the fact that i use Unix / Linux hosts as afaik ZMS devels mainly use Windows machines or that i did anything incorrect here. My possibly subjective experience here is that ZMS >=2.12 are a little bit "slower" then typical 2.9 / 2.10 instances we run - related to the fact that the newer (much more flexible) ZMS concept usually relys on more HTTP-requests per page then older ZMS. I'm happy about any help or hint about this topics here or open in help troubleshooting here... > I am trying to setup a buildout-based zope instance with Zope 2.13.1 as > it is documented here: > http://docs.zope.org/zope2/releases/2.13/INSTALL-buildout.html Yes, id did this - even for my own developed ZOPE apps as ZMS instances too. But it takes a little to read and/or try to get all the required additional components installed to run a "typical" ZMS installation and/or want to migrate an older one. best regards, Niels. -- --- Niels Dettenbach --- Syndicat IT&Internet http://www.syndicat.com T.-Muentzer.-Str. 2, 37308 Heilbad Heiligenstadt - DE --- Kryptoinfo: PGP public key ID 651CA20D Fingerprint: 55E0 4DCD B04C 4A49 1586 88AE 54DC 4465 651C A20D https://syndicat.com/pub_key.asc ---
signature.asc
(application/pgp-signature, 836 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iQIcBAABCAAGBQJNNWyrAAoJEM78prARigUn3XoP/0kR5msNH0zhstGiESOSnaHh 4RNgH+7Eoyy5FnuNCkFjqDQFpynwJfwwMomFcd2elsvdaNMOe1cSAU6bCcORBfyl fsDa5kMfG/mF5OhEgzk+MJpeedf/pBKxuNXZyli3pO76TlB9THXPnUaIXiGz59SL 4MyZm88vKgQ7fozRn23Wm0rfs+FdGevMPtkfxNmUeezn6SdfxHqlNitvFOOpL2vx ESKNOWTKcZl72mXs5LkZ1yRlSVH+eYnNX8SYIeW7eTiaX5eNo90yifMqP7M4cI3B bW1UnyPLgwgSCkV9YCIfv/TsJJ1uCeQLWWwdjp34PORU/4+/TAm0FQ3CWusm2WEC +bys2ngki0hZ0OxiM7iX4wfc1iI1UtecMHZ0MsXB0Rg0YP7PD07SGvOTc7dtHNqX n1bBU7oeF80soqHoHOlSLxKbcDOnwiZVzIr91Lp2AtZv/A5vbQpWE2xzJFqLP7YL ubuUqS0AjqiYgZ/KM29JyyalHknntNJoOM7hX+iPKbOowBq33Q3XhSdjxGBQgfBJ N1VHqmAhxqw+ZSrttPBZkz5v2jPbTu53KFHKAiAd2PMBMPuhsHwvwJ0COPIX+liY /Cp0niqcfr1IGrHTY4V89zVTkbPzg1y4Yi2ug9YqtDrNM0N30xnLUApp03NjznBs aYkyiijMsxXS1LOoua6L =vjhK -----END PGP SIGNATURE-----