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

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

Atualizado arquivos de configuracao do buildout.

File size: 6.4 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/five.grok/1.2.0-1
50    http://good-py.appspot.com/release/plone.app.z3cform/0.5.6-1
51#    http://dist.plone.org/release/4.1-latest/versions.cfg
52
53
54############################################
55# Ports
56# -----
57# Specify the port on which your Zope installation
58# will listen:
59http-address = 8080
60
61
62# If you try to start Zope as root, it will change user id to run as
63# the effective user specified here. This user id must own the var directory
64# of your buildout.
65effective-user = plone
66
67
68############################################
69# Eggs
70# ----
71# Add an indented line to the eggs section for any Python
72# eggs or packages you wish to include.
73#
74eggs =
75    Plone
76    Pillow
77    lxml
78    il.spdo
79
80# Optional Functionality
81# ----------------------
82# Uncomment the indented lines to include these add-on products.
83# Documentation on all of them, along with many more products,
84# is available at
85# http://plone.org/products/
86#
87# Example products:
88# * LinguaPlone provides tools for building multi-lingual sites
89# * PloneFormGen provides through-the-web form building
90#
91#    Products.LinguaPlone==4.0.1
92#    Products.PloneFormGen==1.6.0
93#
94# Note that versions may be specified here or in the [versions]
95# section below. You should always specify versions that you know
96# are compatible with the Plone release and at an acceptable
97# development level.
98#
99# Commonly used development tools:
100# Several excellent development tools are included in the develop.cfg
101# buildout extension. Read it to learn how to activate these tools.
102
103   
104############################################
105# ZCML Slugs
106# ----------
107# Some eggs need ZCML slugs to tell Zope to
108# use them. This is increasingly rare.
109zcml =
110#    plone.reload
111
112   
113############################################
114# Development Eggs
115# ----------------
116# You can use paster to create "development eggs" to
117# develop new products/themes. Put these in the src/
118# directory.
119# You will also need to add the egg names in the
120# eggs section above, and may also need to add them
121# to the zcml section.
122#
123# Provide the *paths* to the eggs you are developing here:
124develop =
125     src/il.spdo
126#    src/my.package
127
128
129############################################
130# Debug Mode
131# ----------
132# Change debug-mode to "on" to run in development mode.
133# This will dramatically slow Plone.
134#
135debug-mode = off
136# Add-on developers should turn deprecation warnings on
137deprecation-warnings = off
138# change verbose-security to "on" for useful security errors while developing
139verbose-security = off
140
141
142############################################
143# Backup Directory
144# ----------------
145# Sets the target directory for the bin/backup and bin/snapshotbackup
146# commands. Default is inside this project's var directory, but ideally
147# this should be on a separate volume or backup server.
148#
149backups-dir=${buildout:directory}/var
150
151
152############################################
153# Initial User
154# ------------
155# This is the user id and password that will be used to create the initial
156# user id that will allow you to log in and create a Plone site. This only
157# sets the initial password; it will not allow you to change an already
158# existing password. If you change the admin password via the web interface,
159# the one below will no longer be valid.
160# If you find yourself locked out of your Zope/Python installation, you may
161# add an emergency user via "bin/plonectl adduser".
162user=admin:OFGfizjN
163
164
165############################################
166# Parts Specification
167#--------------------
168# Specifies the components that should be included in the buildout.
169# All the basics are in the base.cfg extension; you may add your
170# own if you need them at the end of this file.
171parts =
172    instance
173    zopepy
174    zopeskel
175    unifiedinstaller
176    repozo
177    backup
178    chown
179
180
181############################################
182# Versions Specification
183# ----------------------
184# Version information supplied here will "pin" Python packages to a particular
185# version number, even when you use the "newest" flag running buildout.
186# Specifying versions for all packages is a good idea and can prevent
187# accidental changes when you add new packages to your buildout.
188# Note that versions specified here will override those specified earlier
189# in the configuration, including those from the Plone and Zope version
190# config files.
191#
192[versions]
193lxml = 2.3
194Cheetah = 2.2.1
195Pillow = 1.7.2
196Products.DocFinderTab = 1.0.4
197ZopeSkel = 2.19
198collective.recipe.backup = 1.7
199collective.recipe.omelette = 0.10
200plone.recipe.command = 1.1
201plone.recipe.osxcontroller = 0.4
202plone.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.