adminandClaude Sonnet 5
ad042d825f
siax.config.json declared deploy.target: "vercel", which conflicts with the SIAX Cloud platform pattern every sibling OS repo (n0d, st0re, aud0) follows: a Dockerfile "for Coolify" (already present in this repo) plus a .gitea/workflows/deploy.yml that POSTs a restart to a Coolify app UUID. Investigated before changing anything: - 0pt.app is confirmed live on Vercel (Server: Vercel, 200 OK) but its own /api/health reports db/queue "not_configured", and POSTing to /api/orders creates an order that is not durably persisted (in-memory store only, per this repo's own docs/08-infrastructure.md and docs/architecture/ ARCHITECTURE.md, both independently verified live 2026-07-19 / 2026-08-07, and reconfirmed live again today). It's a fully-built marketing/demo surface with no real backend behind it -- not a live product serving real customer data. Safe to change deploy config without a cutover plan. - Dockerfile already exists and is already written "for Coolify" (node:24- alpine multistage, non-root, /api/health healthcheck) -- no changes needed there. - No .gitea/workflows/deploy.yml existed. Added one following the exact pattern used by n0d and st0re (POST /api/v1/deploy?uuid=...&force=false with COOLIFY_TOKEN). No Coolify app has been provisioned for 0pt yet, so the app UUID is a literal placeholder and the workflow fails loudly by design until a real app + token are in place -- this does not silently ship a broken deploy config. This changes only this repo's declared *intent*. It does NOT touch the live Vercel deployment, delete the Vercel project, or move any traffic -- that cutover (provision Coolify app -> verify -> DNS -> decommission Vercel) is a separate, larger decision. README and ARCHITECTURE.md updated to state this plainly rather than let them contradict the new config. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
45 lines
2.1 KiB
YAML
45 lines
2.1 KiB
YAML
name: Deploy to Coolify
|
|
|
|
# Follows the fleet-wide pattern used by sax3l/n0d and sax3l/st0re: push to
|
|
# main triggers a POST to Coolify's deploy endpoint for this app's UUID,
|
|
# authenticated with the COOLIFY_TOKEN repo secret. Coolify already has the
|
|
# Dockerfile (build_pack: dockerfile) -- this workflow only fires the
|
|
# rebuild+redeploy, it doesn't build or push an image itself.
|
|
#
|
|
# STATUS (2026-08-09): no Coolify application has been provisioned for 0pt
|
|
# yet -- siax.config.json's `deploy.target` was flipped from "vercel" to
|
|
# "coolify" to state the intended platform, but there is no app UUID to
|
|
# point at. COOLIFY_APP_ID below is a literal placeholder. The guard step
|
|
# fails the job loudly (rather than silently POSTing to a bogus/empty URL)
|
|
# until both the Coolify app exists and its real UUID replaces the
|
|
# placeholder here. See docs/architecture/ARCHITECTURE.md §5/§8 for the
|
|
# open "Vercel or fleet" question this resolves the config side of.
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
workflow_dispatch:
|
|
jobs:
|
|
deploy:
|
|
runs-on: ubuntu-latest
|
|
env:
|
|
COOLIFY_APP_ID: "TODO-no-coolify-app-provisioned-yet"
|
|
steps:
|
|
- name: Guard against unset token / placeholder app id
|
|
run: |
|
|
if [ -z "${{ secrets.COOLIFY_TOKEN }}" ]; then
|
|
echo "::error::COOLIFY_TOKEN secret is not set on this repo -- cannot redeploy."
|
|
exit 1
|
|
fi
|
|
if [ "$COOLIFY_APP_ID" = "TODO-no-coolify-app-provisioned-yet" ]; then
|
|
echo "::error::No Coolify app has been provisioned for 0pt yet. Create the app in the Coolify UI (cloud.siax.io), copy its UUID into COOLIFY_APP_ID in this file, and set the COOLIFY_TOKEN repo secret before this workflow can deploy anything."
|
|
exit 1
|
|
fi
|
|
- name: Trigger Coolify redeploy
|
|
env:
|
|
COOLIFY_TOKEN: ${{ secrets.COOLIFY_TOKEN }}
|
|
run: |
|
|
curl -fsS -X POST \
|
|
"https://cloud.siax.io/api/v1/deploy?uuid=${COOLIFY_APP_ID}&force=false" \
|
|
-H "Authorization: Bearer $COOLIFY_TOKEN" \
|
|
-o /dev/null -w 'coolify deploy HTTP %{http_code}\n'
|