Hey there 👋 Appwrite was built with scale in mind. You can run docker service ps to see what containers are there in Appwrite.
Depending on your use case, you can disable some of those in docker-compose.yml, such as certificate worker, usage worker or database worker.
With that said, REST logic of all services are inside appwrite container and cannot be disabled separately. Thankfully, you can visit your project settings and disable them from there:
Cool ! Would be really nice to have modularized Appwirte to be able to use only Storage or only Functions and etc. Thanks for an answer 🙂
Hey @squallsama is your issue solved, can I marked this as resolved?
I think yes. It would be nice to have the ability to start just some kind of small modules (only database or only functions) in the future, but for now I can modify settings and remove some containers from docker-compose.yml
You could create GitHub issue with this feature request, so we can better track the interest 🙏
[SOLVED] Deploy only Functions Executor
Recommended threads
- Whats wrong here
I keep trying to fucking add the appwrite domains including CNAME and CAA but it keeps failing , this is the exact records i have right now in cf
- Broken Appwrite can’t make functions nor...
Hii guys, I was having this issue with my locally hosted Appwrite, I can’t create functions ( both template and manual), I can’t make a custom domain ( like in ...
- Tips for Debugging Appwrite Functions Lo...
Hi everyone! 👋 I have an Appwrite Function running locally with Docker, but I’m struggling to debug it because execution doesn’t reach the breakpoints I set. ...