[Op Readiness: P0] filoz-owned infra deployment

[SgtPooki]

Done Criteria

When this issue is completed, a merge of a PR in this repo will result in:

1. A creation of two GHCR container registry images (backend and frontend)
2. A deployment to staging on our infra at https://github.com/FilOzone/infra
3. Modification of FilOzone/infra is required to deploy to prod

Why Important

Getting Dealbot deployed on infrastructure we own, with a well documented deployment process and automation will allow us to scale, and better support fires and testing of issues without relying on any single developer.

What tasks are needed to complete this

• CI/CD Pipeline (Automation)
  • [Op Readiness: P0]: publish frontend and backend docker images to github container registry #86: Build and publish Docker images to GHCR (This is the "Code Push" trigger).
• Infrastructure Configuration (The "Bridge")
  • [Op Readiness: P0] get filoz hosted domain and decide on permanent home for dealbot #93: Finalize domain name (dealbot.filoz.org) and configure Ingress.
  • Robust wallet management #111: Configure multisig/session keys for production environment variables.
  • USDFC to Mainnet Dealbot Address #72: Fund the mainnet dealbot address with USDFC to ensure operation.
• Observability (Validation of Deployment)
  • [Op Readiness: P0] Export prometheus metrics #87: Export Prometheus metrics for the new environment.
  • [Op Readiness: P0] Create operational dashboards and alerts for dealbot #89: Deploy Grafana dashboards linked to the new Prometheus source.
• Ops Readiness
  • [Op Readiness: P0] Runbook and ops docs #90 and https://github.com/FilOzone/infra/issues/32: Create the Runbook for managing this specific deployment (rollbacks, secret rotation).
  • Set up 7 day database backups #68: Verify/Configure database backup retention (30-day) and recovery procedures.
• Infra
  • https://github.com/FilOzone/infra/issues/7

Notes

This task is specifically for getting the Dealbot to a point where we are deploying on commit to staging on the infra defined at https://github.com/FilOzone/infra.

This task is blocked by #106 but also requires https://github.com/FilOzone/infra/issues/2 to be completed.

[BigLep]

@SgtPooki will update this issue.

[BigLep]

@SgtPooki : I see there are some edits, but maybe there will be more?

Things I'm assuming will be covered here:

• Dependency on filoz-infra setup as covered in Make plan for FilOz-owned/affiliated infra for 2026Q1 tpm-utils#1 ?
• What someone will get at the end of this work? I assume we are getting "a push to main branch automatically causes a deployment to our production environment at domain.tbd"