bonethug 0.0.5 → 0.0.6
Sign up to get free protection for your applications and to get access to all the features.
- data/README.md +5 -3
- data/Rakefile +2 -1
- data/bin/bonethug +2 -7
- data/lib/bonethug/cli.rb +44 -0
- data/lib/bonethug/installer.rb +202 -0
- data/lib/bonethug/version.rb +1 -1
- data/lib/bonethug.rb +3 -13
- data/lib/tasks/setup.rake +1 -1
- data/skel/base/README.md +2 -2
- data/skel/base/config/{cnf.yml → example.cnf.yml} +47 -8
- data/skel/base/config/{deploy.rb → example.deploy.rb} +23 -3
- data/skel/base/lib/conf.rb +4 -4
- data/skel/base/log/.gitkeep +0 -0
- data/skel/project_types/drupal/.gitignore +10 -21
- data/skel/project_types/drupal/composer.json +2 -28
- data/skel/project_types/drupal/public/sites/default/development.settings.php +259 -0
- data/skel/project_types/drupal/public/sites/default/production.settings.php +259 -0
- data/skel/project_types/drupal/public/sites/default/settings.php +17 -0
- data/skel/project_types/drupal/public/sites/default/staging.settings.php +260 -0
- data/skel/project_types/php/composer.json +2 -28
- data/skel/project_types/silverstripe3/config/example.schedule.rb +58 -0
- data/skel/skel.yml +7 -0
- metadata +15 -8
- data/lib/bonethug/setup.rake +0 -19
- data/skel/base/composer.json +0 -31
- /data/skel/base/config/{backup.rb → example.backup.rb} +0 -0
- /data/skel/base/config/{schedule.rb → example.schedule.rb} +0 -0
@@ -0,0 +1,259 @@
|
|
1
|
+
<?php
|
2
|
+
// $Id: default.settings.php,v 1.8.2.5 2010/12/15 13:21:14 goba Exp $
|
3
|
+
|
4
|
+
/**
|
5
|
+
* @file
|
6
|
+
* Drupal site-specific configuration file.
|
7
|
+
*
|
8
|
+
* IMPORTANT NOTE:
|
9
|
+
* This file may have been set to read-only by the Drupal installation
|
10
|
+
* program. If you make changes to this file, be sure to protect it again
|
11
|
+
* after making your modifications. Failure to remove write permissions
|
12
|
+
* to this file is a security risk.
|
13
|
+
*
|
14
|
+
* The configuration file to be loaded is based upon the rules below.
|
15
|
+
*
|
16
|
+
* The configuration directory will be discovered by stripping the
|
17
|
+
* website's hostname from left to right and pathname from right to
|
18
|
+
* left. The first configuration file found will be used and any
|
19
|
+
* others will be ignored. If no other configuration file is found
|
20
|
+
* then the default configuration file at 'sites/default' will be used.
|
21
|
+
*
|
22
|
+
* For example, for a fictitious site installed at
|
23
|
+
* http://www.drupal.org/mysite/test/, the 'settings.php'
|
24
|
+
* is searched in the following directories:
|
25
|
+
*
|
26
|
+
* 1. sites/www.drupal.org.mysite.test
|
27
|
+
* 2. sites/drupal.org.mysite.test
|
28
|
+
* 3. sites/org.mysite.test
|
29
|
+
*
|
30
|
+
* 4. sites/www.drupal.org.mysite
|
31
|
+
* 5. sites/drupal.org.mysite
|
32
|
+
* 6. sites/org.mysite
|
33
|
+
*
|
34
|
+
* 7. sites/www.drupal.org
|
35
|
+
* 8. sites/drupal.org
|
36
|
+
* 9. sites/org
|
37
|
+
*
|
38
|
+
* 10. sites/default
|
39
|
+
*
|
40
|
+
* If you are installing on a non-standard port number, prefix the
|
41
|
+
* hostname with that number. For example,
|
42
|
+
* http://www.drupal.org:8080/mysite/test/ could be loaded from
|
43
|
+
* sites/8080.www.drupal.org.mysite.test/.
|
44
|
+
*/
|
45
|
+
|
46
|
+
/**
|
47
|
+
* Database settings:
|
48
|
+
*
|
49
|
+
* Note that the $db_url variable gets parsed using PHP's built-in
|
50
|
+
* URL parser (i.e. using the "parse_url()" function) so make sure
|
51
|
+
* not to confuse the parser. If your username, password
|
52
|
+
* or database name contain characters used to delineate
|
53
|
+
* $db_url parts, you can escape them via URI hex encodings:
|
54
|
+
*
|
55
|
+
* : = %3a / = %2f @ = %40
|
56
|
+
* + = %2b ( = %28 ) = %29
|
57
|
+
* ? = %3f = = %3d & = %26
|
58
|
+
*
|
59
|
+
* To specify multiple connections to be used in your site (i.e. for
|
60
|
+
* complex custom modules) you can also specify an associative array
|
61
|
+
* of $db_url variables with the 'default' element used until otherwise
|
62
|
+
* requested.
|
63
|
+
*
|
64
|
+
* You can optionally set prefixes for some or all database table names
|
65
|
+
* by using the $db_prefix setting. If a prefix is specified, the table
|
66
|
+
* name will be prepended with its value. Be sure to use valid database
|
67
|
+
* characters only, usually alphanumeric and underscore. If no prefixes
|
68
|
+
* are desired, leave it as an empty string ''.
|
69
|
+
*
|
70
|
+
* To have all database names prefixed, set $db_prefix as a string:
|
71
|
+
*
|
72
|
+
* $db_prefix = 'main_';
|
73
|
+
*
|
74
|
+
* To provide prefixes for specific tables, set $db_prefix as an array.
|
75
|
+
* The array's keys are the table names and the values are the prefixes.
|
76
|
+
* The 'default' element holds the prefix for any tables not specified
|
77
|
+
* elsewhere in the array. Example:
|
78
|
+
*
|
79
|
+
* $db_prefix = array(
|
80
|
+
* 'default' => 'main_',
|
81
|
+
* 'users' => 'shared_',
|
82
|
+
* 'sessions' => 'shared_',
|
83
|
+
* 'role' => 'shared_',
|
84
|
+
* 'authmap' => 'shared_',
|
85
|
+
* );
|
86
|
+
*
|
87
|
+
* Database URL format:
|
88
|
+
* $db_url = 'mysql://username:password@localhost/databasename';
|
89
|
+
* $db_url = 'mysqli://username:password@localhost/databasename';
|
90
|
+
* $db_url = 'pgsql://username:password@localhost/databasename';
|
91
|
+
*/
|
92
|
+
$db_url = 'mysqli://'.$db->user.':'.$db->pass.'@'.$db->host.'/'.$db->name;
|
93
|
+
$db_prefix = '';
|
94
|
+
|
95
|
+
/**
|
96
|
+
* Database default collation.
|
97
|
+
*
|
98
|
+
* All data stored in Drupal is in UTF-8. Certain databases, such as MySQL,
|
99
|
+
* support different algorithms for comparing, indexing, and sorting characters;
|
100
|
+
* a so called "collation". The default collation of a database normally works
|
101
|
+
* for many use-cases, but depending on the language(s) of the stored data, it
|
102
|
+
* may be necessary to use a different collation.
|
103
|
+
* Important:
|
104
|
+
* - Only set or change this value BEFORE installing Drupal, unless you know
|
105
|
+
* what you are doing.
|
106
|
+
* - All database tables and columns should be in the same collation. Otherwise,
|
107
|
+
* string comparisons performed for table JOINs will be significantly slower.
|
108
|
+
* - Especially when storing data in German or Russian on MySQL 5.1+, you want
|
109
|
+
* to use the 'utf8_unicode_ci' collation instead.
|
110
|
+
*
|
111
|
+
* @see http://drupal.org/node/772678
|
112
|
+
*/
|
113
|
+
# $db_collation = 'utf8_general_ci';
|
114
|
+
|
115
|
+
/**
|
116
|
+
* Access control for update.php script
|
117
|
+
*
|
118
|
+
* If you are updating your Drupal installation using the update.php script
|
119
|
+
* being not logged in as administrator, you will need to modify the access
|
120
|
+
* check statement below. Change the FALSE to a TRUE to disable the access
|
121
|
+
* check. After finishing the upgrade, be sure to open this file again
|
122
|
+
* and change the TRUE back to a FALSE!
|
123
|
+
*/
|
124
|
+
$update_free_access = FALSE;
|
125
|
+
|
126
|
+
/**
|
127
|
+
* Base URL (optional).
|
128
|
+
*
|
129
|
+
* If you are experiencing issues with different site domains,
|
130
|
+
* uncomment the Base URL statement below (remove the leading hash sign)
|
131
|
+
* and fill in the absolute URL to your Drupal installation.
|
132
|
+
*
|
133
|
+
* You might also want to force users to use a given domain.
|
134
|
+
* See the .htaccess file for more information.
|
135
|
+
*
|
136
|
+
* Examples:
|
137
|
+
* $base_url = 'http://www.example.com';
|
138
|
+
* $base_url = 'http://www.example.com:8888';
|
139
|
+
* $base_url = 'http://www.example.com/drupal';
|
140
|
+
* $base_url = 'https://www.example.com:8888/drupal';
|
141
|
+
*
|
142
|
+
* It is not allowed to have a trailing slash; Drupal will add it
|
143
|
+
* for you.
|
144
|
+
*/
|
145
|
+
# $base_url = 'http://www.example.com'; // NO trailing slash!
|
146
|
+
|
147
|
+
/**
|
148
|
+
* PHP settings:
|
149
|
+
*
|
150
|
+
* To see what PHP settings are possible, including whether they can
|
151
|
+
* be set at runtime (ie., when ini_set() occurs), read the PHP
|
152
|
+
* documentation at http://www.php.net/manual/en/ini.php#ini.list
|
153
|
+
* and take a look at the .htaccess file to see which non-runtime
|
154
|
+
* settings are used there. Settings defined here should not be
|
155
|
+
* duplicated there so as to avoid conflict issues.
|
156
|
+
*/
|
157
|
+
ini_set('arg_separator.output', '&');
|
158
|
+
ini_set('magic_quotes_runtime', 0);
|
159
|
+
ini_set('magic_quotes_sybase', 0);
|
160
|
+
ini_set('session.cache_expire', 200000);
|
161
|
+
ini_set('session.cache_limiter', 'none');
|
162
|
+
ini_set('session.cookie_lifetime', 2000000);
|
163
|
+
ini_set('session.gc_maxlifetime', 200000);
|
164
|
+
ini_set('session.save_handler', 'user');
|
165
|
+
ini_set('session.use_cookies', 1);
|
166
|
+
ini_set('session.use_only_cookies', 1);
|
167
|
+
ini_set('session.use_trans_sid', 0);
|
168
|
+
ini_set('url_rewriter.tags', '');
|
169
|
+
|
170
|
+
/**
|
171
|
+
* If you encounter a situation where users post a large amount of text, and
|
172
|
+
* the result is stripped out upon viewing but can still be edited, Drupal's
|
173
|
+
* output filter may not have sufficient memory to process it. If you
|
174
|
+
* experience this issue, you may wish to uncomment the following two lines
|
175
|
+
* and increase the limits of these variables. For more information, see
|
176
|
+
* http://php.net/manual/en/pcre.configuration.php.
|
177
|
+
*/
|
178
|
+
# ini_set('pcre.backtrack_limit', 200000);
|
179
|
+
# ini_set('pcre.recursion_limit', 200000);
|
180
|
+
|
181
|
+
/**
|
182
|
+
* Drupal automatically generates a unique session cookie name for each site
|
183
|
+
* based on on its full domain name. If you have multiple domains pointing at
|
184
|
+
* the same Drupal site, you can either redirect them all to a single domain
|
185
|
+
* (see comment in .htaccess), or uncomment the line below and specify their
|
186
|
+
* shared base domain. Doing so assures that users remain logged in as they
|
187
|
+
* cross between your various domains.
|
188
|
+
*/
|
189
|
+
# $cookie_domain = 'example.com';
|
190
|
+
|
191
|
+
/**
|
192
|
+
* Variable overrides:
|
193
|
+
*
|
194
|
+
* To override specific entries in the 'variable' table for this site,
|
195
|
+
* set them here. You usually don't need to use this feature. This is
|
196
|
+
* useful in a configuration file for a vhost or directory, rather than
|
197
|
+
* the default settings.php. Any configuration setting from the 'variable'
|
198
|
+
* table can be given a new value. Note that any values you provide in
|
199
|
+
* these variable overrides will not be modifiable from the Drupal
|
200
|
+
* administration interface.
|
201
|
+
*
|
202
|
+
* Remove the leading hash signs to enable.
|
203
|
+
*/
|
204
|
+
# $conf = array(
|
205
|
+
# 'site_name' => 'My Drupal site',
|
206
|
+
# 'theme_default' => 'minnelli',
|
207
|
+
# 'anonymous' => 'Visitor',
|
208
|
+
/**
|
209
|
+
* A custom theme can be set for the off-line page. This applies when the site
|
210
|
+
* is explicitly set to off-line mode through the administration page or when
|
211
|
+
* the database is inactive due to an error. It can be set through the
|
212
|
+
* 'maintenance_theme' key. The template file should also be copied into the
|
213
|
+
* theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
|
214
|
+
* Note: This setting does not apply to installation and update pages.
|
215
|
+
*/
|
216
|
+
# 'maintenance_theme' => 'minnelli',
|
217
|
+
/**
|
218
|
+
* reverse_proxy accepts a boolean value.
|
219
|
+
*
|
220
|
+
* Enable this setting to determine the correct IP address of the remote
|
221
|
+
* client by examining information stored in the X-Forwarded-For headers.
|
222
|
+
* X-Forwarded-For headers are a standard mechanism for identifying client
|
223
|
+
* systems connecting through a reverse proxy server, such as Squid or
|
224
|
+
* Pound. Reverse proxy servers are often used to enhance the performance
|
225
|
+
* of heavily visited sites and may also provide other site caching,
|
226
|
+
* security or encryption benefits. If this Drupal installation operates
|
227
|
+
* behind a reverse proxy, this setting should be enabled so that correct
|
228
|
+
* IP address information is captured in Drupal's session management,
|
229
|
+
* logging, statistics and access management systems; if you are unsure
|
230
|
+
* about this setting, do not have a reverse proxy, or Drupal operates in
|
231
|
+
* a shared hosting environment, this setting should be set to disabled.
|
232
|
+
*/
|
233
|
+
# 'reverse_proxy' => TRUE,
|
234
|
+
/**
|
235
|
+
* reverse_proxy accepts an array of IP addresses.
|
236
|
+
*
|
237
|
+
* Each element of this array is the IP address of any of your reverse
|
238
|
+
* proxies. Filling this array Drupal will trust the information stored
|
239
|
+
* in the X-Forwarded-For headers only if Remote IP address is one of
|
240
|
+
* these, that is the request reaches the web server from one of your
|
241
|
+
* reverse proxies. Otherwise, the client could directly connect to
|
242
|
+
* your web server spoofing the X-Forwarded-For headers.
|
243
|
+
*/
|
244
|
+
# 'reverse_proxy_addresses' => array('a.b.c.d', ...),
|
245
|
+
# );
|
246
|
+
|
247
|
+
/**
|
248
|
+
* String overrides:
|
249
|
+
*
|
250
|
+
* To override specific strings on your site with or without enabling locale
|
251
|
+
* module, add an entry to this list. This functionality allows you to change
|
252
|
+
* a small number of your site's default English language interface strings.
|
253
|
+
*
|
254
|
+
* Remove the leading hash signs to enable.
|
255
|
+
*/
|
256
|
+
# $conf['locale_custom_strings_en'] = array(
|
257
|
+
# 'forum' => 'Discussion board',
|
258
|
+
# '@count min' => '@count minutes',
|
259
|
+
# );
|
@@ -0,0 +1,259 @@
|
|
1
|
+
<?php
|
2
|
+
// $Id: default.settings.php,v 1.8.2.5 2010/12/15 13:21:14 goba Exp $
|
3
|
+
|
4
|
+
/**
|
5
|
+
* @file
|
6
|
+
* Drupal site-specific configuration file.
|
7
|
+
*
|
8
|
+
* IMPORTANT NOTE:
|
9
|
+
* This file may have been set to read-only by the Drupal installation
|
10
|
+
* program. If you make changes to this file, be sure to protect it again
|
11
|
+
* after making your modifications. Failure to remove write permissions
|
12
|
+
* to this file is a security risk.
|
13
|
+
*
|
14
|
+
* The configuration file to be loaded is based upon the rules below.
|
15
|
+
*
|
16
|
+
* The configuration directory will be discovered by stripping the
|
17
|
+
* website's hostname from left to right and pathname from right to
|
18
|
+
* left. The first configuration file found will be used and any
|
19
|
+
* others will be ignored. If no other configuration file is found
|
20
|
+
* then the default configuration file at 'sites/default' will be used.
|
21
|
+
*
|
22
|
+
* For example, for a fictitious site installed at
|
23
|
+
* http://www.drupal.org/mysite/test/, the 'settings.php'
|
24
|
+
* is searched in the following directories:
|
25
|
+
*
|
26
|
+
* 1. sites/www.drupal.org.mysite.test
|
27
|
+
* 2. sites/drupal.org.mysite.test
|
28
|
+
* 3. sites/org.mysite.test
|
29
|
+
*
|
30
|
+
* 4. sites/www.drupal.org.mysite
|
31
|
+
* 5. sites/drupal.org.mysite
|
32
|
+
* 6. sites/org.mysite
|
33
|
+
*
|
34
|
+
* 7. sites/www.drupal.org
|
35
|
+
* 8. sites/drupal.org
|
36
|
+
* 9. sites/org
|
37
|
+
*
|
38
|
+
* 10. sites/default
|
39
|
+
*
|
40
|
+
* If you are installing on a non-standard port number, prefix the
|
41
|
+
* hostname with that number. For example,
|
42
|
+
* http://www.drupal.org:8080/mysite/test/ could be loaded from
|
43
|
+
* sites/8080.www.drupal.org.mysite.test/.
|
44
|
+
*/
|
45
|
+
|
46
|
+
/**
|
47
|
+
* Database settings:
|
48
|
+
*
|
49
|
+
* Note that the $db_url variable gets parsed using PHP's built-in
|
50
|
+
* URL parser (i.e. using the "parse_url()" function) so make sure
|
51
|
+
* not to confuse the parser. If your username, password
|
52
|
+
* or database name contain characters used to delineate
|
53
|
+
* $db_url parts, you can escape them via URI hex encodings:
|
54
|
+
*
|
55
|
+
* : = %3a / = %2f @ = %40
|
56
|
+
* + = %2b ( = %28 ) = %29
|
57
|
+
* ? = %3f = = %3d & = %26
|
58
|
+
*
|
59
|
+
* To specify multiple connections to be used in your site (i.e. for
|
60
|
+
* complex custom modules) you can also specify an associative array
|
61
|
+
* of $db_url variables with the 'default' element used until otherwise
|
62
|
+
* requested.
|
63
|
+
*
|
64
|
+
* You can optionally set prefixes for some or all database table names
|
65
|
+
* by using the $db_prefix setting. If a prefix is specified, the table
|
66
|
+
* name will be prepended with its value. Be sure to use valid database
|
67
|
+
* characters only, usually alphanumeric and underscore. If no prefixes
|
68
|
+
* are desired, leave it as an empty string ''.
|
69
|
+
*
|
70
|
+
* To have all database names prefixed, set $db_prefix as a string:
|
71
|
+
*
|
72
|
+
* $db_prefix = 'main_';
|
73
|
+
*
|
74
|
+
* To provide prefixes for specific tables, set $db_prefix as an array.
|
75
|
+
* The array's keys are the table names and the values are the prefixes.
|
76
|
+
* The 'default' element holds the prefix for any tables not specified
|
77
|
+
* elsewhere in the array. Example:
|
78
|
+
*
|
79
|
+
* $db_prefix = array(
|
80
|
+
* 'default' => 'main_',
|
81
|
+
* 'users' => 'shared_',
|
82
|
+
* 'sessions' => 'shared_',
|
83
|
+
* 'role' => 'shared_',
|
84
|
+
* 'authmap' => 'shared_',
|
85
|
+
* );
|
86
|
+
*
|
87
|
+
* Database URL format:
|
88
|
+
* $db_url = 'mysql://username:password@localhost/databasename';
|
89
|
+
* $db_url = 'mysqli://username:password@localhost/databasename';
|
90
|
+
* $db_url = 'pgsql://username:password@localhost/databasename';
|
91
|
+
*/
|
92
|
+
$db_url = 'mysqli://'.$db->user.':'.$db->pass.'@'.$db->host.'/'.$db->name;
|
93
|
+
$db_prefix = '';
|
94
|
+
|
95
|
+
/**
|
96
|
+
* Database default collation.
|
97
|
+
*
|
98
|
+
* All data stored in Drupal is in UTF-8. Certain databases, such as MySQL,
|
99
|
+
* support different algorithms for comparing, indexing, and sorting characters;
|
100
|
+
* a so called "collation". The default collation of a database normally works
|
101
|
+
* for many use-cases, but depending on the language(s) of the stored data, it
|
102
|
+
* may be necessary to use a different collation.
|
103
|
+
* Important:
|
104
|
+
* - Only set or change this value BEFORE installing Drupal, unless you know
|
105
|
+
* what you are doing.
|
106
|
+
* - All database tables and columns should be in the same collation. Otherwise,
|
107
|
+
* string comparisons performed for table JOINs will be significantly slower.
|
108
|
+
* - Especially when storing data in German or Russian on MySQL 5.1+, you want
|
109
|
+
* to use the 'utf8_unicode_ci' collation instead.
|
110
|
+
*
|
111
|
+
* @see http://drupal.org/node/772678
|
112
|
+
*/
|
113
|
+
# $db_collation = 'utf8_general_ci';
|
114
|
+
|
115
|
+
/**
|
116
|
+
* Access control for update.php script
|
117
|
+
*
|
118
|
+
* If you are updating your Drupal installation using the update.php script
|
119
|
+
* being not logged in as administrator, you will need to modify the access
|
120
|
+
* check statement below. Change the FALSE to a TRUE to disable the access
|
121
|
+
* check. After finishing the upgrade, be sure to open this file again
|
122
|
+
* and change the TRUE back to a FALSE!
|
123
|
+
*/
|
124
|
+
$update_free_access = FALSE;
|
125
|
+
|
126
|
+
/**
|
127
|
+
* Base URL (optional).
|
128
|
+
*
|
129
|
+
* If you are experiencing issues with different site domains,
|
130
|
+
* uncomment the Base URL statement below (remove the leading hash sign)
|
131
|
+
* and fill in the absolute URL to your Drupal installation.
|
132
|
+
*
|
133
|
+
* You might also want to force users to use a given domain.
|
134
|
+
* See the .htaccess file for more information.
|
135
|
+
*
|
136
|
+
* Examples:
|
137
|
+
* $base_url = 'http://www.example.com';
|
138
|
+
* $base_url = 'http://www.example.com:8888';
|
139
|
+
* $base_url = 'http://www.example.com/drupal';
|
140
|
+
* $base_url = 'https://www.example.com:8888/drupal';
|
141
|
+
*
|
142
|
+
* It is not allowed to have a trailing slash; Drupal will add it
|
143
|
+
* for you.
|
144
|
+
*/
|
145
|
+
# $base_url = 'http://www.example.com'; // NO trailing slash!
|
146
|
+
|
147
|
+
/**
|
148
|
+
* PHP settings:
|
149
|
+
*
|
150
|
+
* To see what PHP settings are possible, including whether they can
|
151
|
+
* be set at runtime (ie., when ini_set() occurs), read the PHP
|
152
|
+
* documentation at http://www.php.net/manual/en/ini.php#ini.list
|
153
|
+
* and take a look at the .htaccess file to see which non-runtime
|
154
|
+
* settings are used there. Settings defined here should not be
|
155
|
+
* duplicated there so as to avoid conflict issues.
|
156
|
+
*/
|
157
|
+
ini_set('arg_separator.output', '&');
|
158
|
+
ini_set('magic_quotes_runtime', 0);
|
159
|
+
ini_set('magic_quotes_sybase', 0);
|
160
|
+
ini_set('session.cache_expire', 200000);
|
161
|
+
ini_set('session.cache_limiter', 'none');
|
162
|
+
ini_set('session.cookie_lifetime', 2000000);
|
163
|
+
ini_set('session.gc_maxlifetime', 200000);
|
164
|
+
ini_set('session.save_handler', 'user');
|
165
|
+
ini_set('session.use_cookies', 1);
|
166
|
+
ini_set('session.use_only_cookies', 1);
|
167
|
+
ini_set('session.use_trans_sid', 0);
|
168
|
+
ini_set('url_rewriter.tags', '');
|
169
|
+
|
170
|
+
/**
|
171
|
+
* If you encounter a situation where users post a large amount of text, and
|
172
|
+
* the result is stripped out upon viewing but can still be edited, Drupal's
|
173
|
+
* output filter may not have sufficient memory to process it. If you
|
174
|
+
* experience this issue, you may wish to uncomment the following two lines
|
175
|
+
* and increase the limits of these variables. For more information, see
|
176
|
+
* http://php.net/manual/en/pcre.configuration.php.
|
177
|
+
*/
|
178
|
+
# ini_set('pcre.backtrack_limit', 200000);
|
179
|
+
# ini_set('pcre.recursion_limit', 200000);
|
180
|
+
|
181
|
+
/**
|
182
|
+
* Drupal automatically generates a unique session cookie name for each site
|
183
|
+
* based on on its full domain name. If you have multiple domains pointing at
|
184
|
+
* the same Drupal site, you can either redirect them all to a single domain
|
185
|
+
* (see comment in .htaccess), or uncomment the line below and specify their
|
186
|
+
* shared base domain. Doing so assures that users remain logged in as they
|
187
|
+
* cross between your various domains.
|
188
|
+
*/
|
189
|
+
# $cookie_domain = 'example.com';
|
190
|
+
|
191
|
+
/**
|
192
|
+
* Variable overrides:
|
193
|
+
*
|
194
|
+
* To override specific entries in the 'variable' table for this site,
|
195
|
+
* set them here. You usually don't need to use this feature. This is
|
196
|
+
* useful in a configuration file for a vhost or directory, rather than
|
197
|
+
* the default settings.php. Any configuration setting from the 'variable'
|
198
|
+
* table can be given a new value. Note that any values you provide in
|
199
|
+
* these variable overrides will not be modifiable from the Drupal
|
200
|
+
* administration interface.
|
201
|
+
*
|
202
|
+
* Remove the leading hash signs to enable.
|
203
|
+
*/
|
204
|
+
# $conf = array(
|
205
|
+
# 'site_name' => 'My Drupal site',
|
206
|
+
# 'theme_default' => 'minnelli',
|
207
|
+
# 'anonymous' => 'Visitor',
|
208
|
+
/**
|
209
|
+
* A custom theme can be set for the off-line page. This applies when the site
|
210
|
+
* is explicitly set to off-line mode through the administration page or when
|
211
|
+
* the database is inactive due to an error. It can be set through the
|
212
|
+
* 'maintenance_theme' key. The template file should also be copied into the
|
213
|
+
* theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
|
214
|
+
* Note: This setting does not apply to installation and update pages.
|
215
|
+
*/
|
216
|
+
# 'maintenance_theme' => 'minnelli',
|
217
|
+
/**
|
218
|
+
* reverse_proxy accepts a boolean value.
|
219
|
+
*
|
220
|
+
* Enable this setting to determine the correct IP address of the remote
|
221
|
+
* client by examining information stored in the X-Forwarded-For headers.
|
222
|
+
* X-Forwarded-For headers are a standard mechanism for identifying client
|
223
|
+
* systems connecting through a reverse proxy server, such as Squid or
|
224
|
+
* Pound. Reverse proxy servers are often used to enhance the performance
|
225
|
+
* of heavily visited sites and may also provide other site caching,
|
226
|
+
* security or encryption benefits. If this Drupal installation operates
|
227
|
+
* behind a reverse proxy, this setting should be enabled so that correct
|
228
|
+
* IP address information is captured in Drupal's session management,
|
229
|
+
* logging, statistics and access management systems; if you are unsure
|
230
|
+
* about this setting, do not have a reverse proxy, or Drupal operates in
|
231
|
+
* a shared hosting environment, this setting should be set to disabled.
|
232
|
+
*/
|
233
|
+
# 'reverse_proxy' => TRUE,
|
234
|
+
/**
|
235
|
+
* reverse_proxy accepts an array of IP addresses.
|
236
|
+
*
|
237
|
+
* Each element of this array is the IP address of any of your reverse
|
238
|
+
* proxies. Filling this array Drupal will trust the information stored
|
239
|
+
* in the X-Forwarded-For headers only if Remote IP address is one of
|
240
|
+
* these, that is the request reaches the web server from one of your
|
241
|
+
* reverse proxies. Otherwise, the client could directly connect to
|
242
|
+
* your web server spoofing the X-Forwarded-For headers.
|
243
|
+
*/
|
244
|
+
# 'reverse_proxy_addresses' => array('a.b.c.d', ...),
|
245
|
+
# );
|
246
|
+
|
247
|
+
/**
|
248
|
+
* String overrides:
|
249
|
+
*
|
250
|
+
* To override specific strings on your site with or without enabling locale
|
251
|
+
* module, add an entry to this list. This functionality allows you to change
|
252
|
+
* a small number of your site's default English language interface strings.
|
253
|
+
*
|
254
|
+
* Remove the leading hash signs to enable.
|
255
|
+
*/
|
256
|
+
# $conf['locale_custom_strings_en'] = array(
|
257
|
+
# 'forum' => 'Discussion board',
|
258
|
+
# '@count min' => '@count minutes',
|
259
|
+
# );
|
@@ -0,0 +1,17 @@
|
|
1
|
+
<?php
|
2
|
+
|
3
|
+
// autoloader
|
4
|
+
require_once __DIR__ . '/../../../vendor/autoload.php';
|
5
|
+
|
6
|
+
// Namespace for yaml
|
7
|
+
use Symfony\Component\Yaml\Yaml;
|
8
|
+
|
9
|
+
// Transfer environmental vars to constants
|
10
|
+
if (!defined('APPLICATION_ENV')) define('APPLICATION_ENV', getenv('APPLICATION_ENV') ? getenv('APPLICATION_ENV') : "production");
|
11
|
+
|
12
|
+
// prep some data
|
13
|
+
$db_cnf = Yaml::parse(file_get_contents(__DIR__.'/../../../config/cnf.yml'));
|
14
|
+
$db = (object) $db_cnf['dbs']['default'][APPLICATION_ENV];
|
15
|
+
|
16
|
+
// what conf are we using
|
17
|
+
require APPLICATION_ENV . '.settings.php';
|