Nice! A
-
-
Is it possible to install following your guide on another provider(Linode, Vultr etc) instead of the DigitalOcean?
Regards.
-
Steps 3 and 4 of guide apply for any provider as long as docker compose is available and domain was already configured :)
-
I've updated the installation guide to reflect changes in DigitalOcean's platform. Also I've changed my recommendation from 2GB to 1GB of memory, because thats quite a lot already for Misago.
-
...on my podman install, running a fairly active community with around 75 members, I am finding that misago runs consistently at just over 1GB memory. 1.1Gb in fact. (thats four components - misago, celery, nginx and redis)
-
Can you share what memory usage you are seeing from those? For this forum peaks are 450 for Misago, 200 for Celery, 80 for PostgreSQL, 40 for nginx and 20 for Redis This leaves 200megs for rest of Droplet.
-
....I think it will depend on the number of users with active connections (which I don't know how to measure). My current numbers are (in GB's):
celery: 0.581
misago: 0.510
nginx: 0.00154
redis: 0.00727That is about 5% of my server capacity, and CPU is broadly in the 5% arena, with misago roughly consuming 10-20 times more than the other three components.
That doesn't include postgresql usage, the reverse proxy (caddy 2), and authorisation and identity backend (authelia backed with ldap), all of which are independent system wide services that have some resource consumption attributable to misago.
Clearly my podman setup is not a direct correlation to your docker-compose automated install.
-
its good