Self-hosted docker-compose breaking changes - file uploads

[basiljelly]

I went to download some files I uploaded a few weeks ago on another device (different from the device I uploaded the file on) and I was getting the error There was an error while downloading the file.

I checked the uploads directory on my self-hosted instance and noticed that there were no new files added to the directory for the files I was having issues with downloading. I tested uploading a new file and the interface said everything was successful, yet there was no new file in the uploads directory.

The issue ended up being that I had this path in my docker-compose from when I performed the initial install: - ./uploads:/opt/bundled/files/packages/files/dist/upload. I checked the recent docker-compose example and the path is now - ./uploads:/opt/server/packages/files/dist/uploads.

When I try to delete the file, I get the error Unable to Delete.

Maybe the file was temporarily written to the wrong directory, so the app thought it was successfully uploaded and wrote the record to the database? Another check to verify the uploaded files are actually uploaded would be useful to have, so the frontend interface can throw an error before uploading and losing more files.

I also understand it was my issue for not checking for updates to docker-compose before updating. I think it would be helpful to update this page - https://standardnotes.com/help/self-hosting/docker under "Updating your server:
" to note that localstack_bootstrap.sh and docker-compose.yml should be checked for updates before performing a pull.