patx/projectpay

Document retirement of the Heroku app

Commit 79b4e2a · patx · Nov 3 at 5:57AM

Changeset
79b4e2acc527377702f7192dbf233244c03d4835
Parents
99c3a239e57f33cc0b3f1ebc4757ee1247eab16a

View source at this commit

Comments

No comments yet.

Log in to comment

Diff

diff --git a/README.md b/README.md
index f3a29e1..df6e920 100644
--- a/README.md
+++ b/README.md
@@ -126,8 +126,8 @@ Then copy the `whsec_...` value from the Stripe CLI output into `STRIPE_WEBHOOK_
 
 Production now runs on the existing VPS at https://payment.afterdarklabs.io,
 behind nginx and a private Unix socket. MongoDB Atlas, invoice links, sessions,
-and the existing Stripe webhook remain unchanged. Heroku's web dyno is scaled to
-zero and retained for rollback. See [VPS deployment and rollback](deploy/README.md).
+and the existing Stripe webhook remain unchanged. The retired Heroku app was
+deleted on November 3, 2026. See [VPS deployment and rollback](deploy/README.md).
 
 ## Deployment
 
diff --git a/deploy/README.md b/deploy/README.md
index 9caf638..91d97e6 100644
--- a/deploy/README.md
+++ b/deploy/README.md
@@ -93,7 +93,9 @@ After cutover:
 - Certificate renewal validation passed and automatic renewal was configured.
 - GitMan and Wail remained healthy with protected config hashes and PIDs unchanged.
 - The old Heroku web formation was scaled to zero after public verification.
-  The app/config/custom domain remain for rollback. No Heroku add-ons were present.
+  No Heroku add-ons were present. After the user confirmed the VPS was working,
+  the retired Heroku app, its config, and its Heroku domain attachment were deleted
+  on November 3, 2026. The local Heroku Git remote was removed.
 
 ## Operations and rollback
 
@@ -117,15 +119,16 @@ nginx archive, protected file hashes/PIDs, and `cutover.json` with the previous
 and Heroku formation. `/root/projectpay-releases/preview-verification.json` records
 the read-only preview results.
 
-Rollback while keeping the same shared Atlas data:
+Rollback while keeping the same Atlas data:
 
-1. Run `heroku ps:scale web=1 --app afterdark` from an authenticated workstation.
-2. Verify the Heroku app is healthy before redirecting traffic.
-3. Restore the proxied CNAME for payment.afterdarklabs.io to
-   `globular-baboon-um01s6bh971mrkx0uityd61d.herokudns.com`.
-4. Verify public admin access, customer payment pages, and Stripe webhooks.
-5. Stop the VPS app only after Heroku serves the public domain successfully.
+1. Use a known-good VPS release directory, or stage the known-good source and
+   dependency pins in a new release directory.
+2. Point `/opt/apps/projectpay/current` at that release and restart projectpay.service.
+3. Verify public admin access, customer invoice pages, and webhook validation.
+4. Keep the domain pointing at the VPS. The old Heroku app and CNAME are retired
+   and cannot be used as a rollback destination.
 
-Do not restore an old database snapshot or delete Atlas data during hosting
-rollback. Both hosts use the same live database. The Stripe webhook already
-points at the public hostname, so it follows the DNS change in either direction.
+Do not restore an old database snapshot or delete Atlas data during an application
+rollback. Keep the root-only production environment and existing Stripe webhook
+URL unchanged. The original cutover.json is a historical migration record, not a
+current instruction to restore Heroku DNS.