Nathaniel Knight

This commit adds support for [Chapel](https://chapel-lang.org/). Per [Chapel's documentation] it supports C-style comments and single or double quoted strings. [Chapel's documentation]: https://chapel-lang.org/docs/language/spec/lexical-structure.html

Tiddly Wiki Server currently always binds to `127.0.0.1:3032`, which is perfectly fine for local development or reverse-proxying, but should be configurable.

At time of submission, TWS uses TiddlyWiki 5.2.2, but the most recent release is 5.3.3, which has a bunch of bug fixes.

Serve the tiddler $:/favicon.ico as at /favicon.ico

1

Per https://tiddlywiki.com/static/Setting%2520a%2520favicon.html: On the server, the [ServerCommand](https://tiddlywiki.com/static/ServerCommand.html) will serve the tiddler [$:/favicon.ico](https://tiddlywiki.com/static/%2524%253A%252Ffavicon.ico.html) at the path /favicon.ico.

Unit tests

1

🤦

Stream the full Wiki?

1

On first page load this server sends the whole TiddlyWiki bundle as well as all of the user's tiddlers. This means allocating several megabtyes of memory (which might not be...

Implement authentication

1

Add: * Tower [middleware](https://www.shuttle.rs/blog/2022/08/04/middleware#axum) for * checking credentials * Performing rate limiting * Storing credentials in the database

[this](https://github.com/ekzhang/bore/blob/main/.github/workflows/ci.yml) seems like a reasonable template.