Skip to content
Back

Manual install docs are out of sync with 1.9.0 installer output

  • 0
  • Self Hosted
Rudra
10 Apr, 2026, 12:02

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/compose and static/install/env are 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.yml and .env were significantly different from the current docs files
  • differences included:
    • MongoDB service instead of MariaDB
    • different depends_on structure
    • updated image versions
    • additional/different env vars such as _APP_DB_ADAPTER
  • I ran the generated MongoDB-based files locally with docker compose up -d and confirmed the app loaded successfully at http://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.

TL;DR
Manual install docs for Appwrite 1.9.0 are outdated as they are MariaDB based while the installer now supports MongoDB with significant differences. A suggestion is to update the docs to provide separate files for MongoDB and MariaDB or guide developers to generate the files using the installer flow.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more