archive/theorangeone.net-legacy
1
Fork 0
Code Activity

Add clickhouse warning to main plausible post

Browse source
This commit is contained in:
Jake Howard 2021-02-22 21:17:20 +00:00
parent 00cdbb9f84
commit 8f19781913
Signed by: jake
GPG key ID: 57AFB45680EDD477
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
content/posts/self-hosting-plausible/index.md
View file

@ -58,6 +58,10 @@ environment:
Here's my full [`docker-compose.yml`](https://github.com/RealOrangeOne/infrastructure/blob/master/ansible/roles/plausible/files/docker-compose.yml) for reference. Here's my full [`docker-compose.yml`](https://github.com/RealOrangeOne/infrastructure/blob/master/ansible/roles/plausible/files/docker-compose.yml) for reference.
{{<block warning>}}
Clickhouse can be incredibly resource-intensive unless [configured correctly]({{< relref "calming-down-clickhouse" >}}). Unless constrained and configured properly, it will happily consume almost all the storage and compute resources it's given.
{{</block>}}
### Migration and admin setup ### Migration and admin setup
This is the point we diverge pretty hard from what's defined in both the `docker-compose.yml` and `HOSTING.md` from Plausible. The instructions there note a `setup` container, which is used to initialize Plausible, but then shouldn't be run afterwards. Personally I don't like this pattern, I'd rather the compose file contain exactly what's needed to run the application, no more no less. Instead, we need to set up the databases manually: This is the point we diverge pretty hard from what's defined in both the `docker-compose.yml` and `HOSTING.md` from Plausible. The instructions there note a `setup` container, which is used to initialize Plausible, but then shouldn't be run afterwards. Personally I don't like this pattern, I'd rather the compose file contain exactly what's needed to run the application, no more no less. Instead, we need to set up the databases manually: