Bump Appwrite version to 1.8.1

[stnguyen90]

What does this PR do?

Update installation and upgrade instructions to use the latest Appwrite version

Test Plan

Manual

Related PRs and Issues

None

Have you read the Contributing Guidelines on issues?

Yes

Summary by CodeRabbit

• Chores
  • Updated Docker image versions for self-hosted installations (Appwrite core, realtime, workers, console, assistant, and browser).
  • Added a new _APP_BROWSER_HOST environment variable for self-hosting configuration.
  • Minor formatting tweak in the assistant environment block (no behavioral change).

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This pull request updates Docker image tags and a small environment change across the repo. Appwrite images are bumped from 1.8.0 to 1.8.1 in multiple blog post pages, the self-hosting installation doc, and the Docker Compose file. The Compose file also updates appwrite-console (7.4.7 → 7.5.7), appwrite-assistant (0.8.3 → 0.8.4), and appwrite-browser (0.2.4 → 0.3.2), plus a minor formatting tweak. The environment file adds a new variable _APP_BROWSER_HOST set to http://appwrite-browser:3000/v1.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Bump Appwrite version to 1.8.1' directly and clearly summarizes the main change across all modified files—updating Appwrite and related services from version 1.8.0 to 1.8.1 (with some dependencies updated to newer versions).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat-1.8.1-release

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9ef5d1d and ac1c31c.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (6)

• src/routes/blog/post/building-apps-with-bun-and-appwrite/+page.markdoc
• src/routes/blog/post/email-otp-auth-sveltekit/+page.markdoc
• src/routes/blog/post/planetscale-databases-alternative/+page.markdoc
• src/routes/docs/advanced/self-hosting/installation/+page.markdoc
• static/install/compose
• static/install/env

🚧 Files skipped from review as they are similar to previous changes (3)

• src/routes/docs/advanced/self-hosting/installation/+page.markdoc
• src/routes/blog/post/planetscale-databases-alternative/+page.markdoc
• src/routes/blog/post/email-otp-auth-sveltekit/+page.markdoc

🧰 Additional context used

🧠 Learnings (6)

📓 Common learnings

Learnt from: stnguyen90
Repo: appwrite/website PR: 2520
File: src/routes/docs/advanced/self-hosting/production/updates/+page.markdoc:13-15
Timestamp: 2025-10-24T22:17:14.669Z
Learning: In Appwrite versioning, RC (Release Candidate) versions like `1.6.2-RC1` come before the stable release `1.6.2`. Documentation should recommend upgrading to stable versions, not RC versions.

📚 Learning: 2025-10-24T22:17:14.669Z

Learnt from: stnguyen90
Repo: appwrite/website PR: 2520
File: src/routes/docs/advanced/self-hosting/production/updates/+page.markdoc:13-15
Timestamp: 2025-10-24T22:17:14.669Z
Learning: In Appwrite versioning, RC (Release Candidate) versions like `1.6.2-RC1` come before the stable release `1.6.2`. Documentation should recommend upgrading to stable versions, not RC versions.

Applied to files:

• src/routes/blog/post/building-apps-with-bun-and-appwrite/+page.markdoc

📚 Learning: 2025-09-25T12:18:00.841Z

Learnt from: amustaque97
Repo: appwrite/website PR: 2444
File: .github/workflows/production.yml:107-114
Timestamp: 2025-09-25T12:18:00.841Z
Learning: In the Appwrite website Kubernetes deployment, the team intentionally uses short-lived GITHUB_TOKEN for Docker pull secrets rather than long-lived registry credentials, as per amustaque97's explicit preference.

Applied to files:

• src/routes/blog/post/building-apps-with-bun-and-appwrite/+page.markdoc

📚 Learning: 2025-09-24T08:55:57.959Z

Learnt from: amustaque97
Repo: appwrite/website PR: 2434
File: deploy/templates/deployment.yaml:0-0
Timestamp: 2025-09-24T08:55:57.959Z
Learning: In the Appwrite website Helm deployment, environment variables are managed through ConfigMap rather than direct Helm values injection, so security concerns about secrets in Deployment manifests don't apply to their setup.

Applied to files:

• src/routes/blog/post/building-apps-with-bun-and-appwrite/+page.markdoc
• static/install/compose

📚 Learning: 2025-09-24T09:16:03.075Z

Learnt from: amustaque97
Repo: appwrite/website PR: 2434
File: .github/workflows/staging.yml:117-131
Timestamp: 2025-09-24T09:16:03.075Z
Learning: In the Appwrite website deployment, environment variables are baked into the Docker image during the build stage using build-args, so creating a separate ConfigMap in the Kubernetes deployment job is unnecessary and redundant.

Applied to files:

• src/routes/blog/post/building-apps-with-bun-and-appwrite/+page.markdoc
• static/install/compose

📚 Learning: 2025-09-24T09:00:37.016Z

Learnt from: amustaque97
Repo: appwrite/website PR: 2434
File: .github/workflows/staging.yml:104-111
Timestamp: 2025-09-24T09:00:37.016Z
Learning: The Appwrite website project uses private GHCR images, so imagePullSecret configuration cannot be removed from Kubernetes deployments.

Applied to files:

• static/install/compose

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: tests
• GitHub Check: assets
• GitHub Check: build

🔇 Additional comments (5)

src/routes/blog/post/building-apps-with-bun-and-appwrite/+page.markdoc (1)

78-78: LGTM! Documentation updated to reference the latest version.

The Docker image tag has been correctly updated to 1.8.1, ensuring users following this tutorial will install the latest stable release.

static/install/compose (3)

35-35: LGTM! Core Appwrite services updated to 1.8.1.

All Appwrite core services (main API, realtime, and workers) have been consistently updated from 1.8.0 to 1.8.1. The update is systematic and covers all necessary services.

Also applies to: 195-195, 238-238, 264-264, 292-292, 355-355, 381-381, 449-449, 486-486, 525-525, 559-559, 610-610, 646-646, 685-685, 714-714, 742-742, 770-770, 795-795, 820-820

---

853-853: Minor formatting change.

A blank line was added in the appwrite-assistant environment section. This has no functional impact.

---

175-175: Verify appwrite/browser 0.3.2 compatibility with Appwrite 1.8.1.

Console 7.5.7 and assistant 0.8.4 are confirmed compatible with 1.8.1. However, the official Appwrite 1.8.1 docker-compose uses appwrite/browser:0.2.4. The upgrade to 0.3.2 should be verified for compatibility before deployment.

static/install/env (1)

103-103: LGTM! Browser service host configuration added.

The new _APP_BROWSER_HOST environment variable correctly points to the appwrite-browser service at http://appwrite-browser:3000/v1, which aligns with the browser service update to version 0.3.2 in the Docker Compose file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}