Repository navigation
Appwrite 2.5.0, with Functions and Sites on by default. Upgrading from 1.0.0:
see docs/upgrading.md.
Changed
- Functions and Sites are on by default:
compute.enabledand
compute.executor.privilegeddefault totrue, so a plain install runs
the executor as a privileged pod in a namespace of its own. Set
compute.enabled: falseon clusters that forbid privileged pods. - Files are stored in object storage by default:
storage.devicedefaults
tos3, served by the built-in SeaweedFS. To keep 1.0.0's behaviour, set
storage.device: localandcompute.enabled: false. - Appwrite 2.5.0, with console 1.2.74, executor 1.1.2, browser 0.3.6 and
geo 0.3.2, and the new trusted-proxy, internal-address and DNS settings in
the environment defaults (networking.md). - External S3 settings move to
storage.s3.external.endpointand
storage.s3.external.region, withstorage.s3.mode: external. Setting
the old keys fails with where they went. - ClickHouse drops its per-second metric, trace and text logs and gives
tables left behind by a config change a TTL, as Appwrite 2.4.0 does. - CI upgrades from the published chart 1.0.0 with default values.
Added
- Built-in object storage: SeaweedFS as a single-replica StatefulSet
(storage.s3.mode: builtin), with generated keys, the bucket created on
start, and a NetworkPolicy that admits only Appwrite, the orchestrator,
builds and the executor (storage.md). - Troubleshooting for deployments that fail with an internal error while
Functions and Sites are off.
Removed
- The assistant: Appwrite removed it in 2.4.0. Setting
assistant.*fails
with that message.
Fixed
- Site screenshots: the browser gets the API Service in
ALLOWED_HOSTS, as
browser 0.3.5 and later require for private addresses. make env-defaultsworks with Appwrite 2.4.0 and later, and no longer
leaves an error message infiles/env-defaults.yamlwhen it fails.
Install
helm install appwrite oci://ghcr.io/appwrite/charts/appwrite --version 2.0.0Digest: sha256:b4e331f537dfaaf007ce9dcd9cca888c122fce97934b8f5c0ce0d6ac8b6dfba7