heads up: test your docker volume mapping before first boot
Heads up for anyone bringing up a fresh self-hosted instance with Docker.
I reproduced a case where the app booted cleanly but uploads never persisted because the volume mapping was pointed at the wrong host path. The fix was to stop the container, correct the bind mount, and start again with the same environment variables. If you're using a custom app.yml equivalent, double-check the file storage path before importing content. This is one of those issues that looks like a permissions problem until you inspect the mount.
0
Comments
-
Saved me a lot of time. I had the same symptom and thought it was S3 config at first.
0
