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
|
<title>Unversioned Content</title>
"Unversioned content" or "unversioned files" are
files stored in a Fossil repository without history, meaning
it retains the newest version of each such file, and that alone.
Though it omits history, Fossil does sync unversioned content between
repositories. In the event of a conflict during a sync, it retains
the most recent version of each unversioned file, discarding
older versions.
Unversioned files are useful for storing ephemeral content such as builds
or frequently changing web pages. We store
the [https://fossil-scm.org/home/uv/download.html|download] page of
the self-hosting Fossil repository as unversioned
content, for example.
<h2>Accessing Unversioned Files</h2>
Unversioned files are <u>not</u> a part of a check-out.
Unversioned files are intended to be accessible as web pages using
URLs of the form: "<tt>https://example.com/cgi-script/<b>uv</b>/<i>FILENAME</i></tt>".
In other words, the URI method "<b>uv</b>" (short for "unversioned")
followed by the name of the unversioned file will retrieve the content
of the file. The MIME type is inferred from the filename suffix.
The content of unversioned files can also be retrieved using the
[/help?cmd=unversioned|fossil unvers cat <i>FILENAME</i>] command.
A list of all unversioned files on a server can be seen using
the [/help?cmd=/uvlist|/uvlist] URL. ([/uvlist|example]).
<h2>Syncing Unversioned Files</h2>
Unversioned content does not sync between repositories by default.
One must request it via commands such as:
<pre>
|
>
|
|
|
|
|
|
>
|
|
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
|
<title>Unversioned Content</title>
"Unversioned content" or "unversioned files" are
files stored in a Fossil repository without history, meaning
it retains the newest version of each such file, and that alone.
Unversioned files may have an optional directory name prefix.
Though it omits history, Fossil does sync unversioned content between
repositories. In the event of a conflict during a sync, it retains
the most recent version of each unversioned file, discarding
older versions.
Unversioned files are useful for storing ephemeral content such as
builds or frequently changing web pages. We store the
[https://fossil-scm.org/home/uv/download.html|download] page of the
self-hosting Fossil repository as unversioned content, for
example.
<h2>Accessing Unversioned Files</h2>
Unversioned files are <u>not</u> a part of a check-out.
Unversioned files are intended to be accessible as web pages using
URLs of the form: "<tt>https://example.com/cgi-script/<b>uv</b>/<i>FILENAME</i></tt>".
In other words, the URI method "<b>uv</b>" (short for "unversioned")
followed by the name of the unversioned file will retrieve the content
of the file. The MIME type is inferred from the filename suffix.
The content of unversioned files can also be retrieved using the
[/help?cmd=unversioned|fossil unvers cat <i>FILENAME...</i>]
or [/help?cmd=unversioned|fossil unvers export <i>FILENAME</i>] commands.
A list of all unversioned files on a server can be seen using
the [/help?cmd=/uvlist|/uvlist] URL. ([/uvlist|example].)
<h2>Syncing Unversioned Files</h2>
Unversioned content does not sync between repositories by default.
One must request it via commands such as:
<pre>
|