silverstripe-framework/_config/config.yml

---
Name: coreconfig
---
Upload:
  # Replace an existing file rather than renaming the new one.
  replaceFile: false
MySQLDatabase:
  # You are advised to backup your tables if changing settings on an existing database
  # `connection_charset` and `charset` should be equal, similarly so should `connection_collation` and `collation`
  connection_charset: utf8
  connection_collation: utf8_general_ci
  charset: utf8
  collation: utf8_general_ci
HTTP:
  cache_control:
    max-age: 0
    must-revalidate: "true"
    no-transform: "true"
  vary: "Cookie, X-Forwarded-Protocol, User-Agent, Accept"
NEW Upload->replaceFile setting 2013-02-05 19:10:15 +01:00			`---`
			`Name: coreconfig`
			`---`
			`Upload:`
			`# Replace an existing file rather than renaming the new one.`
API Marked statics private, use Config API instead (#8317) See "Static configuration properties are now immutable, you must use Config API." in the 3.1 change log for details. 2013-03-21 19:48:54 +01:00			`replaceFile: false`
			`MySQLDatabase:`
UPDATE: Add support for user defined charset and collation 2015-09-05 02:50:26 +02:00			`# You are advised to backup your tables if changing settings on an existing database`
			# `connection_charset` and `charset` should be equal, similarly so should `connection_collation` and `collation`
API: Allow HTTP Cache Headers to be customized 2015-06-13 02:12:36 +02:00			`connection_charset: utf8`
UPDATE: Add support for user defined charset and collation 2015-09-05 02:50:26 +02:00			`connection_collation: utf8_general_ci`
			`charset: utf8`
			`collation: utf8_general_ci`
API: Allow HTTP Cache Headers to be customized 2015-06-13 02:12:36 +02:00			`HTTP:`
			`cache_control:`
			`max-age: 0`
			`must-revalidate: "true"`
NEW Use Config for determining Vary header Existing implementation hardcodes the Vary header; swap to using Config layer instead Added test for changing the variable from config 2015-12-02 00:24:17 +01:00			`no-transform: "true"`
MINORE: Remove training whitespace. The main benefit of this is so that authors who make use of .editorconfig don't end up with whitespace changes in their PRs. Spaces vs. tabs has been left alone, although that could do with a tidy-up in SS4 after the switch to PSR-1/2. The command used was this: for match in '.ss' '.css' '.scss' '.html' '.yml' '.php' '.js' '.csv' '.inc' '.php5'; do find . -path ./thirdparty -not -prune -o -path ./admin/thirdparty -not -prune -o -type f -name "$match" -exec sed -E -i '' 's/[[:space:]]+$//' {} \+ find . -path ./thirdparty -not -prune -o -path ./admin/thirdparty -not -prune -o -type f -name "$match" \| xargs perl -pi -e 's/ +$//' done 2016-01-06 00:34:58 +01:00			`vary: "Cookie, X-Forwarded-Protocol, User-Agent, Accept"`