|
| 1 | +# A list of file extensions that nanoc will consider to be textual rather than |
| 2 | +# binary. If an item with an extension not in this list is found, the file |
| 3 | +# will be considered as binary. |
| 4 | +text_extensions: [ 'coffee', 'css', 'erb', 'haml', 'handlebars', 'hb', 'htm', 'html', 'js', 'less', 'markdown', 'md', 'ms', 'mustache', 'php', 'rb', 'sass', 'scss', 'txt', 'xhtml', 'xml' ] |
| 5 | + |
| 6 | +# The path to the directory where all generated files will be written to. This |
| 7 | +# can be an absolute path starting with a slash, but it can also be path |
| 8 | +# relative to the site directory. |
| 9 | +output_dir: output |
| 10 | + |
| 11 | +# A list of index filenames, i.e. names of files that will be served by a web |
| 12 | +# server when a directory is requested. Usually, index files are named |
| 13 | +# “index.html”, but depending on the web server, this may be something else, |
| 14 | +# such as “default.htm”. This list is used by nanoc to generate pretty URLs. |
| 15 | +index_filenames: [ 'index.html' ] |
| 16 | + |
| 17 | +# Whether or not to generate a diff of the compiled content when compiling a |
| 18 | +# site. The diff will contain the differences between the compiled content |
| 19 | +# before and after the last site compilation. |
| 20 | +enable_output_diff: false |
| 21 | + |
| 22 | +prune: |
| 23 | + # Whether to automatically remove files not managed by nanoc from the output |
| 24 | + # directory. For safety reasons, this is turned off by default. |
| 25 | + auto_prune: false |
| 26 | + |
| 27 | + # Which files and directories you want to exclude from pruning. If you version |
| 28 | + # your output directory, you should probably exclude VCS directories such as |
| 29 | + # .git, .svn etc. |
| 30 | + exclude: [ '.git', '.hg', '.svn', 'CVS' ] |
| 31 | + |
| 32 | +# The data sources where nanoc loads its data from. This is an array of |
| 33 | +# hashes; each array element represents a single data source. By default, |
| 34 | +# there is only a single data source that reads data from the “content/” and |
| 35 | +# “layout/” directories in the site directory. |
| 36 | +data_sources: |
| 37 | + - |
| 38 | + # The type is the identifier of the data source. By default, this will be |
| 39 | + # `filesystem_unified`. |
| 40 | + type: filesystem_unified |
| 41 | + |
| 42 | + # The path where items should be mounted (comparable to mount points in |
| 43 | + # Unix-like systems). This is “/” by default, meaning that items will have |
| 44 | + # “/” prefixed to their identifiers. If the items root were “/en/” |
| 45 | + # instead, an item at content/about.html would have an identifier of |
| 46 | + # “/en/about/” instead of just “/about/”. |
| 47 | + items_root: / |
| 48 | + |
| 49 | + # The path where layouts should be mounted. The layouts root behaves the |
| 50 | + # same as the items root, but applies to layouts rather than items. |
| 51 | + layouts_root: / |
| 52 | + |
| 53 | + # Whether to allow periods in identifiers. When turned off, everything |
| 54 | + # past the first period is considered to be the extension, and when |
| 55 | + # turned on, only the characters past the last period are considered to |
| 56 | + # be the extension. For example, a file named “content/about.html.erb” |
| 57 | + # will have the identifier “/about/” when turned off, but when turned on |
| 58 | + # it will become “/about.html/” instead. |
| 59 | + allow_periods_in_identifiers: false |
| 60 | + |
| 61 | + - |
| 62 | + type: static |
| 63 | + items_root: /static |
| 64 | + |
| 65 | +# Configuration for the “watch” command, which watches a site for changes and |
| 66 | +# recompiles if necessary. |
| 67 | +watcher: |
| 68 | + # A list of directories to watch for changes. When editing this, make sure |
| 69 | + # that the “output/” and “tmp/” directories are _not_ included in this list, |
| 70 | + # because recompiling the site will cause these directories to change, which |
| 71 | + # will cause the site to be recompiled, which will cause these directories |
| 72 | + # to change, which will cause the site to be recompiled again, and so on. |
| 73 | + dirs_to_watch: [ 'content', 'layouts', 'lib' ] |
| 74 | + |
| 75 | + # A list of single files to watch for changes. As mentioned above, don’t put |
| 76 | + # any files from the “output/” or “tmp/” directories in here. |
| 77 | + files_to_watch: [ 'config.yaml', 'Rules' ] |
| 78 | + |
| 79 | + # When to send notifications (using Growl or notify-send). |
| 80 | + notify_on_compilation_success: true |
| 81 | + notify_on_compilation_failure: true |
0 commit comments