Document Actions
Managing projects with zc.buildout
This Tutorial applies to:
Plone 3.0.x
This Tutorial is intended for:
Server Administrators, Developers
Learn about eggs, setuptools and dependency management, and how to use zc.buildout to set up a development environment.
optilude
All content on one page (useful for printing, presentation mode etc.)
- Introduction Or: "What's wrong with a plain old Zope instance"?
- Packages, products and eggs Looking at the core concepts in more detail
- Prerequisites A few things you need before we can get started
- Creating a buildout for your project How to create a new buildout for a project, adding Plone and other third party products as dependencies
- Understanding buildout.cfg How to manage the main buildout configuration file
- Creating a buildout defaults file This makes it possible to share configuration across multiple buildouts, and save some time and disk space.
- Installing a third party product How to install a new package using these tools
- Creating a new package How to add a new egg-based package to your buildout
- A deployment configuration How to use buildout for deployment configuration
by
Martin Aspeli
—
last modified
September 18, 2007 - 21:10
All content is copyright Plone Foundation and the individual contributors.
German translation of this tuturial
Posted by
Andreas Mantke
at
March 6, 2008 - 20:10
First thanks for this tuturial.
In the last days I worked on a german translation of this text. It is now finished and could be found <a href="http://amantke.de/index.php?/content/blogcategory/20/35/">here</a>.
In the last days I worked on a german translation of this text. It is now finished and could be found <a href="http://amantke.de/index.php?/content/blogcategory/20/35/">here</a>.
How to get buildout to connect through a proxy?
Posted by
Jet Wilda
at
May 15, 2008 - 14:30
What if the machine you are installing Plone on doesn't have a direct connection to the internet and must connect through a proxy? How do you test buildout how to get out to the internet?
How to get buildout to connect through a proxy?
Posted by
Cliff King
at
June 24, 2008 - 13:53
Our company has a virus checking firewall. The buildout uses liburl on linux. I exported environment variables to point to the proxy server ip and port, like so:
export http_proxy=http://10.1.200.2:8080
export https_proxy=http://10.1.200.2:8080
export ftp_proxy=http://10.1.200.2:8080
I then ran the buildout tool and the buildout worked as expected. However, the
proxy reported an http 503 error when it was busy doing the virus checking and
this caused some packages to fail to be fetched. I did not fully investigate the
failure reason in buildout, but it appears to be because it treats any return
code that is not success as an immediate failure. That is why the buildout
description says it is not designed to work except through a direct connection
to the internet. After using tcpdump, I was able to determine
the failure reason, and after running the buildout script several times, I was able
to fetch all the packages. Warning: the buildout does not stop fetching packages
on an error, but just continues to fetch following packages and report the buildout
completed. However, the installation will not run, so you must get an error free report
to have a working buildout.
I hope this helps some of you trying this for the first time. I know it has taken a long
time for me to get up and running with buildout.
I did not try to figure out exactly which of the export statements were needed.
Whe
export http_proxy=http://10.1.200.2:8080
export https_proxy=http://10.1.200.2:8080
export ftp_proxy=http://10.1.200.2:8080
I then ran the buildout tool and the buildout worked as expected. However, the
proxy reported an http 503 error when it was busy doing the virus checking and
this caused some packages to fail to be fetched. I did not fully investigate the
failure reason in buildout, but it appears to be because it treats any return
code that is not success as an immediate failure. That is why the buildout
description says it is not designed to work except through a direct connection
to the internet. After using tcpdump, I was able to determine
the failure reason, and after running the buildout script several times, I was able
to fetch all the packages. Warning: the buildout does not stop fetching packages
on an error, but just continues to fetch following packages and report the buildout
completed. However, the installation will not run, so you must get an error free report
to have a working buildout.
I hope this helps some of you trying this for the first time. I know it has taken a long
time for me to get up and running with buildout.
I did not try to figure out exactly which of the export statements were needed.
Whe
website doesn't work
Posted by
Luisa
at
June 13, 2008 - 11:38
http://amantke.de/index.php?/content/blogcategory/20/35/
The requested URL was not found on this server.
The requested URL was not found on this server.
chroot container for Plone buildouts