72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
-------------------------------
The automatic backoffice runs are sufficient for most installations.
However, the daily digest of email notifications is handled by the
backoffice. If a Fossil server can sometimes go more than a day without
being accessed, then the automatic backoffice will never run, and the
daily digest might not go out until somebody does visit a webpage.
If this is a problem, an adminstrator can set up a cron job to
periodically run:
> fossil backoffice _REPOSITORY_
That command will cause backoffice processing to occur immediately.
Note that this is almost never necessary for an internet-facing
Fossil repository, since most repositories will get multiple accesses
|
|
|
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
-------------------------------
The automatic backoffice runs are sufficient for most installations.
However, the daily digest of email notifications is handled by the
backoffice. If a Fossil server can sometimes go more than a day without
being accessed, then the automatic backoffice will never run, and the
daily digest might not go out until somebody does visit a webpage.
If this is a problem, an administrator can set up a cron job to
periodically run:
> fossil backoffice _REPOSITORY_
That command will cause backoffice processing to occur immediately.
Note that this is almost never necessary for an internet-facing
Fossil repository, since most repositories will get multiple accesses
|