|
1
|
<title>Fossil Settings</title> |
|
2
|
|
|
3
|
<h1>Using Fossil Settings</h1> |
|
4
|
|
|
5
|
Settings control the behaviour of fossil. They are set with the |
|
6
|
<tt>fossil settings</tt> command, or through the web interface in |
|
7
|
the Settings page in the Admin section. |
|
8
|
|
|
9
|
For a list of all settings, view the Settings page, or type |
|
10
|
<tt>fossil help settings</tt> from the command line. |
|
11
|
|
|
12
|
|
|
13
|
<h2 id="repo">1.0 Repository settings</h2> |
|
14
|
|
|
15
|
Settings are set on a per-repository basis. When you clone a repository, |
|
16
|
a subset of settings are copied to your local repository. |
|
17
|
|
|
18
|
If you make a change to a setting on your local repository, it is not |
|
19
|
synced back to the server when you <tt>push</tt> or <tt>sync</tt>. If |
|
20
|
you make a change on the server, you need to manually make the change on |
|
21
|
all repositories which are cloned from this repository. |
|
22
|
|
|
23
|
You can also set a setting globally on your local machine. The value |
|
24
|
will be used for all repositories cloned to your machine, unless |
|
25
|
overridden explicitly in a particular repository. Global settings can be |
|
26
|
set by using the <tt>-global</tt> option on the <tt>fossil settings</tt> |
|
27
|
command. |
|
28
|
|
|
29
|
<h2 id="versionable">2.0 "Versionable" settings</h2> |
|
30
|
|
|
31
|
Most of the settings control the behaviour of fossil on your local |
|
32
|
machine, largely acting to reflect your preference on how you want to |
|
33
|
use Fossil, how you communicate with the server, or options for hosting |
|
34
|
a repository on the web. |
|
35
|
|
|
36
|
However, for historical reasons, some settings affect how you work with |
|
37
|
versioned files. These are <tt>clean-glob</tt>, <tt>binary-glob</tt>, |
|
38
|
<tt>crlf-glob</tt> (and its alias <tt>crnl-glob</tt>), <tt>empty-dirs</tt>, |
|
39
|
<tt>encoding-glob</tt>, <tt>ignore-glob</tt>, <tt>keep-glob</tt>, |
|
40
|
<tt>manifest</tt>, and <tt>mimetypes</tt>. The most important is |
|
41
|
<tt>ignore-glob</tt> which specifies which files should be ignored when |
|
42
|
looking for unmanaged files with the <tt>extras</tt> command. |
|
43
|
|
|
44
|
Because these options can change over time, and the inconvenience of |
|
45
|
replicating changes, these settings are "versionable". As well as being |
|
46
|
able to be set using the <tt>settings</tt> command or the web interface, |
|
47
|
you can create versioned files in the <tt>.fossil-settings</tt> |
|
48
|
subdirectory of the check-out root, named with the setting name. |
|
49
|
Each file holds the value of a setting, and these files are checked in, |
|
50
|
committed, merged, and so on, as with any other file. |
|
51
|
|
|
52
|
Where a setting is a list of values, such as <tt>ignore-glob</tt>, you |
|
53
|
can use a newline as a separator as well as a comma. |
|
54
|
|
|
55
|
For example, to set the list of ignored files, create a |
|
56
|
<tt>.fossil-settings/ignore-glob</tt> file where each line contains a |
|
57
|
glob for ignored files. |
|
58
|
|
|
59
|
If you set the value of a setting using the <tt>settings</tt> command as |
|
60
|
well as a versioned file, the versioned setting will take precedence. A |
|
61
|
warning will be displayed. |
|
62
|
|