1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
Backoffice
==========
This is technical documentation about the internal workings of Fossil.
Ordinary Fossil users do not need to know about anything covered by this
document. The information here is intended for people who want to enhance
or extend the Fossil code, or who just want a deeper understanding of
the internal workings of Fossil.
What Is The Backoffice
----------------------
The backoffice is a mechanism used by a
[Fossil server](/doc/trunk/www/server.wiki) to do low-priority
background work that is not directly related to the user interface. Here
are some examples of the kinds of work that backoffice performs:
1. Sending email alerts and notifications
2. Sending out daily digests of email notifications
3. Other background email handling chores
4. Automatic syncing of peer repositories
|
|
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
Backoffice
==========
This is technical documentation about the internal workings of Fossil.
Ordinary Fossil users do not need to know about anything covered by this
document. The information here is intended for people who want to enhance
or extend the Fossil code, or who just want a deeper understanding of
the internal workings of Fossil.
What Is The Backoffice
----------------------
The backoffice is a mechanism used by a
[Fossil server](./server/) to do low-priority
background work that is not directly related to the user interface. Here
are some examples of the kinds of work that backoffice performs:
1. Sending email alerts and notifications
2. Sending out daily digests of email notifications
3. Other background email handling chores
4. Automatic syncing of peer repositories
|
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
This happens for every webpage, regardless of how that webpage is launched,
and regardless of the purpose of the webpage. This also happens on the
server for "[fossil sync](/help?cmd=sync)" and
[fossil clone](/help?cmd=clone)" commands which are implemented as
web requests - albeit requests that the human user never sees.
Web requests can arrive at the Fossil server via direct TCP/IP (for example
when Fossil is started using commands like "[fossil server](/help?cmd=server)")
or via [CGI](/doc/trunk/www/server.wiki) or
[SCGI](/doc/trunk/www/scgi.wiki) or via SSH.
A backoffice process might be started regardless of the origin of the
request.
The backoffice is not a daemon. Each backoffice process runs for a short
while and then exits. This helps keep Fossil easy to manage, since there
are no daemons to start and stop. To upgrade Fossil to a new version,
you simply replace the older "fossil" executable with the newer one, and
|
|
|
|
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
This happens for every webpage, regardless of how that webpage is launched,
and regardless of the purpose of the webpage. This also happens on the
server for "[fossil sync](/help?cmd=sync)" and
[fossil clone](/help?cmd=clone)" commands which are implemented as
web requests - albeit requests that the human user never sees.
Web requests can arrive at the Fossil server via direct TCP/IP (for example
when Fossil is started using commands like "[fossil server](/help?cmd=server)")
or via [CGI](./server/any/cgi.md) or
[SCGI](./server/any/scgi.md) or via SSH.
A backoffice process might be started regardless of the origin of the
request.
The backoffice is not a daemon. Each backoffice process runs for a short
while and then exits. This helps keep Fossil easy to manage, since there
are no daemons to start and stop. To upgrade Fossil to a new version,
you simply replace the older "fossil" executable with the newer one, and
|