Hi,
We do the same for our partners.
We work with buildouts stored in our svn.
We have on the same machine several zope with several plone.
On each zope, the plone instances use in majority the same products.
We can hide desired products for the plone manager. Zope manager sees all and can install desired product.
We do a new zope instance when products are too different from existing instances.
The production and test environments are exactly the same.
Regards
Stéphan Geulette
Economisez du papier, n'imprimez ce mail que si nécessaire. Sinon, pensez au recto-verso et à l'impression en plusieurs pages par feuille.
> -----Message d'origine-----
> De :
[hidden email] [mailto:
[hidden email]]
> De la part de NorbertK
> Envoyé : mercredi 5 août 2009 12:09
> À :
[hidden email]
> Objet : [Setup] Q> How to organize several plones ?
>
>
> Hello all,
> I plan to host several plone sites for customers, all of them a little
> different, with different products and theming.
>
> The Box is a linux box with several virtual maschines. I wonder about the
> best way to organize these several Plone Sites during development, staging
> and production.
>
> I assume a version control system for buildouts and own filesystem-based
> products.
>
> I see the follwing options:
> A) 1 Machine - 1 Zope - 1 Plone, either installed as root or as user
>
> B) 1 machine - several Zopes, each with 1 Plone, installed as user
>
> C) 1 machine - x Zopes, each with several Plones.
>
> My thoughts about the alternatives follow and I appreciate any feedback.
>
> Option A seems pretty expensive in terms of ressources but gives a good
> isolation betweeen the instances. Under this aspect it is easy to manage.
> All updates of the lower parts of the software stack (e.g. Zope) must be
> done several times. Seems good for production but a lot of hassle for
> development if one tries to evaluate ideas.
>
> Option B is easier when Zope is not installed as root, less plumbing
> required on the OS level than in option A, same good isolation between the
> instances as in A, same overhead when doing Zope updates.
>
> Option C brings no isolation between the plone instances wrt different
> product versions. Seems not advisable to me.
>
> So the conclusion is : Option A for production, Option B for development
> and
> staging.
>
> Thoughts, ideas ?
>
> How do you guys handle this, especially when you try new ideas ?
>
> Thanks for your time
>
> Norbert
>
>
>
>
>
>
> --
> View this message in context:
http://n2.nabble.com/Q%3E-How-to-organize-> several-plones---tp3390448p3390448.html
> Sent from the Installation, Setup, Upgrades mailing list archive at
> Nabble.com.
>
> _______________________________________________
> Setup mailing list
>
[hidden email]
>
http://lists.plone.org/mailman/listinfo/setup***** DISCLAIMER *****
Ce message électronique et chacune de ses annexes sont établis a l'attention exclusive du destinataire et peuvent contenir des informations confidentielles. Si vous recevez ce message par erreur, veuillez le détruire et avertir son expéditeur. Toute publication, reproduction, copie, distribution ou autre diffusion ou utilisation par des tiers est interdite sans autorisation expresse. L'expéditeur ne peut être tenu responsable d'une modification de son message qui résulterait de la transmission par voie électronique.
_______________________________________________
Setup mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/setup
