New PR of Appwrite Template (v1.9.0 - MariaDB variant)
This PR updates the Appwrite template to version 1.9.0 and clarifies the database backend used.
Appwrite now supports multiple database backends (MariaDB and MongoDB).
This template continues to use MariaDB, which was already the default in previous versions.
The change ensures compatibility with the latest Appwrite release and removes any ambiguity about the selected variant.
I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
I have added tests that demonstrate that my correction works or that my new feature works.
Issues related (if applicable)
N/A
Screenshots or Videos
Successfully deployed Appwrite v1.9.0 using Dokploy
Verified services are running correctly
Application accessible via configured domain
Greptile Summary
This PR updates the Appwrite blueprint from v1.8.0 to v1.9.0 (MariaDB variant), bumping all service images, adding the _APP_DB_ADAPTER env var across every worker, adding _APP_GRAPHQL_INTROSPECTION, removing the deprecated appwrite-assistant service, and updating companion images (console, browser, Redis).
The docker-compose.yml and template.toml changes look correct and consistent. However, two issues were found in meta.json:
Version not updated: The Appwrite entry still shows "version": "1.8.0" instead of "1.9.0", violating the project rule that the meta.json version must match the Docker image tag.
Unrelated Strapi removal: The Strapi template entry was deleted from meta.json with no explanation. This appears unrelated to the Appwrite update and may be an accidental change that would remove Strapi from the template registry.
Confidence Score: 2/5
Not safe to merge as-is — the meta.json version is stale and an unrelated template (Strapi) would be silently removed from the registry.
The docker-compose.yml and template.toml changes are well-structured and complete. The score is lowered because of two meta.json problems: a required version field mismatch (1.8.0 vs 1.9.0) that violates an explicit project convention, and an unexplained deletion of the Strapi template entry that has no relation to this PR's stated goal.
meta.json — version field needs updating to 1.9.0, and the Strapi deletion needs to be reverted or explicitly justified.
The version field in meta.json still shows 1.8.0, but the docker-compose.yml image tags have been updated to 1.9.0. Per the project's AGENTS.md, the version in meta.jsonMUST match the Docker image version in docker-compose.yml.
This PR removes the Strapi template entry from meta.json, which has no connection to the Appwrite version bump. Could you clarify whether this removal is intentional? If it was accidentally included (e.g. from a merge conflict or local edit), it should be reverted so Strapi continues to appear in the template registry.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/767
**Author:** [@nxtgencat](https://github.com/nxtgencat)
**Created:** 4/3/2026
**Status:** 🔄 Open
**Base:** `canary` ← **Head:** `nxt`
---
### 📝 Commits (1)
- [`bc6fd6a`](https://github.com/Dokploy/templates/commit/bc6fd6a57b8d5b18093bb6247730ed20c9860361) feat: update Appwrite to v1.9.0 with MariaDB and MongoDB variants
### 📊 Changes
**7 files changed** (+1169 additions, -51 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/appwrite-mariadb/appwrite.svg` (+0 -0)
📝 `blueprints/appwrite-mariadb/docker-compose.yml` (+43 -30)
📝 `blueprints/appwrite-mariadb/template.toml` (+5 -0)
➕ `blueprints/appwrite-mongodb/appwrite.svg` (+9 -0)
➕ `blueprints/appwrite-mongodb/docker-compose.yml` (+902 -0)
➕ `blueprints/appwrite-mongodb/template.toml` (+188 -0)
📝 `meta.json` (+22 -21)
</details>
### 📄 Description
## What is this PR about?
New PR of **Appwrite Template (v1.9.0 - MariaDB variant)**
This PR updates the Appwrite template to version **1.9.0** and clarifies the database backend used.
Appwrite now supports multiple database backends (MariaDB and MongoDB).
This template continues to use **MariaDB**, which was already the default in previous versions.
The change ensures compatibility with the latest Appwrite release and removes any ambiguity about the selected variant.
---
## Checklist
Before submitting this PR, please make sure that:
- [x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
- [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
- [ ] I have added tests that demonstrate that my correction works or that my new feature works.
---
## Issues related (if applicable)
N/A
---
## Screenshots or Videos
- Successfully deployed Appwrite v1.9.0 using Dokploy
- Verified services are running correctly
- Application accessible via configured domain
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR updates the Appwrite blueprint from v1.8.0 to v1.9.0 (MariaDB variant), bumping all service images, adding the `_APP_DB_ADAPTER` env var across every worker, adding `_APP_GRAPHQL_INTROSPECTION`, removing the deprecated `appwrite-assistant` service, and updating companion images (console, browser, Redis).
The `docker-compose.yml` and `template.toml` changes look correct and consistent. However, two issues were found in `meta.json`:
- **Version not updated:** The Appwrite entry still shows `"version": "1.8.0"` instead of `"1.9.0"`, violating the project rule that the `meta.json` version must match the Docker image tag.
- **Unrelated Strapi removal:** The Strapi template entry was deleted from `meta.json` with no explanation. This appears unrelated to the Appwrite update and may be an accidental change that would remove Strapi from the template registry.
<h3>Confidence Score: 2/5</h3>
Not safe to merge as-is — the meta.json version is stale and an unrelated template (Strapi) would be silently removed from the registry.
The docker-compose.yml and template.toml changes are well-structured and complete. The score is lowered because of two meta.json problems: a required version field mismatch (1.8.0 vs 1.9.0) that violates an explicit project convention, and an unexplained deletion of the Strapi template entry that has no relation to this PR's stated goal.
meta.json — version field needs updating to 1.9.0, and the Strapi deletion needs to be reverted or explicitly justified.
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (2)</h3></summary>
1. `meta.json`, line 368 ([link](https://github.com/dokploy/templates/blob/b43209996b2067a3c8a362ab6c213155e3a53794/meta.json#L368))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Version mismatch with docker-compose.yml**
The `version` field in `meta.json` still shows `1.8.0`, but the `docker-compose.yml` image tags have been updated to `1.9.0`. Per the project's `AGENTS.md`, the version in `meta.json` **MUST** match the Docker image version in `docker-compose.yml`.
**Context Used:** AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
2. `meta.json`, line 5952-5970 ([link](https://github.com/dokploy/templates/blob/b43209996b2067a3c8a362ab6c213155e3a53794/meta.json#L5952-L5970))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Unrelated Strapi entry removal**
This PR removes the Strapi template entry from `meta.json`, which has no connection to the Appwrite version bump. Could you clarify whether this removal is intentional? If it was accidentally included (e.g. from a merge conflict or local edit), it should be reverted so Strapi continues to appear in the template registry.
</details>
<!-- /greptile_failed_comments -->
<sub>Reviews (1): Last reviewed commit: ["feat: update Appwrite to v1.9.0 with Mar..."](https://github.com/dokploy/templates/commit/b43209996b2067a3c8a362ab6c213155e3a53794) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=27309917)</sub>
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
**Context used:**
- Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
<!-- /greptile_comment -->
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/767
Author: @nxtgencat
Created: 4/3/2026
Status: 🔄 Open
Base:
canary← Head:nxt📝 Commits (1)
bc6fd6afeat: update Appwrite to v1.9.0 with MariaDB and MongoDB variants📊 Changes
7 files changed (+1169 additions, -51 deletions)
View changed files
📝
blueprints/appwrite-mariadb/appwrite.svg(+0 -0)📝
blueprints/appwrite-mariadb/docker-compose.yml(+43 -30)📝
blueprints/appwrite-mariadb/template.toml(+5 -0)➕
blueprints/appwrite-mongodb/appwrite.svg(+9 -0)➕
blueprints/appwrite-mongodb/docker-compose.yml(+902 -0)➕
blueprints/appwrite-mongodb/template.toml(+188 -0)📝
meta.json(+22 -21)📄 Description
What is this PR about?
New PR of Appwrite Template (v1.9.0 - MariaDB variant)
This PR updates the Appwrite template to version 1.9.0 and clarifies the database backend used.
Appwrite now supports multiple database backends (MariaDB and MongoDB).
This template continues to use MariaDB, which was already the default in previous versions.
The change ensures compatibility with the latest Appwrite release and removes any ambiguity about the selected variant.
Checklist
Before submitting this PR, please make sure that:
Issues related (if applicable)
N/A
Screenshots or Videos
Greptile Summary
This PR updates the Appwrite blueprint from v1.8.0 to v1.9.0 (MariaDB variant), bumping all service images, adding the
_APP_DB_ADAPTERenv var across every worker, adding_APP_GRAPHQL_INTROSPECTION, removing the deprecatedappwrite-assistantservice, and updating companion images (console, browser, Redis).The
docker-compose.ymlandtemplate.tomlchanges look correct and consistent. However, two issues were found inmeta.json:"version": "1.8.0"instead of"1.9.0", violating the project rule that themeta.jsonversion must match the Docker image tag.meta.jsonwith no explanation. This appears unrelated to the Appwrite update and may be an accidental change that would remove Strapi from the template registry.Confidence Score: 2/5
Not safe to merge as-is — the meta.json version is stale and an unrelated template (Strapi) would be silently removed from the registry.
The docker-compose.yml and template.toml changes are well-structured and complete. The score is lowered because of two meta.json problems: a required version field mismatch (1.8.0 vs 1.9.0) that violates an explicit project convention, and an unexplained deletion of the Strapi template entry that has no relation to this PR's stated goal.
meta.json — version field needs updating to 1.9.0, and the Strapi deletion needs to be reverted or explicitly justified.
Comments Outside Diff (2)
meta.json, line 368 (link)The
versionfield inmeta.jsonstill shows1.8.0, but thedocker-compose.ymlimage tags have been updated to1.9.0. Per the project'sAGENTS.md, the version inmeta.jsonMUST match the Docker image version indocker-compose.yml.Context Used: AGENTS.md (source)
meta.json, line 5952-5970 (link)This PR removes the Strapi template entry from
meta.json, which has no connection to the Appwrite version bump. Could you clarify whether this removal is intentional? If it was accidentally included (e.g. from a merge conflict or local edit), it should be reverted so Strapi continues to appear in the template registry.Reviews (1): Last reviewed commit: "feat: update Appwrite to v1.9.0 with Mar..." | Re-trigger Greptile
(2/5) Greptile learns from your feedback when you react with thumbs up/down!
Context used:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.