-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathpref.yml
76 lines (70 loc) · 3.47 KB
/
pref.yml
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
backend:
backend_dir: backend
synced_dirs:
# Relative paths to destination directories for code developed in Fepper.
# - First, plug a backend into Fepper. Put the actual codebase or even just
# a symbolic link to the codebase into the /backend directory.
# - Then, enter the paths relative to the /backend directory as destinations
# for frontend code to be synced by Fepper.
# - It is recommended to contain the backend codebase within a docroot
# directory just below the /backend directory. This is so Fepper can serve
# static files from the backend as per the webserved_dirs settings.
# - Do not include "backend" or a leading or trailing slash in the directory
# settings.
# - Do include a leading dot in the templates_ext setting.
# - Note that JavaScripts will only be synced if they are at least one
# directory below source/_scripts. In other words, place JavaScripts you
# wish to ignore directly in source/_scripts and no deeper.
# - Use the fp syncback task to perform the sync.
#
# - Examples:
#assets_dir: docroot/themes/theme/assets
#scripts_dir: docroot/themes/theme/scripts
#styles_dir: docroot/themes/theme/styles
#templates_dir: docroot/themes/theme/templates
#templates_ext: .tpl.php
assets_dir:
scripts_dir:
styles_dir:
templates_dir:
templates_ext:
webserved_dirs:
# Relative paths to the backend directories that will be served by Fepper's
# webserver.
# - These directories will just be served; no syncing will occur with them
# unless they are also listed in synced_dirs. The files in webserved_dirs
# can be browsed (or included) without having to copy them over into the
# Fepper frontend.
# - Be sure a backend is plugged into Fepper.
# - Create a list of relative paths which are to be served. Each path must
# contain the document root and the path from the document root to the
# target directory.
# - Do not include "backend" or a leading or trailing slash.
# - To include the directories' files in your code (or to view them in a
# - browser), enter the path without the document root. For example, if the
# setting is docroot/css, enter /css without docroot.
# - Do not use names that will collide with what's in the frontend, i.e.
# docroot/_assets, docroot/_scripts, etc.
# - DO NOT INCLUDE DIRECTORIES WITH SOURCE CODE! GITHUB PAGES AND MANY OTHER
# PUBLIC HOSTS DO NOT PREPROCESS PHP AND OTHER PROGRAMMING LANGUAGES, SO
# ANY PUBLISHED SOURCE CODE WILL BE RENDERED AS PLAIN TEXT! THIS WILL MAKE
# PUBLIC ANY SENSITIVE INFORMATION CONTAINED WITHIN THE SOURCE CODE!
#
# - Examples:
#- docroot/css
#- docroot/img
#- docroot/js
templater:
# By default, the Templater will not retain untranslated Feplet tags when
# translating to the backend's template language. However, if the backend's
# template language happens to be Feplet or Mustache, set this value to true.
retain_mustache: false
# The instance_file declares the class which defines the Fepper instance for
# this project. If you wish to customize a subclass that inherits from the
# default class, put the path to that file here. Make sure the path is relative
# to this directory (the current working directory). This setting is safe to
# delete. Fepper will instantiate the default class if it is missing.
instance_file: node_modules/fepper/core/fepper.js
lang: en
htmllint:
failOnError: true