docs: Remove "great table", make suggestions on layout

This commit is contained in:
Julian-Samuel Gebühr 2023-03-15 13:27:25 +01:00
parent b59d845b29
commit bdeabeffab

View file

@ -1,18 +1,20 @@
# Configuring DNS # Configuring DNS
To reach your services, you'd need to do some DNS configuration. To reach your services, you'd need to do some DNS configuration. We recommend you set up at least one (sub-)domain. Each service can be hostet at a subpath of this domain or on separate (sub-)domains.
## DNS settings example A simple example could be this
The DNS setup is dependent on which services you want to activate. You need t oset the first entry and an entry for each | Service | Type | Host | Target |
service you activate that needs a (sub-)domain. Feel free to adjust the host to you liking (you can even use a separate domain). |-----------------------|-------|---------------------|---------------------|
| Miniflux and radicale | A | `mash.example.com` | `IP of your server` |
| Nextcloud | CNAME | `cloud.example.com` | `mash.example.com` |
| Service | Type | Host | Target | Here you could reach the feedreader miniflux at https://mash.example.com/miniflux (if you set
|-------------|-------|------------------------|---------------------| `miniflux_path_prefix: /miniflux` in your `vars.yml`) and radicale at https://mash.example.com/radicale. In the example
| - | A | `example.com` | `IP of your server` | the nextcloud has a different subdomain, so you could access it at https://cloud.example.com
| Radicale | CNAME | `calendar.example.com` | `example.com` |
| Miniflux | CNAME | `feed.example.com` | `example.com` | Feel free to change this as you like, just make sure that you set `<service>_hostname` and `<service>_path_prefix`
| Uptime-kuma | CNAME | `status.example.com` | `example.com` | accordingly in your `vars.yml`.
Be mindful as to how long it will take for the DNS records to propagate. Be mindful as to how long it will take for the DNS records to propagate.