The configuration file for a Nift project is stored in
Contents
Syntax
To use a command, enter
Project Configuration Files
Each Nift project has its own configuration file located at
contentDir 'content/' contentExt '.content' outputDir 'site/' outputExt '.html' scriptExt '.f' defaultTemplate 'template/page.template' backupScripts 1 lolcatDefault 0 lolcatCmd 'nift lolcat-cc -f' buildThreads -1 paginateThreads -1 incrementalMode -2022 terminal 'normal' unixTextEditor 'subl -n' winTextEditor 'notepad' rootBranch 'master' outputBranch 'master'
Global Configuration File
Each system you have Nift installed on will have its own global configuration file, you can check the location of the global configuration file when starting
defaultTemplate '/home/nick/.nift/template/global.template' backupScripts 1 lolcat 1 lolcatCmd "lolcat-cc -f" buildThreads -1 paginateThreads -1 incrementalMode -2022 terminal '*nix' unixTextEditor 'subl -nw' winTextEditor 'notepad'
Configurable
The table below contains information about what can be configured in the configuration files:
Name | Description | Valid Values | Global | Project |
---|---|---|---|---|
path to content directory | ||||
extension used for content files | ||||
path to output directory | ||||
extension used for build files | ||||
extension used for pre/post build scripts | ||||
default template file to use when tracking new pages | ||||
backup scripts before running them | ||||
whether to use lolcat for output | ||||
quoted command to use when running lolcat | ||||
max number of threads to use when building ($-x \rightarrow x*no\_cores$) | ||||
max number of threads to use with pagination ($-x \rightarrow x*no\_cores$) | ||||
choose between incremental mode using modification times or file hashes | ||||
mostly just to change output background colour for Powershell on Windows | ||||
specifies which text editor to use on *nix machines | eg. |
|||
specifies which text editor to use on Windows machines | eg. |
|||
Name | Description | Valid Values | Global | Project |