-
Notifications
You must be signed in to change notification settings - Fork 0
/
buildout.cfg
137 lines (104 loc) · 2.68 KB
/
buildout.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
[buildout]
extends =
versions.cfg
recipes.cfg
deployment.cfg
update-versions-file = versions.cfg
show-picked-versions = true
parts =
directories
# Using 'true' causes issues with file templates and extra Z3C_RECIPE_FILETEMPLATE_BASE
# not being interpreted
relative-paths = false
# By default, buildout checks for
# updated eggs when the requirements
# specify no version or >=. This can
# be fairly slow if most requirements are
# unpinned. Setting newest to false
# makes this not happen. The command line
# arg -n can make it happen again
newest = false
# We manage our checkouts using mr.developer, which
# easily allows pinning versions (revision=XXX)
# and provides the 'develop' command with many
# useful actions (like 'rebuild)
# See https://pypi.python.org/pypi/mr.developer/
extensions = mr.developer
mr.developer-threads = 35
sources-dir = sources
auto-checkout = *
# always-checkout =
# This defaults to false. If it's true, then all packages specified by
# auto-checkout and currently in develop mode are updated during each
# buildout run. If set to force, then packages are updated even when
# they are dirty instead of asking interactively.
[base-sources]
[solr-sources]
[site-sources]
[extra-sources]
[forums-sources]
[webapp-sources]
[product-sources]
[metadata-sources]
[recorder-sources]
[mobileapp-sources]
[credit-sources]
[calendar-sources]
[completion-sources]
[dataserver-sources]
[publishing-sources]
[landingpage-sources]
[contentrendering-sources]
[analytics-sources]
[analytics-pandas-sources]
[learning-sources]
[spark-sources]
[tableau-sources]
[orgsync-sources]
[ou-recommendations-sources]
[campusgenius-sources]
[sources]
<= base-sources
site-sources
solr-sources
extra-sources
spark-sources
credit-sources
forums-sources
webapp-sources
tableau-sources
orgsync-sources
product-sources
recipes-sources
learning-sources
metadata-sources
recorder-sources
analytics-sources
mobileapp-sources
calendar-sources
completion-sources
dataserver-sources
publishing-sources
landingpage-sources
campusgenius-sources
contentrendering-sources
analytics-pandas-sources
ou-recommendations-sources
[deployment]
root-directory = ${buildout:directory}
[eggs]
recipe = zc.recipe.egg
eggs =
pip
interpreter = python
# Note that when scripts are installed,
# the order is not knowable. Thus it is not
# possible for one egg to reliable override
# a script from another egg, without
# explicitly listing exactly which scripts (from all
# eggs) to install. That is a large list, so
# we just need to make sure we don't have conflicts
# in names.
dependent-scripts = true
extra-paths =
${deployment:plugin-directory}