helmi is having trouble using a mounted volume for backups in Discourse, encountering server errors when trying to read or create backup files after symlinking and copying ownership. bartv advises configuring the mounted volumes directly in the app.yml file, providing an example that maps /mnt/discourse-data/backups on the host to /shared/backups in the container, which should resolve the issue by ensuring proper volume mounting instead of relying on symlinks.
I’m trying to use a mounted volume for my backups but I can’t seem to get it right. I tried mounting the volume into place (/var/discourse/shared/standalone/backups/default) and tried symlinking the default folder to a different mount folder. I copied the ownership of files and folder over as much as I could see but all I get is a server error in the admin backup section. It can’t seem to read the existing backup files that I copied over and also can’t create new ones there.