-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathnanoc.yaml
140 lines (119 loc) · 5.54 KB
/
nanoc.yaml
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
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
# The syntax to use for patterns in the Rules file. Can be either `"glob"`
# (default) or `"legacy"`. The former will enable glob patterns, which behave
# like Ruby’s File.fnmatch. The latter will enable Nanoc 3.x-style patterns.
string_pattern_type: glob
# A list of file extensions that Nanoc will consider to be textual rather than
# binary. If an item with an extension not in this list is found, the file
# will be considered as binary.
text_extensions: [ 'adoc', 'asciidoc', 'atom', 'coffee', 'css', 'erb', 'haml', 'handlebars', 'hb', 'htm', 'html', 'js', 'less', 'markdown', 'md', 'ms', 'mustache', 'php', 'rb', 'rdoc', 'sass', 'scss', 'slim', 'txt', 'xhtml', 'xml' ]
# The path to the directory where all generated files will be written to. This
# can be an absolute path starting with a slash, but it can also be path
# relative to the site directory.
output_dir: output/prod
# A list of index filenames, i.e. names of files that will be served by a web
# server when a directory is requested. Usually, index files are named
# “index.html”, but depending on the web server, this may be something else,
# such as “default.htm”. This list is used by Nanoc to generate pretty URLs.
index_filenames: [ 'index.html' ]
# Whether or not to generate a diff of the compiled content when compiling a
# site. The diff will contain the differences between the compiled content
# before and after the last site compilation.
enable_output_diff: true
prune:
# Whether to automatically remove files not managed by Nanoc from the output
# directory.
auto_prune: true
# Which files and directories you want to exclude from pruning. If you version
# your output directory, you should probably exclude VCS directories such as
# .git, .svn etc.
exclude: [ '.git', '.hg', '.svn', 'CVS' ]
# The data sources where Nanoc loads its data from. This is an array of
# hashes; each array element represents a single data source. By default,
# there is only a single data source that reads data from the “content/” and
# “layout/” directories in the site directory.
data_sources:
-
# The type is the identifier of the data source.
type: filesystem
# The path where items should be mounted (comparable to mount points in
# Unix-like systems). This is “/” by default, meaning that items will have
# “/” prefixed to their identifiers. If the items root were “/en/”
# instead, an item at content/about.html would have an identifier of
# “/en/about/” instead of just “/about/”.
items_root: /
# The path where layouts should be mounted. The layouts root behaves the
# same as the items root, but applies to layouts rather than items.
layouts_root: /
# The encoding to use for input files. If your input files are not in
# UTF-8 (which they should be!), change this.
encoding: utf-8
# The kind of identifier to use for items and layouts. The default is
# “full”, meaning that identifiers include file extensions. This can also
# be “legacy”, primarily used by older Nanoc sites.
identifier_type: full
# Configuration for the “check” command, which run unit tests on the site.
checks:
# Configuration for the “internal_links” checker, which checks whether all
# internal links are valid.
internal_links:
# A list of patterns, specified as regular expressions, to exclude from the check.
# If an internal link matches this pattern, the validity check will be skipped.
# E.g.:
# exclude: ['^/server_status']
exclude: []
# Configuration for the “external_links” checker, which checks whether all
# external links are valid.
external_links:
# A list of patterns, specified as regular expressions, to exclude from the check.
# If an external link matches this pattern, the validity check will be skipped.
# E.g.:
# exclude: ['^http://example.com$']
exclude: []
# A list of file patterns, specified as regular expressions, to exclude from the check.
# If a file matches this pattern, the links from this file will not be checked.
# E.g.:
# exclude_files: ['blog/page']
exclude_files: []
# see https://nanoc.ws/doc/deploying/
deploy:
default:
# To use rsync as the deployment method, set kind to rsync in the
# deployment configuration, and set dst to the destination, in the
# format used by rsync.
kind: rsync
dst: "[email protected]:~/nanoc"
# Nanoc will, by default, only update files that have changed, and not
# remove any files from the remote destination. If you want to let
# nanoc deploy remove any files on the destination that are not part of
# the Nanoc site, you can modify the options used for rsync to include
# --delete-after, like this:
options: [ '-aP', '--delete-after' ]
# our stuff.
base_url: https://kaworu.ch
title: There is no spoon.
subtitle: ENOSPOON
description: kAworu's slice of web.
# author
author_name: kAworu
author_uri: /about
# You can customize the format as described at
# http://www.ruby-doc.org/core-1.9.2/Time.html#method-i-strftime
date_format: "%a %e %b %Y, %l:%M %p"
# Posts per page on the blog index
paginate: 6
# "Continue reading" link text at the bottom of excerpted articles
excerpt_link: "Read on →"
excerpt_separator: "<!-- more -->"
# search
simple_search: https://duckduckgo.com
# GitHub
github_user: kAworu
# Twitter
twitter_account: enospoon
# RSS
subscribe_rss: true
# see https://nanoc.ws/doc/sites/#environments
environments:
dev:
base_url: https://next.kaworu.ch
output_dir: output/dev