Skip to content

docs(install): point self-hosters at the self-host image #618

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
therealbrad merged 1 commit into from
Sep 8, 2026
Merged

docs(install): point self-hosters at the self-host image #618

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/blog/2026-09-08-v1.0-release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,9 +108,11 @@ pnpm build
For Docker deployments:

```bash
docker pull ghcr.io/testplanit/testplanit:latest
docker pull ghcr.io/testplanit/testplanit-selfhost:latest
```

Self-hosted deployments use the `testplanit-selfhost` image — domain-agnostic, so one image serves any hostname, and published for both `linux/amd64` and `linux/arm64`.

If you've been on the beta channel, v1.0.0 is the graduation of that line — upgrade as usual.

## What's Next
Expand Down
14 changes: 12 additions & 2 deletions docs/docs/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,10 +22,20 @@ TestPlanIt applies database schema changes with versioned migrations (`zenstack
A routine upgrade with Docker:

```bash
docker pull ghcr.io/testplanit/testplanit:latest
docker pull ghcr.io/testplanit/testplanit-selfhost:latest
docker compose up -d # pending migrations apply on startup
```

:::note Which image to pull

Self-hosted deployments use **`testplanit-selfhost`**. It is domain-agnostic, so
one image serves any hostname, and it is published for both `linux/amd64` and
`linux/arm64`. The `testplanit` image is built for the hosted service, bakes its
domain in at build time, and is `arm64` only — pulling it on an x86 host fails
with `no matching manifest for linux/amd64`.

:::

A routine upgrade from source:

```bash
Expand All @@ -51,7 +61,7 @@ npx zenstack migrate resolve --applied 20260625193632_init --schema schema.zmode
# `docker compose run --rm --no-deps --entrypoint "" prod` for `docker run --rm --entrypoint ""`):
docker run --rm --entrypoint "" \
-e DATABASE_URL="postgresql://user:password@host:5432/testplanit" \
ghcr.io/testplanit/testplanit:latest \
ghcr.io/testplanit/testplanit-selfhost:latest \
npx zenstack migrate resolve --applied 20260625193632_init --schema schema.zmodel
```

Expand Down
Loading