appwrite: 🐛 Bug Report: All function files are deleted when the container is stopped
👟 Reproduction steps
- Deploy a cloud function for a project (Just a simple Hello World output)
- Run
docker-compose down - Run
docker-compose up -d - Try to execute the function. There will be an error with the string:
File Not Found - Deploy the same function again
- Now executions are working
👍 Expected behavior
I would expect that after rebooting the containers, you don’t have to redeploy all the functions every time. For large projects, that could be a lot.
👎 Actual Behavior
Currently, you have to redeploy the functions after each container restart. Otherwise they do not work and return “File not found”. The programming language of the function does not seem to matter. I tested it with DART and PHP functions.
🎲 Appwrite version
Version 0.13.x
💻 Operating system
MacOS
🧱 Your Environment
No special customizations.
👀 Have you spent some time to check if this issue has been raised before?
- I checked and didn’t find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (11 by maintainers)
Found it 🥳 We will need to sync our development and production docker-compose, as there are some mismatches around volumes, environment variables, and versions.
The solution to this problem can be seen in this gist: https://gist.github.com/Meldiron/1ac493328141210da950e40d9c3cb568/revisions
Check out the latest revision and apply these changes to your
docker-compose.yml. Then, restart appwrite withdocker-compose down && docker-compose up -d. After Appwrite starts, make sure to redeploy your functions, and from now on, your functions should not lose deployments if you restart Appwrite 😍Never mind, the problem is there on 0.13.2, but not on master branch. With next release, the bug will most likely be fixed.
i can confirm, everything is fine now! 😉
I can confirm this occurs with 0.13.3 when using Docker images. If started from source code (same version), it works fine. Whoof, this one will be interesting… 🤔