docs: warn that v4 removes the bundled postgres and document the migration - #1121
Merged
Conversation
✅ Deploy Preview for tolgee-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dkrizan
force-pushed
the
dkrizan/slim-ee-image
branch
2 times, most recently
from
June 23, 2026 09:54
1d35a59 to
a28eeb1
Compare
dkrizan
force-pushed
the
dkrizan/slim-ee-image
branch
2 times, most recently
from
July 16, 2026 13:45
ed5bbe2 to
8854090
Compare
dkrizan
changed the title
dkrizan
marked this pull request as ready for review
July 16, 2026 14:29
dkrizan
force-pushed
the
dkrizan/slim-ee-image
branch
4 times, most recently
from
July 16, 2026 14:51
4faf2c2 to
5b64a9a
Compare
dkrizan
changed the title
dkrizan
force-pushed
the
dkrizan/slim-ee-image
branch
from
July 17, 2026 10:03
5b64a9a to
958696d
Compare
The EE image is becoming slim and bundles no postgres server, so the job needs a database of its own. Postgres 13 went end of life in November 2025.
dkrizan
force-pushed
the
dkrizan/slim-ee-image
branch
2 times, most recently
from
July 17, 2026 11:28
e9d063d to
58f7476
Compare
JanCizmar
approved these changes
Jul 21, 2026
…ation The bundled server is PostgreSQL 13, end of life since November 2025, so the migration leads with a dump into PostgreSQL 17 and keeps reusing the existing files on 13 as the quicker alternative. The external database example sets up an empty database, which is the wrong thing to copy for a migration: a newer PostgreSQL refuses to start on the files the bundled server leaves behind.
dkrizan
force-pushed
the
dkrizan/slim-ee-image
branch
from
July 28, 2026 14:19
7374ad7 to
8885223
Compare
dkrizan
added a commit
to tolgee/tolgee-platform
that referenced
this pull request
Jul 28, 2026
## What Two changes, both preparing for v4 dropping the bundled postgres from `tolgee/tolgee`: 1. **Deprecation warning** — the app logs a `WARN` on startup when it's actually running the bundled postgres, pointing at the external-database docs. 2. **Internal slim image** — `Dockerfile.slim` + the `dockerSlim` Gradle task. Not published. Built on demand by the EE image build and by the smoke test. ## Why In v4, `tolgee/tolgee` loses the embedded postgres. Self-hosters running the bundled database have to move to an external one before upgrading. They can already do that today on the current image by setting `postgres-autostart.enabled=false` (this is what the external-database docs section has always described). So the warning gives them a full release cycle of notice, on every boot, for a migration that needs nothing new from us. The slim image is deliberately **not** published: a public `:slim` tag would only advertise a name that goes obsolete the moment v4 makes it the default, and it buys users nothing they can't already do. It exists so the internal EE image can drop the postgres layers now. ## Notes for review - No behavior change for existing users beyond the log line. The default `Dockerfile` and the `tolgee/tolgee` tag are untouched. - The warning is guarded on `enabled=true` **and** `mode=EMBEDDED`, so it stays silent for external-database setups and for Java + `DOCKER` autostart (that mode isn't going away). - `docker-slim-smoke` boots the slim image against a postgres service and waits for `/actuator/health`. - Docs: tolgee/documentation#1121 · EE image switch: tolgee/billing#274 - Revives #3193 (stale). Thanks @transparentChange for the original work. --------- Co-authored-by: Matthew Sekirin <matthew.sekirin@gmail.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
TolgeeMachine
added a commit
to tolgee/tolgee-platform
that referenced
this pull request
Jul 30, 2026
# [3.215.0](v3.214.1...v3.215.0) (2026-07-30) ### Features * auto-invalidate caches by value shape instead of wiping on startup ([#3813](#3813)) ([7e1db10](7e1db10)) * Community translation v1.1 — Contributors (pitch [#3806](#3806)) ([#3819](#3819)) ([3232c4f](3232c4f)) * deprecate embedded postgres ahead of v4 ([#3610](#3610)) ([3cef7ad](3cef7ad)), closes [tolgee/documentation#1121](tolgee/documentation#1121) [tolgee/billing#274](tolgee/billing#274) [#3193](#3193)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two changes:
platform/self_hosting/running_with_docker.mdx— warns that Tolgee v4 removes the bundled PostgreSQL from thetolgee/tolgeeimage, and adds a Migrate from the bundled database section with the actual procedure..github/workflows/update-generated-code.yaml— the docs codegen job bootedghcr.io/tolgee/tolgee-eestandalone and relied on its embedded postgres. The EE image is becoming slim (no bundled DB), so the job now starts apostgresservice and points the app at it.Why
In v4 the bundled postgres goes away, so anyone running it has to move to an external database first. The good news is that this needs no dump and restore: the bundled server keeps its files in
data/postgreson the volume users already mount, which is exactly where a separate postgres container looks for them. Pin the container topostgres:13and it adopts the directory in place.This also fixes a live trap. The existing external-database example runs
postgres:15and mounts./data/postgres:/var/lib/postgresql/data— the same directory a bundled user already has. Copy-pasting it as a migration fails hard:That example is fine for fresh installs and now says it's for fresh installs.
Verified end-to-end
Against the real
tolgee/tolgee:v3.212.0image, not by reasoning:PG_VERSIONis13atdata/postgres, created a marker translation key via the API.postgres:15on that directory → exits(1), incompatible-files error above.postgres:13on that directory → starts, all 103 tables intact.postgres-autostart.enabled=falseagainst the externalpostgres:13→ boots, starts no embedded server, original admin password still works, marker key still present.Notes for review