Fossil SCM
Update the documentation on the "fossil backoffice" command.
Commit
35c8103e6d90413072d1e2720888dce179a26c803b952474fc158f93b19c294b
Parent
1021afc6aa3ea77…
1 file changed
+1
-1
+1
-1
| --- www/backoffice.md | ||
| +++ www/backoffice.md | ||
| @@ -77,11 +77,11 @@ | ||
| 77 | 77 | being accessed, then the automatic backoffice will never run, and the |
| 78 | 78 | daily digest might not go out until somebody does visit a webpage. |
| 79 | 79 | If this is a problem, an adminstrator can set up a cron job to |
| 80 | 80 | periodically run: |
| 81 | 81 | |
| 82 | -> fossil backoffice -R _REPOSITORY_ | |
| 82 | +> fossil backoffice _REPOSITORY_ | |
| 83 | 83 | |
| 84 | 84 | That command will cause backoffice processing to occur immediately. |
| 85 | 85 | Note that this is almost never necessary for an internet-facing |
| 86 | 86 | Fossil repository, since most repositories will get multiple accesses |
| 87 | 87 | per day from random robots, which will be sufficient to kick off the |
| 88 | 88 |
| --- www/backoffice.md | |
| +++ www/backoffice.md | |
| @@ -77,11 +77,11 @@ | |
| 77 | being accessed, then the automatic backoffice will never run, and the |
| 78 | daily digest might not go out until somebody does visit a webpage. |
| 79 | If this is a problem, an adminstrator can set up a cron job to |
| 80 | periodically run: |
| 81 | |
| 82 | > fossil backoffice -R _REPOSITORY_ |
| 83 | |
| 84 | That command will cause backoffice processing to occur immediately. |
| 85 | Note that this is almost never necessary for an internet-facing |
| 86 | Fossil repository, since most repositories will get multiple accesses |
| 87 | per day from random robots, which will be sufficient to kick off the |
| 88 |
| --- www/backoffice.md | |
| +++ www/backoffice.md | |
| @@ -77,11 +77,11 @@ | |
| 77 | being accessed, then the automatic backoffice will never run, and the |
| 78 | daily digest might not go out until somebody does visit a webpage. |
| 79 | If this is a problem, an adminstrator can set up a cron job to |
| 80 | periodically run: |
| 81 | |
| 82 | > fossil backoffice _REPOSITORY_ |
| 83 | |
| 84 | That command will cause backoffice processing to occur immediately. |
| 85 | Note that this is almost never necessary for an internet-facing |
| 86 | Fossil repository, since most repositories will get multiple accesses |
| 87 | per day from random robots, which will be sufficient to kick off the |
| 88 |