· 10 years ago · Apr 18, 2016, 01:48 PM
1# Database setup. The driver can be either 'sqlite', 'mysql' or 'postgres'.
2#
3# For SQLite, only the databasename is required. However, MySQL and PostgreSQL
4# also require 'username', 'password', and optionally 'host' ( and 'port' ) if the database
5# server is not on the same host as the web server.
6#
7# If you're trying out Bolt, just keep it set to SQLite for now.
8database:
9 driver: sqlite
10 databasename: bolt
11
12# The name of the website
13sitename: json's little secret
14payoff: The amazing payoff goes here
15
16# The theme to use. Be sure to copy the {theme_path}/base-2014 folder, and
17# change the name here accordingly.
18#
19# Don't edit the templates in theme/base-2014, because they _will_ get updated
20# in next releases
21theme: xd2016
22
23# The locale that'll be used by the application. If no locale is set the
24# fallback locale is 'en_GB'. For available options, see:
25# http://docs.bolt.cm/locales
26#
27# In some cases it may be needed to specify (non-standard) variations of the
28# locale to get everything to work as desired.
29#
30# This can be done as [nl_NL, Dutch_Netherlands] when specifying multiple
31# locales, ensure the first is a standard locale.
32locale: nl_NL
33locales:
34 nl_NL:
35 label: NL
36 slug: nl
37 en_GB:
38 label: EN
39 slug: en
40 fr_FR:
41 label: FR
42 slug: fr
43
44#timezone: UTC
45
46# Set maintenance mode on or off.
47#
48# While in maintenance mode, only users of level editor or higher can access the
49# site.
50#
51# All other visitors are presented with a notice that the site is currently
52# offline.
53#
54# The default template file can be found in /app/theme_defaults/ and overridden
55# with this option using your own theme.
56#
57# Note: If you've changed the filename, and your changes do not show up on the
58# website, be sure to check for a config.ymlfile in your theme's folder.
59# If a template is set there, it will override the setting here.
60maintenance_mode: false
61maintenance_template: maintenance_default.twig
62
63# The hour of the day for the internal cron task scheduler to run daily, weekly,
64# monthly and yearly jobs.
65#
66# Default: 3 (3 am)
67cron_hour: 3
68
69# If your site is reachable under different urls (say, both blog.example.org/
70# as well as example.org/), it's a good idea to set one of these as the
71# canonical, so it's clear which is the primary address of the site.
72#
73# If you include `https://`, it will be included in the canonical urls.
74#canonical: example.org
75
76# Bolt can insert a <link rel="shortcut icon"> for all pages on the site.
77
78# Note: The location given is relative to the currently selected theme. If
79# you want to set the icon yourself, just don't enable the following line.
80#favicon: images/favicon-bolt.ico
81
82# The default content to use for the homepage, and the template to render it
83# with.
84#
85# Note: If you've changed the filename, and your changes do not show up on
86# the website, be sure to check for a config.yml file in your theme's
87# folder. If a template is set there, it will override the setting here.
88homepage: page/1
89homepage_template: index.twig
90
91# The default content for the 404 page. Uses the 'record_template' template by
92# default.
93#
94# Make sure this is set to an existing record, otherwise visitors will get an
95# error-page when the request a non-existing page.
96#
97# Note 1: The record specified in this parameter must be set to 'published'
98# Note 2: If you are logged on, and debug is set to 'true', you will NOT see the
99# 404 page!
100# Note 3: This may also point to a template without a record, eg error404.twig
101notfound: page/not-found
102
103# The default template and amount of records to use for listing-pages on the
104# site.
105#
106# Can be overridden for each contenttype and for each record, if it has a
107# 'templateselect' field.
108#
109# Note: If you've changed the filename, and your changes do not show up on the
110# website, be sure to check for a config.yml file in your theme's folder.
111# If a template is set there, it will override the setting here.
112record_template: record.twig
113
114# The default template and amount of records to use for listing-pages on the
115# site.
116#
117# Can be overridden for each contenttype.
118#
119# Note 1: Sorting on TAXONOMY-pages will give unexpected results, if it has a
120# pager.
121# If you need sorting on those, make sure you display all the records on one
122# page.
123#
124# Note 2: If you've changed the filename, and your changes do not show up on the
125# website, be sure to check for a config.yml file in your theme's
126# folder. If a template is set there, it will override the setting here.
127listing_template: listing.twig
128listing_records: 6
129listing_sort: datepublish DESC
130
131# Because of limitations on how the underlying database queries work, there are
132# only two options for sorting on taxonomies. 'ASC' for roughly "oldest first"
133# and 'DESC' for roughly 'newest first'.
134taxonomy_sort: DESC
135
136# Template for showing the search results. If not defined, uses the settings for
137# listing_template and listing_records.
138#
139# Note: If you've changed the filename, and your changes do not show up on the
140# website, be sure to check for a config.yml file in your theme's folder.
141# If a template is set there, it will override the setting here.
142search_results_template: listing.twig
143search_results_records: 10
144
145# Add jQuery to the rendered HTML, whether or not it's added by an extension.
146add_jquery: false
147
148# The default amount of records to show on overview pages. Can be overridden
149# for each contenttype.
150recordsperpage: 10
151
152# Settings for caching in parts of Bolt.
153# - config: Caches the parsed .yml files from /app/config. It's updated
154# immediately when one of the files changes on disk. There
155# should be no good reason to turn this off.
156# - templates: Caches rendered templates.
157# - request: Caches entire rendered pages like '/page/about', but only on
158# GET requests.
159# - duration: The duration (in minutes) for the 'templates' and 'request'
160# options. default is 10 minutes. Note that the duration is set
161# on storing the cache. By lowering this value you will not
162# invalidate currently cached items.
163# - authenticated: Cache 'templates' and 'request' for logged-on users. In most
164# cases you should *NOT* enable this, because it will cause
165# side-effects if the website shows different content to
166# authenticated users.
167caching:
168 config: true
169 templates: true
170 request: false
171 duration: 10
172 authenticated: false
173
174# Set 'enabled' to 'true' to log all content changes in the database.
175#
176# Unless you need to rigorously monitor every change to your site's content, it
177# is recommended to keep this disabled.
178changelog:
179 enabled: false
180
181# Default settings for thumbnails.
182#
183# Quality should be between 0 (horrible, small file) and 100 (best, huge file).
184#
185# cropping: One of either crop, fit, borders, resize.
186# default_thumbnail: The default size of images, when using
187# {{ record.image|thumbnail() }}
188# default_image: The default size of images, when using
189# {{ record.image|image() }}
190# allow_upscale: Determines whether small images will be enlarged to fit
191# the requested dimensions.
192# browser_cache_time: Sets the amount of seconds that the browser will cache
193# images for. Set it to activate browser caching.
194#
195# Note: If you change these values, you might need to clear the cache before
196# they show up.
197thumbnails:
198 default_thumbnail: [ 160, 120 ]
199 default_image: [ 1000, 750 ]
200 quality: 80
201 cropping: crop
202 notfound_image: view/img/default_notfound.png
203 error_image: view/img/default_error.png
204 save_files: false
205 allow_upscale: false
206 exif_orientation: true
207# browser_cache_time: 2592000
208
209# Define the HTML tags and attributes that are allowed in 'cleaned' HTML. This
210# is used for sanitizing HTML, to make sure there are no undesirable elements
211# left in the content that is shown to users. For example, tags like `<script>`
212# or `onclick`-attributes.
213htmlcleaner:
214 allowed_tags: [ div, p, br, hr, s, u, strong, em, i, b, li, ul, ol, blockquote, pre, code, tt, h1, h2, h3, h4, h5, h6, dd, dl, dh, table, tbody, thead, tfoot, th, td, tr, a, img ]
215 allowed_attributes: [ id, class, style, name, value, href, src ]
216
217# Uploaded file handling
218#
219# You can change the pattern match and replacement on uploaded files and if the
220# resulting filename should be transformed to lower case.
221# upload:
222# pattern: '[^A-Za-z0-9\.]+'
223# replacement: '-'
224# lowercase: true
225
226# File types that are acceptable for upload in either 'file' fields or through
227# the 'files' screen.
228
229# The following is the default list of file-types that can be uploaded through
230# the 'files' screen.
231accept_file_types: [ twig, html, js, css, scss, gif, jpg, jpeg, png, ico, zip, tgz, txt, md, doc, docx, pdf, epub, xls, xlsx, ppt, pptx, mp3, ogg, wav, m4a, mp4, m4v, ogv, wmv, avi, webm, svg]
232
233# Alternatively, if you wish to limit these, uncomment the following list
234# instead. It includes file types that are harder to exploit.
235# accept_file_types: [ gif, jpg, jpeg, png, txt, md, pdf, epub, mp3, svg ]
236
237# If you want to 'brand' the Bolt backend for a client, you can change some key
238# variables here, that determine the name of the backend, and adds a primary
239# support/contact link to the footer.
240#
241# Additionally you can change the mount
242# point for the backend, either for convenience or to obscure it from prying
243# eyes.
244#
245# The Bolt backend is accessible as /bolt/ by default, if you change it here,
246# it will only be accessible through the value set in 'path'.
247#
248# Keep the path simple: lowercase only, no extra slashes or other special
249# characters.
250# branding:
251# name: SuperCMS
252# path: /admin
253# provided_by: [ supercool@example.org, "Supercool Webdesign Co." ]
254
255# Show the 'debug' nut in the lower right corner for logged-in user. By default,
256# the debugbar is only shown to logged-in users. Use the 'debug_show_loggedoff'
257# option to show it to all users. You probably do not want to use this in a
258# production environment.
259debug: true
260developer_notices: false
261debug_show_loggedoff: false
262debug_permission_audit_mode: false
263debug_error_level: 6135 # equivalent to E_ALL &~ E_NOTICE &~ E_DEPRECATED &~ E_USER_DEPRECATED
264# debug_error_level: 30719 # equivalent to E_ALL
265debug_enable_whoops: true # change this to false to use PHP's built-in error handling instead of Whoops
266
267# System debug logging
268# This will enable intensive logging of Silex functions and will be very hard on
269# performance and log file size. The log file will be created in your cache
270# directory.
271#
272# Enable this for short time periods only when diagnosing system issues.
273# The level can be either: DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY
274debuglog:
275 enabled: false
276 filename: bolt-debug.log
277 level: DEBUG
278
279# Use strict variables. This will make Bolt complain if you use {{ foo }},
280# when foo doesn't exist.
281strict_variables: false
282
283# There are several options for giving editors more options to insert images,
284# video, etc in the WYSIWYG areas. But, as you give them more options, that
285# means they also have more ways of breaking the preciously designed layout.
286#
287# By default the most 'dangerous' options are set to 'false'. If you choose to
288# enable them for your editors, please instruct them thoroughly on their
289# responsibility not to break the layout.
290wysiwyg:
291 images: false # Allow users to insert images in the content.
292 anchor: false # Adds a button to create internal anchors to link to.
293 tables: false # Adds a button to insert and modify tables in the content.
294 fontcolor: false # Allow users to mess around with font coloring.
295 align: false # Adds buttons for 'align left', 'align right', etc.
296 subsuper: false # Adds buttons for subscript and superscript, using `<sub>` and `<sup>`.
297 embed: false # Allows the user to insert embedded video's from Youtube, Vimeo, etc.
298 underline: false # Adds a button to underline text, using the `<u>`-tag.
299 ruler: false # Adds a button to add a horizontal ruler, using the `<hr>`-tag.
300 strike: false # Adds a button to add stikethrough, using the `<s>`-tag.
301 blockquote: false # Allows the user to insert blockquotes using the `<blockquote>`-tag.
302 codesnippet: false # Allows the user to insert code snippets using `<pre><code>`-tags.
303 specialchar: false # Adds a button to insert special chars like '€' or '™'.
304 ck:
305 allowedContent: true # If set to 'true', any elements and attributes are allowed in Wysiwg Elements
306 autoParagraph: true # If set to 'true', any pasted content is wrapped in `<p>`-tags for multiple line-breaks
307 disableNativeSpellChecker: true # If set to 'true' it will stop browsers from underlining spelling mistakes
308 allowNbsp: false # If set to 'false', the editor will strip out ` ` characters. If set to 'true', it will allow them. ¯\_(ツ)_/¯
309 # viewSourceRoles: [ 'admin', 'developer' ] # The roles which are allowed to use the [Source]-button.
310
311# Global option to enable/disable the live editor
312liveeditor: true
313
314# Use the 'mailoptions' setting to configure how Bolt sends email: using 'smtp'
315# or PHP's built-in `mail()`-function.
316
317# Note that the latter might _seem_ easier, but it's been disabled by a lot of
318# webhosts, in order to prevent spam from wrongly configured scripts. If you use
319# it, your mail might disappear into a black hole, without producing any errors.
320# Generally speaking, using 'smtp' is the better option, so use that if possible.
321#
322# Protip: If your webhost does not support SMTP, sign up for a (free) Mandrill
323# account at https://mandrill.com/ for sending emails reliably.
324
325mailoptions:
326 transport: smtp
327 spool: true
328 host: smtp.iaf.nl
329 username:
330 password:
331 port: 25
332 encryption: null
333 auth_mode: null
334 senderMail: null
335 senderName: null
336
337mailoptions:
338 transport: mail
339 spool: false
340
341# Bolt allows some modifications to how 'strict' login sessions are. For every
342# option that is set to true, it becomes harder for a bad-willing person to
343# spoof your login session. However, it also requires you to re-authenticate
344# more often if you change location(ip-address) or your browser has frequent
345# upgrades. Only change these if you know what you're doing, and you're having
346# issues with the default settings.
347#
348# Note: If you change any of these, all current users will automatically be
349# logged off.
350cookies_use_remoteaddr: true
351cookies_use_browseragent: false
352cookies_use_httphost: true
353
354# The length of time a user stays 'logged in'. Change to 0 to end the session
355# when the browser is closed.
356#
357# The default is 1209600 (two weeks, in seconds).
358cookies_lifetime: 1209600
359
360# Set the session cookie to a specific domain. Leave blank, unless you know what
361# you're doing.
362#
363# When set incorrectly, you might not be able to log on at all.
364#
365# If you'd like it to be valid for all subdomains of 'www.example.org', set this
366# to '.example.org'.
367cookies_domain:
368
369# If your system is using a custom session configuration (such as a Redis
370# handler from a PHP extension) then we need to disable our session storage
371# handler. In that case, set this setting to false.
372# See: http://silex.sensiolabs.org/doc/providers/session.html#custom-session-configurations
373#
374# Do not change this, unless you know what you're doing!
375session_use_storage_handler: true
376
377# The hash_strength determines the amount of iterations for encrypting
378# passwords.
379#
380# A higher number means a harder to decrypt password, but takes longer to
381# compute. '8' is the minimum, '10' is the default, '12' is better.
382hash_strength: 10
383
384# Bolt sets the `X-Frame-Options` and `Frame-Options` to `SAMEORIGIN` by
385# default, to prevent.
386#
387# Setting this to 'false', will prevent the setting of these headers.
388# headers:
389# x_frame_options: true
390
391# Bolt uses extensions.bolt.cm to fetch it's extensions by default. You can
392# change that URL here.
393#
394# Do not change this, unless you know what you're doing, and understand the
395# associated risks. If you use 'http://extensions.bolt.cm', Bolt will not use
396# SSL, increasing the risk for a MITM attacks.
397#
398# For the stability option, you can choose either 'dev' or 'stable'. Setting
399# this to 'dev' will allow you to install dev-master versions of extensions.
400extensions:
401 site: 'https://extensions.bolt.cm/'
402 stability: stable
403 enabled: true
404
405# Enforcing the use of SSL. If set, all but the front-end pages will enforce an
406# SSL connection (and redirect to HTTPS if you attempt to visit the backend over
407# plain HTTP).
408# enforce_ssl: true
409
410# If configured, Bolt will trust X-Forwarded-XXX headers from the listed IP
411# addresses and ranges when determining whether the current request is
412# 'secure'.
413#
414# This is required to correctly determine the current hostname and protocol
415# (HTTP vs. HTTPS) when running behind some proxy, e.g. a load balancer, cache,
416# or SSL proxy.
417#
418# List the IP addresses or subnets that you know are such proxies.
419#
420# Note: Allowing hosts here that may not be trusted proxies is a security risk.
421# If you do not understand what this does, it is probably best to not
422# touch it.
423# trustProxies:
424# - 127.0.0.1
425# - 10.0.0.0/8
426
427# Theme file path where themes are. They are under /theme in project's root
428# folder by default but can be relocated. This case you should define theme_path
429# accordingly.
430#
431# Make sure the path exists, and be aware that you'll get a new 'theme' folder on any
432# subsequent Bolt update. Changing this setting is not advised.
433# theme_path: theme
434
435# If you want Bolt installation get news through a proxy
436# httpProxy:
437# host: my.proxy.server
438# user: usr
439# password: pwd
440
441
442# Options for when you're working with Grunt.
443# grunt:
444# livereload: false
445# livereloadport: 35729
446
447# Options for backend user interface
448# backend:
449# news:
450# disable: true # Disable news panel. Defaults to false. "Alerts" will still be shown.
451# stack:
452# disable: true # Disable stack usage. Defaults to false.