Skip to content

deploy docs: post-release docker pull verification #17

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
klagrida merged 1 commit into from
Jun 8, 2026
Merged

deploy docs: post-release docker pull verification #17

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
17 changes: 14 additions & 3 deletions deploy/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,17 +12,28 @@ Registry via [`.github/workflows/release.yml`](../.github/workflows/release.yml)
| `ghcr.io/gridatek/agentforge-api` | FastAPI gateway + agent graph (runs as non-root, port 8000) |
| `ghcr.io/gridatek/agentforge-console` | Angular console built and served by nginx (port 80) |

Each image is tagged with the full version (`0.1.0`), the minor line (`0.1`), the
Each image is tagged with the full version (`0.2.0`), the minor line (`0.2`), the
commit SHA, and `latest`. Cut a release with:

```bash
git tag v0.1.0
git push origin v0.1.0
git tag v0.2.0
git push origin v0.2.0
```

(Or trigger **Release** manually from the Actions tab.) Every PR also *builds*
both images (no push) so a broken Dockerfile fails CI before merge.

After the release run finishes, verify the images are pullable:

```bash
docker pull ghcr.io/gridatek/agentforge-api:0.2.0
docker pull ghcr.io/gridatek/agentforge-console:0.2.0
```

GHCR packages are **private by default** — if the pull asks for auth, make each
package Public (org → Packages → the package → *Package settings* → Change
visibility), or `docker login ghcr.io` first.

## Running the published images

You still need a Postgres+pgvector instance and an embedding/chat provider.
Expand Down
Loading