Blog Entry 12 years, 10 months ago

Create separate Plone environment

In the waiting of my new Plone buildout complete, I noted down some of my steps to create a new environment for developing Plone products. If the current user doesn't have enough permission to install package to common location live /usr/local/... or you don't want to mess up that place by future tweaks, test libraries, or do not want your products to deal with unexpected conflicts from global settings, you should separate your developing environment.

In the waiting of my new Plone buildout complete, I noted down some of my steps to create a new environment for developing Plone products. If the current user doesn't have enough permission to install package to common location live /usr/local/... or you don't want to mess up that place by future tweaks, test libraries, or do not want your products to deal with unexpected conflicts from global settings, you should separate your developing environment.

This one is the good choice: http://www.virtualenv.org/en/latest/

Not using that one above, here is my work:

1. Create new user, name it 'plone' (give it a new password if needed):

# useradd -m plone

2. At plone, download the packages Python 2.6, Zlib, setuptools, PIL.

3. At first installation step of  Python and Zlib, specify the --prefix parameter before "make" and "make install"

$ ./configure --prefix=/home/plone/
$ make
$ make install

4. After having Python successfully installed, let's move to setuptools:

$ /home/plone/bin/python setup.py build
$ /home/plone/bin/python setup.py install

5. Almost done now. Next is the ZopeSkel:

$ /home/plone/bin/easy_install ZopeSkel

6. Now you are ready to create the new Plone buildout using paster:

$ paster create -t plone4_buildout

7. Final steps, inside the newly created buildout directory:

$ /home/plone/bin/python bootstrap.py
$ ./bin/buildout -v

That it is. The buildout process is now running, no... walking. Let's take a nap.

Recent Reads