[DEPLOY] Go live + smoke test #7

Open
opened 2026-03-30 16:40:25 +00:00 by Timmy · 3 comments
Owner

Parent: #1

Go/No-Go Checklist

  • DNS propagated
  • SSL valid
  • Chat works on mobile (Android + iOS)
  • 988 banner visible
  • Crisis detection triggers correctly
  • Backend down -> static fallback loads
  • Rate limit works
  • HTTP redirects to HTTPS

After Go-Live

  • Share with small trusted group first
  • Monitor VPS resources 24h
  • Check Hermes logs for errors
## Parent: #1 ## Go/No-Go Checklist - DNS propagated - SSL valid - Chat works on mobile (Android + iOS) - 988 banner visible - Crisis detection triggers correctly - Backend down -> static fallback loads - Rate limit works - HTTP redirects to HTTPS ## After Go-Live - Share with small trusted group first - Monitor VPS resources 24h - Check Hermes logs for errors
Timmy added this to the v0.1 — The Door Opens milestone 2026-03-30 16:40:25 +00:00
Timmy added the deploypriority:critical labels 2026-03-30 16:40:25 +00:00
grok was assigned by bezalel 2026-04-04 18:04:24 +00:00
grok was unassigned by allegro 2026-04-05 09:30:45 +00:00
bezalel was assigned by allegro 2026-04-05 09:30:45 +00:00
bezalel was unassigned by allegro 2026-04-05 11:58:15 +00:00
allegro self-assigned this 2026-04-05 11:58:15 +00:00
Member

🔥 Burn Update — Allegro

Deployment is currently blocked.

Completed

  • Frontend code complete and pushed to main
  • Deploy script and nginx config updated with CORS + rate limiting
  • Backend setup docs added

Blocker

Cannot SSH to VPS 67.205.155.108 from this execution environment (Connection timed out). The deploy script is ready to run, but requires shell access to the target server.

Next step

Either:

  1. Grant this agent SSH key access to 67.205.155.108, or
  2. Run bash deploy.sh manually on the VPS after pulling latest main

Pivoting to next burn target.

## 🔥 Burn Update — Allegro Deployment is currently blocked. ### Completed - Frontend code complete and pushed to main - Deploy script and nginx config updated with CORS + rate limiting - Backend setup docs added ### Blocker Cannot SSH to VPS `67.205.155.108` from this execution environment (Connection timed out). The deploy script is ready to run, but requires shell access to the target server. ### Next step Either: 1. Grant this agent SSH key access to `67.205.155.108`, or 2. Run `bash deploy.sh` manually on the VPS after pulling latest `main` Pivoting to next burn target.
Owner

For the record everyone I deleted the vps that was at 67.205.155.108
we don't have a testbed anymore.
And for go live, assign a final review to me before truly launching.

For the record everyone I deleted the vps that was at 67.205.155.108 we don't have a testbed anymore. And for go live, assign a final review to me before truly launching.
Author
Owner

Triaged during backlog cleanup — priority confirmed. Needs owner assignment.

Triaged during backlog cleanup — priority confirmed. Needs owner assignment.
allegro was unassigned by Timmy 2026-04-05 23:28:08 +00:00
Timmy self-assigned this 2026-04-05 23:28:08 +00:00
Sign in to join this conversation.