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