Fepper can very easily work with a CMS backend such as Drupal or WordPress, while not requiring Apache, MySQL, or PHP. Put the actual backend codebase or even just a symbolic link to the codebase into the
backend directory. Then, enter the relative paths to the appropriate backend directories in
pref.yml. (Do not include "backend" or a leading slash.) You will then be able to run
fp syncback or
fp frontend-copy to export your frontend data into your backend web application.
- Be sure that
backend.synced_dirs.styles_dirare set in
- The above values set in
pref.ymlcan be overridden on a per-file basis by similarly named YAML files with similarly named settings.
- These YAML files must match the source file's name with the exception of the extension.
- The extension must be
- The overriding property must only contain the lowest level key:value, not the entire hierarchy, e.g. only
- Asset, script, and style files prefixed by "__" will be ignored by
fp frontend-copy, as will files in the
_nosyncdirectory at the root of the source directories.