{{ message }}
Tags: appwrite/appwrite
Tags
Merge pull request #13496 from appwrite/codex/update-base-curl-822 fix: update base image to 2.0.4 for libcurl shutdown cleanup
fix(install): read the upgraded-from version off .env when compose in…
…terpolates it
Compose files before 2.0 write the image as
"${_APP_IMAGE:-appwrite/appwrite}:${_APP_VERSION:-latest}", and the tag is
everything after the first colon -- so the version read back was the rest of
that expression. It parses as no version at all, which counts as newer than
every release, so every infrastructure migration looked already applied and
none ran. A 1.9.x upgrade therefore never carried its build artifacts across,
which is the one thing those migrations exist to do.
A tag that does not start with a digit is now left to .env, which holds the
value the expression resolves to.
Appwrite 2.0.0-rc.1 First release candidate for the self-hosted 2.0.0 release. Release-blocking fixes found while testing the upgrade path from 1.9.6: - Postgres data is now persisted. The volume was mounted beside PGDATA rather than at it, so Docker satisfied the image's declared VOLUME with a throwaway anonymous volume. Data survived a restart but was destroyed by any container recreate, and Postgres is the 2.0 default. - APP_CACHE_BUSTER no longer collides with 1.9.6, which shipped the same value, so an upgraded installation kept serving responses cached under 1.9.6 keys. - V25 now migrates projects.onboarding and schedules.projectInternalId. Boot-time sync only creates missing collections, so neither attribute reached an upgraded installation. - DocumentsDB and VectorsDB connections are configurable, and the installer deploys only the engines the enabled products need. - utopia-php/platform is pinned to the released 1.0.0-rc18 instead of a mutable branch reference. - upgrade --database now warns instead of silently ignoring the flag. - The database batch limit is configurable through _APP_LIMIT_DATABASE_BATCH.
PreviousNext