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
- TOO_MANY_REDIRECTS after temporarily ena...
I am losing my mind over this, I enabled this setting because I was having issues with sites not making links with https. I enabled it, ran into issues, so I di...
- TablesDB `updateRows` returns `database_...
Hi Appwrite team! I’m seeing a strange issue with TablesDB bulk row updates on a self-hosted Appwrite instance. **Environment** - Appwrite self-hosted `1.9.0` ...
- [SOLVED] Realtime Missing Channels
```js useEffect(() => { let subscription: RealtimeSubscription; async function loadChips() { try { const {rows: chi...