source: publico/il.spdo/trunk/il/spdo/buildout/develop.cfg

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

Atualizado buildouts para o plone 4.1.3

File size: 4.2 KB
Linha 
1#################################################################
2#
3#    Development Configuration
4#    =========================
5#   
6#    This is a buildout configuration that sets up a development
7#    environment for Plone. It extends buildout.cfg.
8#   
9#    To use this configuration, run buildout via:
10#   
11#    bin/buildout -c develop.cfg
12#   
13#    This specifies develop.cfg as buildout's configuration file. This configuration
14#    file extends buildout.cfg, so that all the options from that file are
15#    automatically included.
16#   
17#    Included in the development configuration
18#   
19#    Common development tools:
20#   
21#     * paster and Zopeskel, an add-on skeleton construction kit.
22#     
23#     * mr.developer, a tool that automatically checks out source for
24#       add ons from a versioning system, then adds them to your
25#       development package list.
26#       
27#     * testrunner, which provides a command-line option to run
28#       test suites.
29#     
30#     * omelette, which automatically musters python package sources
31#       into parts/omelette for easy find / grep access.
32#     
33#     * DocFinderTab, which adds a "doc" tab to the ZMI to explore documentation
34#       for the current Zope object.
35#
36#     * plone.reload, which allows you to use a URL like http://localhost:8080/@@reload
37#       to reload Python and ZCML code without restarting Zope.
38#
39#     Common Customizations
40#     =====================
41#     
42#     Add packages to the sources managed by mr.developer by adding them to the
43#     [sources] section below.
44#     
45#     Add packages to the test suite by adding them to the "test-packages" option
46#     in the [buildout] section below.
47
48
49############################################
50# Sources
51# -------
52# Specify packages under development here.
53#
54# See http://pypi.python.org/pypi/mr.developer for mr.developer source specifications.
55# <name> = <kind> [key=value] <url> [path] [key=value]
56# kind = The kind of repository. Currently supported are one of svn (>= 1.5), hg, git, cvs or fs.
57#
58[sources]
59# Examples: to check out plonetheme.sunburst from Plone's svn, use:
60# plonetheme.sunburst = svn https://svn.plone.org/svn/plone/plonetheme.sunburst/trunk
61#
62# To use a python package that is being developed in your src subdirectory, use:
63# myproduct.betterplone = fs myproduct.betterplone
64plone.app.drafts = git https://github.com/plone/plone.app.drafts.git
65
66
67[buildout]
68
69############################################
70# Test Packages
71# ----------
72# Specify a list of packages that you wish to explicity include in your test suite.
73# Base eggs are automatically included
74#
75test-packages =
76#    plonetheme.sunburst
77
78
79############################################
80# Debug Mode
81# ----------
82# Most development work is done with Zope/Plone started
83# in foreground mode (bin/plonectl fg), which automatically
84# turns on debug mode and causes Zope/Plone to stop on
85# package loading errors.
86#
87# Note that debug mode makes Plone run *very* slowly due to
88# extra filesystem checks and granular transmission of browser resources.
89#
90# If you have a need to run in debug mode outside foreground
91# operation, turn on debug mode below.
92debug-mode = off
93#
94# If you're developing Plone add-ons, you should want to see
95# deprecation warnings that let you know if you're using outmoded
96# methods or modules.
97deprecation-warnings = on
98#
99# Turning on verbose security may help diagnose security bugs.
100# You'll also need to disable the intercepting of "unauthorized"
101# errors in the error_log via the ZMI.
102verbose-security = off
103
104
105############################################
106# Less Commonly Changed Options
107# -----------------------------
108# The remainder of the buildout mainly sets up the development
109# environment based on the settings above.
110
111# we're extending buildout.cfg
112extends =
113    buildout.cfg
114
115extensions +=
116    mr.developer
117
118eggs +=
119    plone.reload
120#    Products.PrintingMailHost
121#    Products.DocFinderTab
122#    Products.PDBDebugMode
123
124parts +=
125    test
126    omelette
127
128# mr.developer settings:
129always-checkout = force
130sources = sources
131auto-checkout = *
132
133
134[omelette]
135recipe = collective.recipe.omelette
136eggs = ${buildout:eggs}
137
138
139[test]
140recipe = zc.recipe.testrunner
141defaults = ['--auto-color', '--auto-progress']
142
143eggs =
144    ${buildout:eggs}
145    ${buildout:test-packages}
146
147
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.