Deploy pipeline (mirror the aac pipeline logic) #33

New issue

Closed

opened 2026-07-17 16:42:27 +02:00 by marco · 0 comments

marco commented

2026-07-17 16:42:27 +02:00

Owner

Set up a deploy pipeline for IsoMmo (Auth + GameServer as separately-deployable processes, plus the client build), mirroring the exact logic of the existing aac pipeline — same structure/stages/conventions, adapted to this repo.

Complements #11 (which lists "cross-platform deploy scripts + per-environment config" as a bullet); this is the concrete CI/CD pipeline.

Blocked on input

Point me at the aac pipeline (repo + the workflow/CI file, or a copy) so it can be replicated 1:1 in logic. Until then this is a placeholder.

Scope (to refine once aac is available)

Build + publish Auth and GameServer (self-contained, multi-platform: Win/macOS/Linux for the server).
Same trigger/stage/artifact/secret conventions as aac.
Per-environment config (staging/prod) — the JWT key/issuer/audience and DB connection strings come from environment/secrets, never committed.
Client build artifact (Win/macOS).

Definition of Done

The pipeline mirrors aac's logic (stages/triggers/artifacts), reviewed side-by-side.
A push/tag produces deployable Auth + GameServer artifacts for the target environment.
Secrets (JWT key, DB creds) are injected, not in the repo.
Runs green end-to-end at least once.

Set up a **deploy pipeline** for IsoMmo (Auth + GameServer as separately-deployable processes, plus the client build), **mirroring the exact logic of the existing `aac` pipeline** — same structure/stages/conventions, adapted to this repo. Complements #11 (which lists "cross-platform deploy scripts + per-environment config" as a bullet); this is the concrete CI/CD pipeline. ## Blocked on input - **Point me at the `aac` pipeline** (repo + the workflow/CI file, or a copy) so it can be replicated 1:1 in logic. Until then this is a placeholder. ## Scope (to refine once aac is available) - Build + publish Auth and GameServer (self-contained, multi-platform: Win/macOS/Linux for the server). - Same trigger/stage/artifact/secret conventions as `aac`. - Per-environment config (staging/prod) — the JWT key/issuer/audience and DB connection strings come from environment/secrets, never committed. - Client build artifact (Win/macOS). ## Definition of Done - The pipeline mirrors `aac`'s logic (stages/triggers/artifacts), reviewed side-by-side. - A push/tag produces deployable Auth + GameServer artifacts for the target environment. - Secrets (JWT key, DB creds) are injected, not in the repo. - Runs green end-to-end at least once.

marco referenced this issue

2026-07-19 13:50:32 +02:00

feat(protocol): version the wire contract, reject mismatched clients #97

marco referenced this issue from a commit

2026-07-19 14:00:15 +02:00

chore(deploy): containerize Auth + GameServer, add Forgejo release pipeline (#33)

marco referenced this issue from a pull request that will close it,

2026-07-19 14:05:31 +02:00

chore(deploy): containerize services + Forgejo release pipeline (#33) #98

marco referenced this issue from a commit

2026-07-19 20:25:35 +02:00

feat(protocol): version the wire contract, reject mismatched clients (#97)