update readme

README.md

@@ -25,6 +25,7 @@ some kind of hosting setup
 specifics for everything
 
 **currently serving**
+
 - via docker
   - **caddy** – http server & reverse proxy
   - **stalwart** – mailserver
@@ -34,6 +35,7 @@ specifics for everything
   - `post.yaoi.dog` – mail (webmail)
 
 **dns setup**
+
 | type  | host      | value                       | notes                      |
 |-------|-----------|---------------------------- |----------------------------|
 | `A`   | `@`       | `<ip>`                      | apex domain                |
@@ -44,6 +46,7 @@ specifics for everything
 ### stalwart
 
 **first setup**
+
 1. server identity
     - server hostname: `mail.yaoi.dog`
     - default email domain: `yaoi.dog`
@@ -61,12 +64,14 @@ specifics for everything
     - description: `porkbun`
 
 **further setup**
+
 - settings -> security -> allowed ips
   - added `172.18.0.0/24`; reason: `internal`
 - settings -> network -> http -> security
   - permissive cors policy: `true`   **[restart needed]**
 
 **useful links**
+
 - https://stalw.art/docs
 - https://testconnectivity.microsoft.com/tests/Imap/input
 - https://mail-tester.com
@@ -74,6 +79,7 @@ specifics for everything
 ### bulwark
 
 **useful links**
+
 - https://bulwarkmail.org/docs
 
 ## backups
@@ -83,6 +89,7 @@ backups are done with [vykar](https://vykar.borgbase.com) to [borgbase](https://
 always remember to `docker compose stop` before doing any of this!
 
 **creating**
+
 - if on a new borgbase repo, run `vykar init` first
 - to back up, run `sudo vykar backup` (sudo required as we are accessing `/var/lib/docker/volumes/`)
 - to back up automatically, run `sudo EDITOR=micro crontab -e` and add the following:
@@ -92,6 +99,7 @@ always remember to `docker compose stop` before doing any of this!
   ```
 
 **restoring**
+
 the restore process is kind of fucked up but doable
 
 - restore on new system