source: publico/il.spdo/trunk/il/spdo/buildout/buildout.cfg @ 5357

Última Alteração nesse arquivo desde 5357 foi 5357, incluída por fabianosantos, 8 anos atrás

Armazenada uma copia dos arquivos do buildout no svn

File size: 6.5 KB
Linha 
1############################################
2#
3# Buildout Configuration File for Standalone Plone
4# ------------------------------------------------
5# $LastChangedDate: 2011-07-18 16:04:13 -0700 (Mon, 18 Jul 2011) $ $LastChangedRevision: 51292 $
6#
7# After making changes in this configuration file,
8# you should run bin/buildout to update the components.
9#
10# ALWAYS back up all Plone/Zope data and components
11# before changing configuration.
12#
13# Running "bin/buildout" will update your installation,
14# installing missing components as necessary.
15#
16# Use "bin/buildout -n" to update many components here to the newest
17# available releases.
18# This will update the add-on products you've added in the eggs= lines.
19# This will not, however, upgrade Plone itself (or anything else you've
20# pinned with a version specification). To upgrade Plone itself, see the
21# comments in "Plone Component Versions".
22#
23# Tutorial instructions for using zc.buildout for
24# configuration management are available at:
25# http://plone.org/documentation/tutorial/buildout
26# Full details at http://pypi.python.org/pypi/zc.buildout
27#
28############################################
29
30
31[buildout]
32
33############################################
34# Plone Component Versions
35# ------------------------
36# This version of the Unified Installer has the components of Plone 4
37# preloaded so that it can install without an Internet connection.
38# If you want to update, uncomment the "http://..." line below,
39# edit it to point to the current version URL, comment out the
40# "versions.cfg" line and run "bin/buildout" while attached to the
41# Internet. Generally, you only want to do that as part of a planned migration.
42# Note that if you are updating components, you should also check the versions
43# section at the end of this file, since recipes or components other than
44# those of Zope and Plone may need updating at the same time.
45#
46extends =
47    base.cfg
48    versions.cfg
49    http://good-py.appspot.com/release/plone.app.theming/1.0b8
50    http://good-py.appspot.com/release/five.grok/1.2.0-1
51    http://good-py.appspot.com/release/plone.app.z3cform/0.5.6-1
52    spdo.cfg
53#    http://dist.plone.org/release/4.1-latest/versions.cfg
54
55
56############################################
57# Ports
58# -----
59# Specify the port on which your Zope installation
60# will listen:
61http-address = 8080
62
63
64# If you try to start Zope as root, it will change user id to run as
65# the effective user specified here. This user id must own the var directory
66# of your buildout.
67effective-user = plone
68
69
70############################################
71# Eggs
72# ----
73# Add an indented line to the eggs section for any Python
74# eggs or packages you wish to include.
75#
76eggs =
77    Plone
78    Pillow
79    lxml
80    il.spdo
81#z3c.formdemo
82#plone.formwidget.autocomplete
83#IPython == 0.10
84
85# Optional Functionality
86# ----------------------
87# Uncomment the indented lines to include these add-on products.
88# Documentation on all of them, along with many more products,
89# is available at
90# http://plone.org/products/
91#
92# Example products:
93# * LinguaPlone provides tools for building multi-lingual sites
94# * PloneFormGen provides through-the-web form building
95#
96#    Products.LinguaPlone==4.0.1
97#    Products.PloneFormGen==1.6.0
98#
99# Note that versions may be specified here or in the [versions]
100# section below. You should always specify versions that you know
101# are compatible with the Plone release and at an acceptable
102# development level.
103#
104# Commonly used development tools:
105# Several excellent development tools are included in the develop.cfg
106# buildout extension. Read it to learn how to activate these tools.
107
108   
109############################################
110# ZCML Slugs
111# ----------
112# Some eggs need ZCML slugs to tell Zope to
113# use them. This is increasingly rare.
114zcml =
115#    plone.reload
116
117   
118############################################
119# Development Eggs
120# ----------------
121# You can use paster to create "development eggs" to
122# develop new products/themes. Put these in the src/
123# directory.
124# You will also need to add the egg names in the
125# eggs section above, and may also need to add them
126# to the zcml section.
127#
128# Provide the *paths* to the eggs you are developing here:
129develop =
130     src/il.spdo
131#    src/my.package
132
133
134############################################
135# Debug Mode
136# ----------
137# Change debug-mode to "on" to run in development mode.
138# This will dramatically slow Plone.
139#
140debug-mode = off
141# Add-on developers should turn deprecation warnings on
142deprecation-warnings = off
143# change verbose-security to "on" for useful security errors while developing
144verbose-security = off
145
146
147############################################
148# Backup Directory
149# ----------------
150# Sets the target directory for the bin/backup and bin/snapshotbackup
151# commands. Default is inside this project's var directory, but ideally
152# this should be on a separate volume or backup server.
153#
154backups-dir=${buildout:directory}/var
155
156
157############################################
158# Initial User
159# ------------
160# This is the user id and password that will be used to create the initial
161# user id that will allow you to log in and create a Plone site. This only
162# sets the initial password; it will not allow you to change an already
163# existing password. If you change the admin password via the web interface,
164# the one below will no longer be valid.
165# If you find yourself locked out of your Zope/Python installation, you may
166# add an emergency user via "bin/plonectl adduser".
167user=admin:OFGfizjN
168
169
170############################################
171# Parts Specification
172#--------------------
173# Specifies the components that should be included in the buildout.
174# All the basics are in the base.cfg extension; you may add your
175# own if you need them at the end of this file.
176parts =
177    instance
178    zopepy
179    zopeskel
180    unifiedinstaller
181    repozo
182    backup
183    chown
184
185
186############################################
187# Versions Specification
188# ----------------------
189# Version information supplied here will "pin" Python packages to a particular
190# version number, even when you use the "newest" flag running buildout.
191# Specifying versions for all packages is a good idea and can prevent
192# accidental changes when you add new packages to your buildout.
193# Note that versions specified here will override those specified earlier
194# in the configuration, including those from the Plone and Zope version
195# config files.
196#
197[versions]
198lxml = 2.3
199Cheetah = 2.2.1
200Pillow = 1.7.2
201Products.DocFinderTab = 1.0.4
202ZopeSkel = 2.19
203collective.recipe.backup = 1.7
204collective.recipe.omelette = 0.10
205plone.recipe.command = 1.1
206plone.recipe.osxcontroller = 0.4
207plone.recipe.unifiedinstaller = 4.1
Note: Veja TracBrowser para ajuda no uso do navegador do trac.
 

The contents and data of this website are published under license:
Creative Commons 4.0 Brasil - Atribuir Fonte - Compartilhar Igual.