Okay, did the migration just now. Everything seems a little more responsive, but I wouldn’t call it way faster.
Either way, it wasn’t very scary at all. For anybody coming after me:
- add postgres container to compose file like so. I named mine “postgres”, added a “postgres” volume, and added it to depends_on for app and cron
- run migration command from nextcloud app container like any other occ command and check admin settings/system for db state:
./occ db:convert-type --password $POSTGRES_PASSWORD --all-apps pgsql $POSTGRES_USER postgres $POSTGRES_DB - remove old “db” container and volume and all references to it from compose file and run
docker compose up -d --remove-orphans
haplo@lemmy.world 10 months ago
Thank you for this. I really dislike MySQL/MariaDB and favor SQLite whenever possible, or PostgreSQL otherwise. The DB migration of my Nextcloud instance was high in my to-do list, and your instructions saved me research time.
tofubl@discuss.tchncs.de 10 months ago
Here’s a cool article I found on Nextcloud performance improvements, and connecting Redis over Unix sockets gave me a more substantial performance improvement than migrating to Postgres. Very happy I fell down this rabbit hole today.
To note if you’re following the tutorial in the link above, and for people using the nextcloud:stable container together with the recommended cron container:
config/config.php, as well asconfig/redis.config.php/etc/localtimeand/etc/timezonevolumes the app container did, as well as thevolumes_from: tmphaplo@lemmy.world 10 months ago
Thank you for the link and the Redis pointers. I should double check that my Nextcloud setup is using Redis, it might well be misconfigured.
sj_zero 10 months ago
If you do end up using postgresql, over time the database could end up getting fragmented and that can lead to increased latency, so routine pg_repacks imo are a worthwhile thing to schedule.