Rank 1: Thread
Hi Appwrite team, I’m running a self-hosted Appwrite instance.
I have some scheduled/cron Functions that periodically update documents in my Appwrite database.
Currently, inside the Functions I’m using:
APPWRITE_ENDPOINT=https://mydomain.com/v1
The problem is that sometimes my internet/public network connection goes down. During those periods, the Functions themselves are running on the same Appwrite server, but they fail to connect to Appwrite because they are trying to reach my public domain.
Is there a supported way to configure the Functions to communicate with the Appwrite API internally, without going through the public domain/Internet?
For example, could I use something like:
APPWRITE_ENDPOINT=http://appwrite/v1
where appwrite is the internal Docker service/container hostname?
Or is there an official internal hostname/network endpoint that Functions should use for accessing the Appwrite /v1 API?
Ideally, I would like the architecture to be:
Appwrite Function
│
│ internal Docker/network
▼
Appwrite API
│
▼
MariaDB / Redis / other services
instead of:
Appwrite Function
│
│ HTTPS / public DNS
▼
mydomain.com
│
▼
Appwrite server
The goal is to make scheduled Functions continue updating the database even if the server's external Internet connection or public DNS route temporarily becomes unavailable.
Questions:
Is http://appwrite/v1 supported from inside Function containers?
If not, what internal hostname/endpoint should be used?
Do Function runtime containers have access to the same Docker network as the appwrite service?
Is there any recommended configuration for this in self-hosted Appwrite?
Does using an internal endpoint require any special APP* configuration or Docker network configuration?
I'm currently using self-hosted Appwrite, so I'm specifically looking for the recommended internal networking approach rather than routing the Function request through the public domain.