A working Plone 2.5.5 buildout

On a recent project I needed to get Plone 2.5.5 up and running. This is a note to self so I can get it done more quickly next time. It also reminds me how far we've come from the Plone 2.5.5 and early buildout days.

As a starting point I needed a "known good Plone 2.5.5 buildout" I borrowed most of ideas from this Venezuelan repository: http://plataforma.cenditel.gob.ve/browser/proyectosInstitucionales/eGov/ppm/buildout/plone/2.5/buildout.cfg?rev=137. After reading around I mixed and matched and came up with this template: https://gist.github.com/pigeonflight/5268138 (I consider it good enough for a developer to get started)

Use collective buildout.python for building a suitable  Python 2.4

I did the following as the root user (Takes about 40 minutes to compile on an Amazon EC2 micro instance)

cd /usr/local git clone https://github.com/collective/buildout.python.git python cd python python bootstrap.py

Edit 'buildout.cfg' so that parts and eggs only reference python 2.4

extends =    src/base.cfg    src/readline.cfg    src/libjpeg.cfg    src/python24.cfg    src/links.cfg parts =    ${buildout:base-parts}    ${buildout:readline-parts}    ${buildout:libjpeg-parts}    ${buildout:python24-parts}    ${buildout:links-parts}

Then run buildout

bin/buildout  bin/install-links

As the Plone user download the custom buildout.cfg run the following commands

Get the custom buildout.
          wget https://gist.github.com/pigeonflight/5268138/raw/27f2f61e4a51d6822816a9c451d6ae35583184bf/buildout.cfg

/usr/local/python/bin/virtualenv-2.4 .bin/easy_install zc.buildout==1.4.4          # this line below does a little dance (to take advantage of buildout init) mv buildout.cfgzz && bin/buildout init && mv buildout.cfgzz buildout.cfg bin/buildout

The result should be a working Plone 2.5.5.

I plan to customize this for production (yes, they are still using Plone 2.5.5).