Fossil SCM
Added "id"s to every header tag in the forum.wiki document, so you can create links to sub-sections.
Commit
03c298dcb9deab7ff02c78d13d37d8dcbc6db0cac04cac96c88f9ee83a086e30
Parent
e00cdbe7024b105…
1 file changed
+11
-11
+11
-11
| --- www/forum.wiki | ||
| +++ www/forum.wiki | ||
| @@ -119,13 +119,13 @@ | ||
| 119 | 119 | need to do duplicate configuration, such as to point Fossil at your |
| 120 | 120 | server's TLS certificate private key in order to support users |
| 121 | 121 | behind mail servers that require STARTTLS encryption. |
| 122 | 122 | |
| 123 | 123 | |
| 124 | -<h2>Setting up a Fossil Forum</h2> | |
| 124 | +<h2 id="setup">Setting up a Fossil Forum</h2> | |
| 125 | 125 | |
| 126 | -<h3>Permissions</h3> | |
| 126 | +<h3 id="caps">Capabilities</h3> | |
| 127 | 127 | |
| 128 | 128 | Fossil forums use the same role-based access control mechanism as |
| 129 | 129 | for normal Fossil repository logins. |
| 130 | 130 | |
| 131 | 131 | There are several dedicated forum-related capability bits you can grant |
| @@ -225,11 +225,11 @@ | ||
| 225 | 225 | </verbatim> |
| 226 | 226 | |
| 227 | 227 | That overlays the background with 5% white to lighten it slightly. |
| 228 | 228 | |
| 229 | 229 | |
| 230 | -<h3>Enable Forum Search</h3> | |
| 230 | +<h3 id="search">Enable Forum Search</h3> | |
| 231 | 231 | |
| 232 | 232 | One of the underlying assumptions of the forum feature is that you will |
| 233 | 233 | want to be able to search the forum archives, so the <tt>/forum</tt> |
| 234 | 234 | page always includes a search box. Since that depends on search being |
| 235 | 235 | enabled on the Fossil repository, Fossil warns that search is disabled |
| @@ -239,11 +239,11 @@ | ||
| 239 | 239 | You may want to enable some of the other Fossil search features while |
| 240 | 240 | you're in there. All of this does come at some CPU and I/O cost, which |
| 241 | 241 | is why it's disabled by default. |
| 242 | 242 | |
| 243 | 243 | |
| 244 | -<h3>Single Sign-On</h3> | |
| 244 | +<h3 id="sso">Single Sign-On</h3> | |
| 245 | 245 | |
| 246 | 246 | If you choose to host your discussion forums within the same repository |
| 247 | 247 | as your project's other Fossil-managed content, you inherently have a |
| 248 | 248 | single sign-on system. Contrast third-party mailing list and forum |
| 249 | 249 | software where you either end up with two separate user tables and |
| @@ -264,11 +264,11 @@ | ||
| 264 | 264 | has been a feature of Fossil since April of 2011: Admin → |
| 265 | 265 | Login-Group. This allows one Fossil repository to recognize users |
| 266 | 266 | authorized on a different Fossil repository. |
| 267 | 267 | |
| 268 | 268 | |
| 269 | -<h3>Email Notification</h3> | |
| 269 | +<h3 id="alerts">Email Notifications (Alerts)</h3> | |
| 270 | 270 | |
| 271 | 271 | The detailed information for this feature of Fossil is in two other |
| 272 | 272 | documents: |
| 273 | 273 | |
| 274 | 274 | * [./alerts.md | Email Alerts] |
| @@ -277,11 +277,11 @@ | ||
| 277 | 277 | You may want to study those in detail, since email is complicated. Some |
| 278 | 278 | of that complexity necessarily leaks out to the configuration of email |
| 279 | 279 | notification in Fossil. |
| 280 | 280 | |
| 281 | 281 | |
| 282 | -<h4>Quick Setup</h4> | |
| 282 | +<h4 id="quick">Quick Setup</h4> | |
| 283 | 283 | |
| 284 | 284 | However, if you've already got a working Postfix, Exim, or Sendmail |
| 285 | 285 | server on the machine running your Fossil instance(s), and you aren't |
| 286 | 286 | using Fossil's <tt>chroot</tt> feature to wall it off from the rest of |
| 287 | 287 | the machine, it's fairly simple to set up email notifications: |
| @@ -343,11 +343,11 @@ | ||
| 343 | 343 | Pending Alerts: 0 normal, 0 digest |
| 344 | 344 | Subscribers: 0 active, 0 total |
| 345 | 345 | </verbatim> |
| 346 | 346 | |
| 347 | 347 | |
| 348 | -<h4>Subscribe to Alerts</h4> | |
| 348 | +<h4 id="subscribe">Subscribe to Alerts</h4> | |
| 349 | 349 | |
| 350 | 350 | Above, we see that there are no subscribers, so the next step is to add |
| 351 | 351 | one. |
| 352 | 352 | |
| 353 | 353 | Go to the <tt>/alerts</tt> page on your Fossil instance and sign your |
| @@ -366,11 +366,11 @@ | ||
| 366 | 366 | by the way: a user can be signed up for email alerts without having a |
| 367 | 367 | full-fledged Fossil user account. Only when both user names are the same |
| 368 | 368 | are the two records tied together under the hood. |
| 369 | 369 | |
| 370 | 370 | |
| 371 | -<h4>Test the Email Subsystem</h4> | |
| 371 | +<h4 id="alert-test">Test the Email Subsystem</h4> | |
| 372 | 372 | |
| 373 | 373 | If you'd rather not create an inane "testing" post in your Fossil |
| 374 | 374 | instance just to force out an email alert, we can test the email |
| 375 | 375 | subsystem separately from the rest of the Fossil email alerts system |
| 376 | 376 | with the following command: |
| @@ -386,11 +386,11 @@ | ||
| 386 | 386 | |
| 387 | 387 | That command assumes that your project [./foss-cklist.wiki | contains a |
| 388 | 388 | readme file]. Of course it does. Why would it not? |
| 389 | 389 | |
| 390 | 390 | |
| 391 | -<h4>Frist Post</h4> | |
| 391 | +<h4 id="frist" name="first">First Post</h4> | |
| 392 | 392 | |
| 393 | 393 | Since you've already edited the skin per [#skin | the instructions |
| 394 | 394 | above], you can click the "Forum" link in the navbar and create a new |
| 395 | 395 | post. I suggest taking the time to compose a suitable introductory |
| 396 | 396 | message especially for your project's forum, one which a new user would |
| @@ -398,11 +398,11 @@ | ||
| 398 | 398 | |
| 399 | 399 | Wait a few seconds, and you should receive a notification email with the |
| 400 | 400 | post's subject and body text in the email. |
| 401 | 401 | |
| 402 | 402 | |
| 403 | -<h4>Troubleshooting</h4> | |
| 403 | +<h4 id="trouble">Troubleshooting</h4> | |
| 404 | 404 | |
| 405 | 405 | If email alerts aren't working, there are several useful commands you |
| 406 | 406 | can give to figure out why. |
| 407 | 407 | |
| 408 | 408 | (Be sure to [#cd | <tt>cd</tt> into a repo checkout directory] first!) |
| @@ -462,11 +462,11 @@ | ||
| 462 | 462 | |
| 463 | 463 | This only does the same thing as the final command above, rather than |
| 464 | 464 | send you an ale, as you might be hoping. Sorry. |
| 465 | 465 | |
| 466 | 466 | |
| 467 | -<h2>Moderation</h2> | |
| 467 | +<h2 id="moderation">Moderation</h2> | |
| 468 | 468 | |
| 469 | 469 | Fossil forum moderation is easy: |
| 470 | 470 | |
| 471 | 471 | <ol> |
| 472 | 472 | <li>Add the <b>Moderate Forum</b> (<tt>5</tt>) capability to any of |
| 473 | 473 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -119,13 +119,13 @@ | |
| 119 | need to do duplicate configuration, such as to point Fossil at your |
| 120 | server's TLS certificate private key in order to support users |
| 121 | behind mail servers that require STARTTLS encryption. |
| 122 | |
| 123 | |
| 124 | <h2>Setting up a Fossil Forum</h2> |
| 125 | |
| 126 | <h3>Permissions</h3> |
| 127 | |
| 128 | Fossil forums use the same role-based access control mechanism as |
| 129 | for normal Fossil repository logins. |
| 130 | |
| 131 | There are several dedicated forum-related capability bits you can grant |
| @@ -225,11 +225,11 @@ | |
| 225 | </verbatim> |
| 226 | |
| 227 | That overlays the background with 5% white to lighten it slightly. |
| 228 | |
| 229 | |
| 230 | <h3>Enable Forum Search</h3> |
| 231 | |
| 232 | One of the underlying assumptions of the forum feature is that you will |
| 233 | want to be able to search the forum archives, so the <tt>/forum</tt> |
| 234 | page always includes a search box. Since that depends on search being |
| 235 | enabled on the Fossil repository, Fossil warns that search is disabled |
| @@ -239,11 +239,11 @@ | |
| 239 | You may want to enable some of the other Fossil search features while |
| 240 | you're in there. All of this does come at some CPU and I/O cost, which |
| 241 | is why it's disabled by default. |
| 242 | |
| 243 | |
| 244 | <h3>Single Sign-On</h3> |
| 245 | |
| 246 | If you choose to host your discussion forums within the same repository |
| 247 | as your project's other Fossil-managed content, you inherently have a |
| 248 | single sign-on system. Contrast third-party mailing list and forum |
| 249 | software where you either end up with two separate user tables and |
| @@ -264,11 +264,11 @@ | |
| 264 | has been a feature of Fossil since April of 2011: Admin → |
| 265 | Login-Group. This allows one Fossil repository to recognize users |
| 266 | authorized on a different Fossil repository. |
| 267 | |
| 268 | |
| 269 | <h3>Email Notification</h3> |
| 270 | |
| 271 | The detailed information for this feature of Fossil is in two other |
| 272 | documents: |
| 273 | |
| 274 | * [./alerts.md | Email Alerts] |
| @@ -277,11 +277,11 @@ | |
| 277 | You may want to study those in detail, since email is complicated. Some |
| 278 | of that complexity necessarily leaks out to the configuration of email |
| 279 | notification in Fossil. |
| 280 | |
| 281 | |
| 282 | <h4>Quick Setup</h4> |
| 283 | |
| 284 | However, if you've already got a working Postfix, Exim, or Sendmail |
| 285 | server on the machine running your Fossil instance(s), and you aren't |
| 286 | using Fossil's <tt>chroot</tt> feature to wall it off from the rest of |
| 287 | the machine, it's fairly simple to set up email notifications: |
| @@ -343,11 +343,11 @@ | |
| 343 | Pending Alerts: 0 normal, 0 digest |
| 344 | Subscribers: 0 active, 0 total |
| 345 | </verbatim> |
| 346 | |
| 347 | |
| 348 | <h4>Subscribe to Alerts</h4> |
| 349 | |
| 350 | Above, we see that there are no subscribers, so the next step is to add |
| 351 | one. |
| 352 | |
| 353 | Go to the <tt>/alerts</tt> page on your Fossil instance and sign your |
| @@ -366,11 +366,11 @@ | |
| 366 | by the way: a user can be signed up for email alerts without having a |
| 367 | full-fledged Fossil user account. Only when both user names are the same |
| 368 | are the two records tied together under the hood. |
| 369 | |
| 370 | |
| 371 | <h4>Test the Email Subsystem</h4> |
| 372 | |
| 373 | If you'd rather not create an inane "testing" post in your Fossil |
| 374 | instance just to force out an email alert, we can test the email |
| 375 | subsystem separately from the rest of the Fossil email alerts system |
| 376 | with the following command: |
| @@ -386,11 +386,11 @@ | |
| 386 | |
| 387 | That command assumes that your project [./foss-cklist.wiki | contains a |
| 388 | readme file]. Of course it does. Why would it not? |
| 389 | |
| 390 | |
| 391 | <h4>Frist Post</h4> |
| 392 | |
| 393 | Since you've already edited the skin per [#skin | the instructions |
| 394 | above], you can click the "Forum" link in the navbar and create a new |
| 395 | post. I suggest taking the time to compose a suitable introductory |
| 396 | message especially for your project's forum, one which a new user would |
| @@ -398,11 +398,11 @@ | |
| 398 | |
| 399 | Wait a few seconds, and you should receive a notification email with the |
| 400 | post's subject and body text in the email. |
| 401 | |
| 402 | |
| 403 | <h4>Troubleshooting</h4> |
| 404 | |
| 405 | If email alerts aren't working, there are several useful commands you |
| 406 | can give to figure out why. |
| 407 | |
| 408 | (Be sure to [#cd | <tt>cd</tt> into a repo checkout directory] first!) |
| @@ -462,11 +462,11 @@ | |
| 462 | |
| 463 | This only does the same thing as the final command above, rather than |
| 464 | send you an ale, as you might be hoping. Sorry. |
| 465 | |
| 466 | |
| 467 | <h2>Moderation</h2> |
| 468 | |
| 469 | Fossil forum moderation is easy: |
| 470 | |
| 471 | <ol> |
| 472 | <li>Add the <b>Moderate Forum</b> (<tt>5</tt>) capability to any of |
| 473 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -119,13 +119,13 @@ | |
| 119 | need to do duplicate configuration, such as to point Fossil at your |
| 120 | server's TLS certificate private key in order to support users |
| 121 | behind mail servers that require STARTTLS encryption. |
| 122 | |
| 123 | |
| 124 | <h2 id="setup">Setting up a Fossil Forum</h2> |
| 125 | |
| 126 | <h3 id="caps">Capabilities</h3> |
| 127 | |
| 128 | Fossil forums use the same role-based access control mechanism as |
| 129 | for normal Fossil repository logins. |
| 130 | |
| 131 | There are several dedicated forum-related capability bits you can grant |
| @@ -225,11 +225,11 @@ | |
| 225 | </verbatim> |
| 226 | |
| 227 | That overlays the background with 5% white to lighten it slightly. |
| 228 | |
| 229 | |
| 230 | <h3 id="search">Enable Forum Search</h3> |
| 231 | |
| 232 | One of the underlying assumptions of the forum feature is that you will |
| 233 | want to be able to search the forum archives, so the <tt>/forum</tt> |
| 234 | page always includes a search box. Since that depends on search being |
| 235 | enabled on the Fossil repository, Fossil warns that search is disabled |
| @@ -239,11 +239,11 @@ | |
| 239 | You may want to enable some of the other Fossil search features while |
| 240 | you're in there. All of this does come at some CPU and I/O cost, which |
| 241 | is why it's disabled by default. |
| 242 | |
| 243 | |
| 244 | <h3 id="sso">Single Sign-On</h3> |
| 245 | |
| 246 | If you choose to host your discussion forums within the same repository |
| 247 | as your project's other Fossil-managed content, you inherently have a |
| 248 | single sign-on system. Contrast third-party mailing list and forum |
| 249 | software where you either end up with two separate user tables and |
| @@ -264,11 +264,11 @@ | |
| 264 | has been a feature of Fossil since April of 2011: Admin → |
| 265 | Login-Group. This allows one Fossil repository to recognize users |
| 266 | authorized on a different Fossil repository. |
| 267 | |
| 268 | |
| 269 | <h3 id="alerts">Email Notifications (Alerts)</h3> |
| 270 | |
| 271 | The detailed information for this feature of Fossil is in two other |
| 272 | documents: |
| 273 | |
| 274 | * [./alerts.md | Email Alerts] |
| @@ -277,11 +277,11 @@ | |
| 277 | You may want to study those in detail, since email is complicated. Some |
| 278 | of that complexity necessarily leaks out to the configuration of email |
| 279 | notification in Fossil. |
| 280 | |
| 281 | |
| 282 | <h4 id="quick">Quick Setup</h4> |
| 283 | |
| 284 | However, if you've already got a working Postfix, Exim, or Sendmail |
| 285 | server on the machine running your Fossil instance(s), and you aren't |
| 286 | using Fossil's <tt>chroot</tt> feature to wall it off from the rest of |
| 287 | the machine, it's fairly simple to set up email notifications: |
| @@ -343,11 +343,11 @@ | |
| 343 | Pending Alerts: 0 normal, 0 digest |
| 344 | Subscribers: 0 active, 0 total |
| 345 | </verbatim> |
| 346 | |
| 347 | |
| 348 | <h4 id="subscribe">Subscribe to Alerts</h4> |
| 349 | |
| 350 | Above, we see that there are no subscribers, so the next step is to add |
| 351 | one. |
| 352 | |
| 353 | Go to the <tt>/alerts</tt> page on your Fossil instance and sign your |
| @@ -366,11 +366,11 @@ | |
| 366 | by the way: a user can be signed up for email alerts without having a |
| 367 | full-fledged Fossil user account. Only when both user names are the same |
| 368 | are the two records tied together under the hood. |
| 369 | |
| 370 | |
| 371 | <h4 id="alert-test">Test the Email Subsystem</h4> |
| 372 | |
| 373 | If you'd rather not create an inane "testing" post in your Fossil |
| 374 | instance just to force out an email alert, we can test the email |
| 375 | subsystem separately from the rest of the Fossil email alerts system |
| 376 | with the following command: |
| @@ -386,11 +386,11 @@ | |
| 386 | |
| 387 | That command assumes that your project [./foss-cklist.wiki | contains a |
| 388 | readme file]. Of course it does. Why would it not? |
| 389 | |
| 390 | |
| 391 | <h4 id="frist" name="first">First Post</h4> |
| 392 | |
| 393 | Since you've already edited the skin per [#skin | the instructions |
| 394 | above], you can click the "Forum" link in the navbar and create a new |
| 395 | post. I suggest taking the time to compose a suitable introductory |
| 396 | message especially for your project's forum, one which a new user would |
| @@ -398,11 +398,11 @@ | |
| 398 | |
| 399 | Wait a few seconds, and you should receive a notification email with the |
| 400 | post's subject and body text in the email. |
| 401 | |
| 402 | |
| 403 | <h4 id="trouble">Troubleshooting</h4> |
| 404 | |
| 405 | If email alerts aren't working, there are several useful commands you |
| 406 | can give to figure out why. |
| 407 | |
| 408 | (Be sure to [#cd | <tt>cd</tt> into a repo checkout directory] first!) |
| @@ -462,11 +462,11 @@ | |
| 462 | |
| 463 | This only does the same thing as the final command above, rather than |
| 464 | send you an ale, as you might be hoping. Sorry. |
| 465 | |
| 466 | |
| 467 | <h2 id="moderation">Moderation</h2> |
| 468 | |
| 469 | Fossil forum moderation is easy: |
| 470 | |
| 471 | <ol> |
| 472 | <li>Add the <b>Moderate Forum</b> (<tt>5</tt>) capability to any of |
| 473 |