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
- DeploymentStatus enum value `canceled` m...
Hey, Sorry if it has been reported already, I found an issue using the Dart SDK where the `canceled` enum value is missing from `DeploymentStatus`. This causes...
- Synchronous function execution timeout w...
I am calling server functions with xasync = true and I still get this error message. Synchronous function execution timed out. Use asynchronous execution inste...
- Function running for more than 2 hours i...
This is my projectID: 669fe01b003800dd0503 Cloud functionID is 696ea05400147eb8eb3b I hope this doesn't count against my GB-hours?