rmancinasandClaude Opus 5
4ee7ec71f0
Closes the gap between "what tag did I deploy" and "what is actually running", and gives the schema a history that can be reasoned about across releases. Migrations - Baseline the existing schema as 0000_init (migrate diff --from-empty). The schema had only ever been applied with `prisma db push`, so no history existed and schema state was disconnected from app version. Existing databases must be baselined once with `migrate resolve --applied 0000_init`; the workflows print this remedy on P3005. - Run `prisma migrate deploy` as a deploy STEP, not the container CMD — as a CMD, N replicas would race each other applying the same migration. Version reporting - GET /version on the API reports the APP_VERSION / GIT_SHA / BUILD_DATE that build.yml already baked into both images but nothing ever read. - The web footer shows the web build and flags an api/web mismatch. The two cannot drift at build time (one matrix run) but can at deploy time. - Both deploy workflows now fail if the running API does not report the tag that was dispatched — a stack naming a tag is not proof of what is running. - scripts/set-version.mjs stamps every package.json, which had all sat at 0.1.0 while real releases shipped as v1.x. Pre-migrate backup - deploy/scripts/pre-migrate-backup.mjs dumps the database from INSIDE the still-running old API container over Portainer's Docker API, so the file lands in the volume the Operaciones restore screen reads. A dump taken on the CI runner would be unreachable by the only restore path we have. Verifies the artefact with `gzip -t` before letting the migration proceed. galactus - deploy/galactus/*.compose.yml: standalone-Docker ports of the Swarm stacks. Plain compose silently ignores `deploy:`, so restart_policy becomes `restart: unless-stopped` — without it nothing returns after a host reboot. - .gitea/workflows/deploy-galactus.yml drives endpoint 3 with its own secrets. Fixes - deploy.yml passed `endpoint_id` and `pull_image` to cssnr/portainer-stack-deploy-action, which has no such inputs (they are `endpoint` and `pull`). The endpoint was silently never set. docs/DEPLOY_AND_MIGRATIONS.md documents expand/contract as the rule for schema changes: Prisma has no down-migrations, so a code rollback never rolls the schema back, and restoring the replication master from a dump diverges every replica. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
31 lines
986 B
TypeScript
31 lines
986 B
TypeScript
import { Controller, Get } from "@nestjs/common";
|
|
|
|
@Controller()
|
|
export class AppController {
|
|
@Get("health")
|
|
health() {
|
|
return { status: "ok" };
|
|
}
|
|
|
|
/**
|
|
* What is actually running. The three values are baked into the image at
|
|
* build time by .gitea/workflows/build.yml (see docker/api.Dockerfile) and
|
|
* are the only way to confirm a deploy — or a rollback — landed: the tag you
|
|
* dispatched and the code inside the container can disagree if a stack was
|
|
* applied without pulling, or if the app stack still names an older tag.
|
|
*
|
|
* Deliberately unauthenticated, same as /health: the deploy workflow has to
|
|
* read it with no session, and it exposes nothing an attacker could not
|
|
* already infer from the repo.
|
|
*/
|
|
@Get("version")
|
|
version() {
|
|
return {
|
|
service: "api",
|
|
version: process.env.APP_VERSION ?? "dev",
|
|
gitSha: process.env.GIT_SHA ?? "unknown",
|
|
buildDate: process.env.BUILD_DATE ?? "unknown",
|
|
};
|
|
}
|
|
}
|