I edited .env file and set it to 5 minutes. Afterwards, I did docker compose down and docker compose up -d but I dont notice the containers being destroyed even tho they are up for like 18 hours and run every 20-30 minutes..
that maintenance interval doesn't actually affect those runtime containers
You need to look at these:
_APP_FUNCTIONS_INACTIVE_THRESHOLD_APP_FUNCTIONS_MAINTENANCE_INTERVALhttps://appwrite.io/docs/advanced/self-hosting/environment-variables#functions
oh π
right i am dumb lmao lemme try those
i read the description i am kind of confused between the two
so i did get what inactive threshold is supposed to do
maintenance would just restart as an extra step?
No that one determines how often the check is done
This one is during the check, which ones are removed
ohh i see now gotcha
thanks
[CLOSED] Maintenance Interval not Recreating Containers
Recommended threads
- Unable to create Sites or Functions with...
Heya, I was looking at the appwrite documentation for Sites API with the server api: https://appwrite.io/docs/references/cloud/server-nodejs/sites I canβt fin...
- Triggers and call function in function p...
Hello, Today we are experiencing several issues with Appwrite Cloud. Functions triggered by events, or functions called from another function, are taking an e...
- Functions executed by events does not ap...
Hello, Running self-hosted Appwrite version 1.9.0 (with console 7.8.26). When functions are triggered by an event (eg. databases.\*tables.\*.rows.\*.create) doe...