Fossil

login/logout link in the upper right corner, then go to "Email Alerts".)
You will need "Forum Posts" checked at the least for the testing steps
below.

If you use the same user name and email address as you used for your
normal user login, Fossil will simply tie your alert preferences to your
login, and it will be considered already-verified. Otherwise, Fossil
will create up an alert-only record, and you will have to verify the
email address before Fossil will send notifications to it.

This shows a key aspect of the way Fossil's email alerts system works,
by the way: a user can be signed up for email alerts without having a
full-fledged Fossil user account. Only when both user names are the same
are the two records tied together under the hood.


<h4>Test the Email Subsystem</h4>

If you'd rather not create an inane "testing" post in your Fossil
instance just to force out an email alert, we can check whether the
email subsystem separate from the rest of the Fossil Email Alerts system
is working with the following command:

<verbatim>
    $ fossil alerts test-message you@example.com --body README.md --subject Test
</verbatim>

That should send you an email with "Test" in the subject line and the
contents of your project's <tt>README.md</tt> file in the body. If it
works, the file's contents may be truncated. I'm uncertain whether
that's due to an intentionally-small buffer size or if it's a bug.

That command assumes that your project [./foss-cklist.wiki | contains a
readme file]. Of course it does. Why would it not?


<h4>Frist Post</h4>

Since you've already edited the skin per [#skin | the instructions
above], you can click the "Forum" link in the navbar and create a new
post. I suggest taking the time to compose a suitable introductory
message especially for your project's forum, suitable for pointing new
forum users at.

Wait a few seconds, and you should receive a notification email with the
post's subject and body text in the email.


<h4>Troubleshooting</h4>

</verbatim>

This should also kick off the backoffice processing, if there are any
pending alerts to send out.

<verbatim>
    $ fossil alert pending






    $ fossil test-add-alerts f5900
    $ fossil alert send
</verbatim>

If the first command gives no output and <tt>pending-alerts</tt> in the
earlier command is 0, the second command will add another alert, which
should shortly cause another notification email. The <tt>f</tt> in the
final parameter means you're scheduling a "forum" alert, and the integer
is the ID of a forum post, which you can find by visiting
<tt>/timeline?showid</tt> on your Fossil instance.


The third command above is necessary because the
<tt>test-add-alerts</tt> command doesn't kick off a backoffice run.

<verbatim>
    $ fossil ale send
</verbatim>

This only does the same thing as the final command above, rather than
send you an ale, as you might be hoping. Sorry.


<h2>Moderation</h2>

TODO