conduit/docs/SUMMARY.md

# Summary

- [Introduction](introduction.md)

- [Configuration](configuration.md)
- [Delegation](delegation.md)
- [Deploying](deploying.md)
    - [Generic](deploying/generic.md)
    - [Debian](deploying/debian.md)
    - [Docker](deploying/docker.md)
    - [NixOS](deploying/nixos.md)
- [Administration](administration.md)
    - [Media](administration/media.md)
- [TURN](turn.md)
- [Appservices](appservices.md)
- [FAQ](faq.md)
docs: build docs using mdBook 2024-03-13 18:01:41 +01:00			`# Summary`

			`- [Introduction](introduction.md)`

chore(docs): Rename configuration section to `Configuration` 2024-04-18 02:35:14 +03:00			`- [Configuration](configuration.md)`
docs: delegation 2024-05-02 09:27:14 +01:00			`- [Delegation](delegation.md)`
make chapter name reflect file name Personally I think this makes more sense anyway. 2024-03-21 15:42:36 -07:00			`- [Deploying](deploying.md)`
rename "simple" deployment to "generic" The main thing this section is really useful for is explaining how to configure various reverse proxies, which applies to basically anything. Also, remove all the language about this being "recommended", because nothing in this documentation is actually tested in CI. 2024-03-21 15:22:53 -07:00			`- [Generic](deploying/generic.md)`
docs: build docs using mdBook 2024-03-13 18:01:41 +01:00			`- [Debian](deploying/debian.md)`
			`- [Docker](deploying/docker.md)`
reduce scope of nixos documentation There are so many ways to do this we realistically shouldn't bother describing any of them, especially because people should be learning all the options and choosing the one that suits them best anyway. 2024-03-21 15:25:34 -07:00			`- [NixOS](deploying/nixos.md)`
docs: guide to moderating media 2025-05-07 13:03:55 +01:00			`- [Administration](administration.md)`
			`- [Media](administration/media.md)`
docs: build docs using mdBook 2024-03-13 18:01:41 +01:00			`- [TURN](turn.md)`
			`- [Appservices](appservices.md)`
docs: add FAQ 2024-04-27 11:26:12 +01:00			`- [FAQ](faq.md)`