メニュー
Build and start the two production Docker containers (API + web app) for The Long Night on this host. Use when asked to bring up, start, boot, rebuild, or restart the production stack.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/cgoulart35/HalloweenEvent --skill prod-upコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Drive the isolated QA sandbox season lifecycle for The Long Night (open / tick / close / restart / status / wipe) and optionally browser-test it, without ever touching real game data or emailing real players. Use for manual end-to-end QA of signup, fights, results emails, and the season rollover.
Run the pytest suite for The Long Night (or a single test / a dependency CVE audit) the correct way — in an ephemeral container on the webapp image. Use when asked to run the tests, check that tests pass, run a specific test, or audit dependencies for CVEs.
Orchestrate a dev change for The Long Night end-to-end — explore, plan, branch, implement (+ tests), /test, optional /qa, commit, push, open a PR, work the review feedback, then pre-deploy checks, merge (only on your explicit OK), and verify the build + prod deploy. Composes the atomic skills and pauses at every human gate. Use for fixes, features, vulnerability fixes, and tooling/dependency upgrades.
SOC 職業分類に基づく
SKILL.md を表示中
| name | prod-up |
| description | Build and start the two production Docker containers (API + web app) for The Long Night on this host. Use when asked to bring up, start, boot, rebuild, or restart the production stack. |
Builds and starts both prod containers with docker-compose-prod.yml:
HalloweenEventApi_prod (service halloween-api-prod, host port 5007 → HTTP) and
HalloweenEventWebApp_prod (service halloween-webapp-prod, host port 5009 → HTTPS, self-signed).
⚠️ This is the live production stack. On the Raspberry Pi (this deploy target) these are the containers real players hit through the Cloudflare tunnel. The API uses the real Firebase node (
halloween-event) and real SMTP, and its lifecycle reconcile loop can send real emails near a season boundary. To exercise the app without touching real data or mailing real people, use/qainstead.Normal deploys happen automatically: CI publishes a new image to GHCR and the in-repo
scripts/deploy-watcher.shpulls it (see Deployment in CLAUDE.md). Run this skill for a deliberate manual (re)start of the stack on this host.
Confirm the secrets are present (the compose file mounts/loads all three; without them the build or boot fails):
ls -1 api.env app.env serviceAccountKey.json
If any is missing, stop and tell the user — on the Pi these live persistently in the repo dir (gitignored); do not fabricate them.
Pull the published images and start (recreates both containers; -d = detached):
docker compose -f docker-compose-prod.yml pull
docker compose -f docker-compose-prod.yml up -d
This runs the current GHCR images (ghcr.io/cgoulart35/halloweenevent-{api,webapp}:latest) —
the same artifacts CI publishes and the watcher auto-deploys. For a full sync to origin/master
(code + images, like the auto-deploy), run sh scripts/deploy.sh. To rebuild locally from source
(dev/debugging only — the watcher replaces it on the next published image), use up -d --build.
Verify both are up:
docker compose -f docker-compose-prod.yml ps
Both services should show state running/Up. Then sanity-check the logs:
docker compose -f docker-compose-prod.yml logs --tail=20 halloween-api-prod
docker compose -f docker-compose-prod.yml logs --tail=20 halloween-webapp-prod
Healthy startup looks like each Flask/werkzeug app reporting it's serving (API on :5004
inside the container → published as 5007; web app on :5004 → 5009 HTTPS). Report any
traceback (common causes: a missing/blank required env var, or a bad FIREBASE_CONFIG_JSON).
docker compose -f docker-compose-prod.yml restart. Use the pull + up -d above to move to a
newer published image.http://localhost:5007, web app https://localhost:5009 (self-signed
cert — browser warning is expected).restart: unless-stopped is set, so the containers come back on reboot/crash on their own./prod-down. To inspect a running stack, use /prod-logs.