I looked into the manual install docs issue for Appwrite 1.9.0 and wanted to share the findings, since this seems to need a bigger docs decision.
What I found:
- the current manual install files in
static/install/composeandstatic/install/envare MariaDB-based - Appwrite 1.9.0 installer output is not just a version bump; it changes structurally depending on the selected database engine
- I tested the installer with MongoDB selected and the generated
docker-compose.ymland.envwere significantly different from the current docs files - differences included:
- MongoDB service instead of MariaDB
- different
depends_onstructure - updated image versions
- additional/different env vars such as
_APP_DB_ADAPTER
- I ran the generated MongoDB-based files locally with
docker compose up -dand confirmed the app loaded successfully athttp://localhost - I also captured screenshots/recordings of the generated files and successful local run
Based on this, it seems the docs may need to support both MongoDB and MariaDB, rather than relying on a single static compose/env pair.
Wanted to ask the team:
- should the manual install docs provide separate files for MongoDB and MariaDB?
- or should the docs move toward telling users to generate the files through the installer flow instead?
Happy to share the screenshots/findings if useful.
Recommended threads
- Running into a server error on my self-h...
Hey everyone, I'm running into a server error on my self-hosted setup after updating to v1.19.0. The issue only happens during user creation and deletion. Ever...
- Storage System
Hey guys, quick question regarding massive storage scaling. I’m working in digital forensics and I’m constantly dealing with huge binary disk images, usually be...
- _APP_OPTIONS_ROUTER_PROTECTION
Hi Everyone, I just setup a fresh 1.9.0 on a server. Configured everything and now when i try to connect to appwrite for first time setup i get a _APP_OPTIONS_R...