📚 Documentation: Provide an update on appwrite-lite status

[gaby]

💭 Description

The standard version of appwrite uses a lot of containers which some users don't even need, are there any plans to continue futher development of appwrite-lite ?

• What are the current road blocks?
• What can the community do to help make appwrite-lite happen?
• What happened to the last docker-image for appwrite-line ?

👀 Have you spent some time to check if this issue has been raised before?

• [X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

[AurelienKun]

Any news on this ?

[eldadfux]

Hey, Appwrite lite was originally designed for us to be able to have an Appwrite version that works on Heroku. Some of the limitations we had is that Heroku free tier supported only a few containers (3 iirc) while Appwrite is using a lot more. Another major limitation we faced in Heroku was that we couldn't get access to the Docker socket which made Functions useless.

What we tried to do is to drastically reduce the number of containers required for Appwrite. We removed InfluxDB and StatsDB and completely disabled stats from the setup. We also introduced a flag to disable Functions. To reduce the number of Appwrite containers, we used supervisord and run all the crucial Appwrite processes under a single Appwrite container.

This direction still seems valid, but we never had enough time capacity in the core team to try and complete the work. We're very happy to accept support, give our advice, and help with ongoing maintenance to any community driven initiative on this project.