feat: browser on by default

[levivannoort]

What

Sites are on by default since 2.0.0, and Appwrite takes a screenshot of every site deployment through the browser service, which was off by default (browser.enabled: false). On a default install every site deployment therefore ends with:

[appwrite] Screenshot capturing started.
[appwrite] Screenshot capturing failed. Deployment will continue.

and the console shows "No preview". The screenshots worker logs Could not resolve host: appwrite-browser (Domain name not found). Found on a fresh 2.0.0 install on kind, deploying the TanStack Start starter. Appwrite's Docker install runs the browser by default too.

• browser.enabled defaults to true. It requests 100m CPU and 512Mi, with a 2Gi limit.
• docs/optional-components.md: Geo and the browser are on by default, and the browser section shows how to turn it off and what happens without it.
• docs/troubleshooting.md: Site deployments log "Screenshot capturing failed" covers the browser being off, or its egress policy.
• Unit test: the browser deploys by default; the other optional components still don't.
• CHANGELOG.md [Unreleased]: Changed and Added. A new default, not a breaking change, so this is for 2.1.0 (release in a separate PR, based on main after this merges).

Testing

• make test passes: 247/247 unit tests, lint, kubeconform, examples, generated files.
• Every CI install scenario now runs the browser, and hack/smoke.sh takes a screenshot through it when its Service exists.
• Not yet checked by hand: a site redeployed on the local 2.0.0 install with the browser on.

[hansi-codes]

🟢 Tier S · Ready to merge

The revised selector matches worker pods in all documented modes, including separate and grouped deployments, so the earlier log-command issue is resolved and no new defect is apparent.

Enables the browser by default so Site deployments can capture previews, and adds a default-deployment test, changelog entry, and updated generated chart documentation. The optional-components guide explains the browser default and how to disable it, while troubleshooting guidance covers screenshot failures and locating their worker logs across worker modes.

Latest changes: The latest commit changes the screenshot troubleshooting command to find worker logs by label across combined, separate, and grouped modes, and clarifies which worker emits the cause.

Verdict	New comments	Fixed	Still open
✅ Approved	0	1	0

📂 Walkthrough · 7

File	Change
CHANGELOG.md	Records the browser default change and screenshot troubleshooting addition.
charts/appwrite/README.md	Regenerates the chart reference documentation for the browser default.
charts/appwrite/tests/optional_test.yaml	Tests that the browser deploys by default while other optional components remain disabled.
charts/appwrite/values.schema.json	Regenerates the schema description for the browser setting.
charts/appwrite/values.yaml	Enables the browser by default and documents its resource settings and purpose.
docs/optional-components.md	Documents the browser's default-on behavior and how to disable it.
docs/troubleshooting.md	Adds screenshot failure guidance and a worker-label log command that works across worker modes.

✅ Fixed since the last review · 1

• Log command only works with combined workers · docs/troubleshooting.md:330

---

_{Reviewed the commits since 46589f9 · Details · Comment @hansi-codes review to re-run, or mention @hansi-codes with a question.}

[hansi-codes]

🔵 Tier A · Looks good to merge. Summary

[hansi-codes]

🟢 Tier S · Looks good to merge. Summary