Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Update the documentation on the "fossil backoffice" command. |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
35c8103e6d90413072d1e2720888dce1 |
User & Date: | drh 2019-03-08 00:42:43 |
Context
2019-03-14
| ||
13:52 | When doing a "fossil stash" make sure that the stash has committed before deleting changes from disk, so that the changes can be recovered if something goes wrong. ... (check-in: 60af514d user: drh tags: trunk) | |
2019-03-09
| ||
21:57 | Initial check-in of the documentation for the proposed VCCP. Very incomplete. This is just to save my work. ... (check-in: b37bb7dc user: drh tags: vccp) | |
2019-03-08
| ||
00:42 | Update the documentation on the "fossil backoffice" command. ... (check-in: 35c8103e user: drh tags: trunk) | |
2019-03-07
| ||
17:57 | Add the --poll option to "fossil backoffice" to allow it to act as a backoffice launch daemon. ... (check-in: 1021afc6 user: drh tags: trunk) | |
Changes
Changes to www/backoffice.md.
︙ | ︙ | |||
75 76 77 78 79 80 81 | 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: | | | 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 | 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 per day from random robots, which will be sufficient to kick off the daily digest emails. And even for a private server, if there is very little traffic, then the daily digests are probably a no-op anyhow |
︙ | ︙ |