limetree.kdl
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
// This is a sample configuration file for the Limetree CMS. It is written in KDL
// (https://kdl.dev/).
//
// Nothing needs to be changed to start up the service and try it out. When deploying for real,
// you'll probably want to change the following items:
//
// - title (the site title, which you will likely want to customize)
// - theme (the look and feel of your website, which you may want to change or edit)
// - port (if you already have something running on port 8080)
// - root_path (if you are running Limetree as a system service)
//
// Most of these parameters can be overridden on the command line if for some reason you don't wish
// to edit the configuration file.
// The site title is displayed in several prominent locations, like tabs, bookmarks, and the site
// header.
//
// Default: "Limetree CMS"
site_title "Limetree CMS"
// Your theme controls how your pages look and any additional features. The "simple" theme is
// bundled within the Limetree executable (i.e., it does not need to be installed; Limetree will
// extract and use it automatically).
//
// If you would like to develop a new theme, make a copy of the "themes/simple" directory with a
// different name, then edit the copy. This way you can reference back to the original theme if
// anything breaks.
//
// Default: "simple"
theme_name "simple"
// This is the host address that Limetree will bind to. Use 127.0.0.1 or localhost to make
// Limetree available only on the local machine, or an explicit IP address to expose it to the
// network. Generally you should bind to localhost and reverse-proxy from a dedicated web server
// like nginx.
//
// Default: "127.0.0.1"
host "127.0.0.1"
// This is the host port that Limetree will bind to. If you already have another service running
// on port 8080, you can change it to anything between 1024 and 65535.
//
// Default: 8080
port 8080
// This is the filter applied to Limetree's log messages. This can also be configured via the
// RUST_LOG environment variable, which in turn can be overridden by the --logging command line
// switch. The filter syntax can be found here:
//
// https://docs.rs/tracing-subscriber/latest/tracing_subscriber/filter/struct.EnvFilter.html#directives
//
// Default: "info"
logging "info"
// This is an alternate location for Limetree to store its data files. By default this folder is
// placed in the current user's local persistent application data directory, which is
// "%LocalAppData%\echowritescode\limetree" on Windows,
// "${HOME}/Library/Application Support/dev.echowritescode.limetree" on macOS, or
// "${XDG_DATA_HOME}/limetree" on Linux.
//
// If you are running Limetree as a system service, you will likely want to change this to another
// directory such as "/srv/limetree".
//
// Default: #null (platform specific location)
root_path #null
// This is an alternate location for Limetree to store content files specifically (i.e., the pages
// you create and edit, as well as file uploads). Normally, these go in a folder called "content"
// under the Limetree root directory.
//
// Default: #null (platform specific location)
content_path #null
// This is an alternate location for Limetree to store its metadata file, which stores things like
// page titles and tag associations. Normally, this is a file called "metadata.json" under the
// Limetree root directory.
//
// Default: #null (platform specific location)
metadata_path #null
// This is an alternate location for theme files. Normally, these go in a folder called "themes"
// under the Limetree root directory.
//
// Default: #null (platform specific location)
themes_path #null