mirror of
https://forgejo.ellis.link/continuwuation/continuwuity.git
synced 2026-11-13 12:16:54 +00:00
fix(docs): Small fixes
This commit is contained in:
1 parent
d0ca302347
commit
3c3e3b5316
4 files changed
+5
-4
No files matched your search
@@ -58,4 +58,4 @@ where `<name>` one of the output of `appservices list`.
|
||||
|
||||
### Docker DNS
|
||||
|
||||
If you follow the [DNS tuning guide](./guides/dns.mdx#for-docker-users) and mount a custom `/etc/resolv.conf`, you may not be able to connect to appservices containers via hostname. Follow the workaround [there](./guides/dns.mdx#breaking-resolution-with-container-hostnames) to connect to your appservice via static IPs.
|
||||
If you follow the [DNS tuning guide](./guides/dns.mdx#for-docker-users) and mount a custom `/etc/resolv.conf`, you may not be able to connect to appservices containers via hostname. Follow the workaround [there](./guides/dns.mdx#for-docker-users) to connect to your appservice via static IPs.
|
||||
@@ -63,7 +63,7 @@ See the [reference configuration](../reference/config) page for all config optio
|
||||
These examples include reverse proxy configurations for Matrix federation, which will route your Matrix domain (and optionally .well-known paths) to Continuwuity.
|
||||
|
||||
:::note Docker DNS Performance
|
||||
Docker's default DNS resolver are known to [cause timeout issues](../troubleshooting#dns-issues) for Matrix federation. To bypass it and use a more performant resolver, we will mount a custom `/etc/resolv.conf` config file into the Continuwuity container.
|
||||
Docker's default DNS resolver are known to [**cause timeout issues**](../troubleshooting#dns-issues) for Matrix federation. To bypass it and use a more performant resolver, we will mount a custom `/etc/resolv.conf` config file into the Continuwuity container.
|
||||
|
||||
```yaml title='docker-compose.yml'
|
||||
services:
|
||||
|
||||
@@ -42,7 +42,7 @@ running compaction is not recommended, or compaction via a timer, due to
|
||||
creating unnecessary I/O amplification. RocksDB is built with io_uring support
|
||||
via liburing for improved read performance.
|
||||
|
||||
RocksDB troubleshooting can be found [in the RocksDB section of
|
||||
RocksDB troubleshooting can be found [in the RocksDB section of
|
||||
troubleshooting](./troubleshooting.mdx#rocksdb--database-issues).
|
||||
|
||||
### Compression
|
||||
@@ -103,7 +103,6 @@ To restore a backup from an online RocksDB backup:
|
||||
if you have multiple) to your new directory
|
||||
- Set your `database_path` config option to your new directory, or replace your
|
||||
old one with the new one you crafted
|
||||
- Verify that
|
||||
- Start up Continuwuity again and it should open as normal
|
||||
|
||||
Note: You can verify the necessary files to copy by comparing them with contents in the `$DATABASE_BACKUP_PATH/meta/1` (or latest backup number) file.
|
||||
|
||||
@@ -2,6 +2,8 @@
|
||||
|
||||
This configuration file reflect latest developments on the `main` branch. To check the file from a specific Continuwuity version, browse the [tags](https://forgejo.ellis.link/continuwuation/continuwuity/tags) and view the `conduwuit-example.toml` file there.
|
||||
|
||||
---
|
||||
|
||||
```toml file="../../conduwuit-example.toml"
|
||||
|
||||
```
|
||||
Reference in new issue
Block a user