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
|
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
|
-
+
-
+
-
+
|
<title>Unversioned Content</title>
<h1 align="center">Unversioned Content</h1>
"Unversioned content" or "unversioned files" are
files stored in a Fossil repository without history.
Only the newest version of each unversioned file is retained.
Though history is omitted, unversioned content is synced between
respositories. In the event of a conflict during a sync, the most recent
repositories. In the event of a conflict during a sync, the most recent
version of each unversioned file is retained and older versions are discarded.
Unversioned files are useful for storing ephemeral content such as builds
or frequently changing web pages.
The [https://www.fossil-scm.org/fossil/uv/download.html|download] page of
the self-hosting Fossil repository is stored 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: "http://domain/cgi-script/<b>uv</b>/<i>FILENAME</i>".
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 mimetype is inferred from the filename suffix.
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 is synced between respositories, though not by default.
Unversioned content is synced between repositories, though not by default.
Special commands or command-line options are required.
Unversioned content can be synced using the following commands:
<blockquote><pre>
fossil sync <b>-u</b>
fossil clone <b>-u</b> <i>URL local-repo-name</i>
fossil unversioned sync
|