GNOME Bugzilla – Bug 454602
Documentation: Deployment needs documentation
Last modified: 2011-04-21 07:08:58 UTC
There should be a live.gnome.org page that says how to install the new www.gnome.org. I'm not a sysadmin, but I think this should include - The precise Plone version used. - The theme used, as a tarball, with precise instructions for integrating it with the Plone installation. - The precise versions of any Plone extras/plugins used. - Precise details about any other customizations. - The content (a database backup?) in a tarball, with precise instructions for installing it so that it appears in the website. This should allow a non sysadmin idiot (for instance, me) to install the website.
Also: - How to ensure that the database content is backed up regularly.
One of the common ways to make this part is creating a svn with all the products and the plone: trunk/PloneCommon trunk/Developed trunk/ThirdParty These three folders store all the products that make the plone as it is, so you can co from the svn ( using tags to make a stable snapshot of all the mess ). There are a lot of important things to know about deployment : * The front-end * The Cache * The loadbalancer * The ZEO/ZOPE configuracion The best aproach is : * A frontend using apache for virtualhosting ( http - www / https - edit ) * a Loadbalancer ( pound or perlbal ) ( www to 2 zope clients ) * a cache ( 1 for each of this 2 zope cleints ) * 1 zeo and 3 zope ( 2 for www and 1 for edit without cache ) All the configuration files should go to svn. About the content we are going to use the gsxml that enable export to xml of all the content.
Obviously the deployment instructions are a blocker to deployment. Marking this as a blocker.
Deployment ---------- An repeatable deployment is done with `buildout` which lists pinned versions - in the buildout configuration (*.cfg in the buildout directory), - in the setup.py-files in the wgo.* packages (automatically recognized by buildout) Other dependencies and install instructions are listed in the README of the buildout http://dev.plone.org/collective/browser/gnomeweb-plone/buildout/trunk/README.txt. The documentation is refered from http://live.gnome.org/GnomeWeb/CmsSetup under "Installing a local Sandbox". Generic backup documentation is available on plone.org, special backup documentation should be written together with the sysadmin-team at a later stage. This is also true for the documentation to integrate the running plone into the gnome website infrastructure. Release tarballs ---------------- Python packages are delivered in .egg-files, a zipped package format like java jars. We'll do them for later releases. Currently we just tag releases in svn and include them as svn:externals. For later versions we can do tarballs from fresh buildout also. Does the documentation hould we leave this ticket open as a reminder
Carsten, could we make sure this is documented in http://live.gnome.org/GnomeWeb/Plone?
Can we close this now that the Plone attempt is dead?
Yes.