https://github.com/redturtle/wpd2013
WordPloneDay2013 buildout
https://github.com/redturtle/wpd2013
Last synced: about 1 year ago
JSON representation
WordPloneDay2013 buildout
- Host: GitHub
- URL: https://github.com/redturtle/wpd2013
- Owner: RedTurtle
- Created: 2013-04-10T09:27:10.000Z (about 13 years ago)
- Default Branch: master
- Last Pushed: 2013-04-11T13:06:21.000Z (about 13 years ago)
- Last Synced: 2025-02-19T17:10:02.485Z (over 1 year ago)
- Language: Python
- Size: 755 KB
- Stars: 1
- Watchers: 10
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Plone 4 buildout
================
[](https://travis-ci.org/RedTurtle/deployments.buildout.plone)
Introduction
------------
This is the a very basic buildout template
For the impatients
------------------
Make a symlink to the file you want to use (e.g. `development.cfg`) and start the buildout:
```bash
$ ln -s profiles/development.cfg buildout.cfg
$ python2.7 bootstrap.py
$ ./bin/buildout
```
Before you start
----------------
Probably you may want to set up your system and configure some parameters!
Don't forget to read the full documentation.
### Requirements ###
You may want to install this to get this buildout working:
```bash
# python stuff
$ apt-get install python-dev python-virtualenv
# version control stuff
$ apt-get install git subversion
# other stuff
$ apt-get install libjpeg8-dev poppler-utils wv libgeos-c1
```
### Plone version ###
In the file `config/plone.cfg` you may can control the plone version by changing the
__extends__ and __find-links__ variables:
```cfg
extends =
http://dist.plone.org/release/4.2.5/versions.cfg
...
find-links =
http://dist.plone.org/release/4.2.5
...
```
### Virtualenv ###
Using a virtualenv is a good idea:
```bash
# NOTE: --no-site-packages is the default behaviour of the newer virtualenv
# you might remove this parameter if you get an error
$ virtualenv --no-site-packages -p /usr/bin/python2.7 .
$ ./bin/activate
```
### Add additional eggs to Plone ###
Customize the __eggs__ and the __zcml__ variable in the **[plone]** section (a
good place is `config/base.cfg`), e.g:
```cfg
[plone]
eggs+=
my.egg
zcml+=
my.egg
```
### Add development eggs with mr.developer ###
Customize the **[sources]** section (a good place is `profiles/development.cfg`) adding
your checkouts, e.g:
```cfg
[sources]
collective.developermanual = git git://github.com/collective/collective.developermanual.git
```
The provided configuration files
--------------------------------
In the directory `./profiles` you will find configs that can be symlinked in the root of the buildout.
__You shouldn't use directly configuration files that are stored in `config` folder.__
Beneath is the list of available configurations:
### development.cfg ###
This is what the developer wants!
Gives you a standalone Plone instance (no ZEO).
As usual you can launch it with:
```bash
$ ./bin/instance fg
2013-03-22 13:58:39 INFO ZServer HTTP server started at Fri Mar 22 13:58:39 2013
Hostname: 0.0.0.0
Port: 8080
2013-03-22 13:58:44 INFO Zope Ready to handle requests
```
Adds to the buildout development scripts (`test`, `i18ndude`) and to plone some
products (`plone.reload` and `stxnext.pdb`).
Some other are suggested (commented) In the `config/development.cfg` file.
Ask for new stuff if you want (`sauna.reload`, `plone.app.debugtoolbar`, ...).
### production.cfg ###
A ZEO cluster ready for production
Will install:
- zeoserver
- instance1
- debuginstance
- zeopack
- repozo
Note
----
### Versions pinning ###
The buildout prints unpinned versions at the end of the build.
You may want to add them to some cfg file.