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
- Does 1.9.0 Self Hosted have MongoDB Atla...
I have been playing with the new 1.9.0 update and I am really excited for the MongoDB support. I wanted to ask though if at the current time Appwrite supports b...
- significant increase in CPU usage with 1...
Hi, This is no big deal at all (as everything is working great so far), but I just saw that the update (from 1.8 to 1.9) consumes much more CPU than before (re...
- Issues with executor in Appwrite 1.9.0
Hi, I’ve recently did a fresh install of appwrite 1.9.0 self hosted and when I run a function, it just waits indefinite This is the error from the log: [Er...