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_INTERVAL
https://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
- HTTP POST to function returning "No Appw...
Hi everyone, I’m running into an issue with my self-hosted Appwrite instance. I’ve set up my environment variables (APPWRITE_FUNCTION_PROJECT_ID, APPWRITE_FUNC...
- Can't add dart 3.5 runtime
Modified the `.env` to enable dart 3.5 runtime on my self-hosted instance but still can't find the runtime when creating a new function. I manually pulled the i...
- How to verify an user using AppWrite Fun...
I have seen similar questions but none whose solutions serve me. I have a function to verify a user with their secret and their id: https://blahblah.appwrite.gl...