chore(ops): set up stackda.sh for the StackDash rename

Aperta
  • Qualcosa non va?
#435 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, supabase
Ambito
cloud, devops, infrastructure

Direzione di ricerca

This is remote configuration only: DNS, Vercel, Resend, provider consoles and the Supabase dashboard, with no code to touch. Start by reading docs/operations/jobs.md for the Vault and cron renaming in step 7, and read #437 to see exactly which DEVMACRO_* variables become STACKDASH_* before renaming them, since an unrenamed DEVMACRO_ENCRYPTION_KEY breaks stored credentials. Done means each acceptance-criteria box is verified against https://stackda.sh and recorded on the issue. The issue states it is Eddie's to run because every step needs console access, so do not pick this up as a first contribution.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: ops enhancement impact: high priority: P0 size: S

Context

DevMacro is being renamed to StackDash, served at stackda.sh. The code rename is #437, which does not touch anything remote. This issue covers the remote setup that has to exist before the renamed app can run on the new domain. Every step here changes a remote system, so it is Eddie's to run.

Plan

  1. DNS: point stackda.sh at Vercel.
  2. Vercel: add stackda.sh to the project, and set NEXT_PUBLIC_SITE_URL=https://stackda.sh.
  3. Resend: verify stackda.sh as a sending domain (SPF, DKIM, DMARC), then set [email protected].
  4. Rename the DEVMACRO_* environment variables in every environment to STACKDASH_*. The code rename does a clean cutover with no fallback, so an unrenamed DEVMACRO_ENCRYPTION_KEY means stored connection credentials can no longer be decrypted.
  5. Update the callback URLs on every provider app to https://stackda.sh/api/connections/<provider>/callback (GitHub App callback and setup URL, Vercel integration, Sentry, Stripe, Supabase, DigitalOcean, Polar, Resend, GitLab), and the PostHog client metadata URL to https://stackda.sh/oauth/posthog/client-metadata. Rename the app display names and slugs from DevMacro to StackDash where the provider allows it, then update GITHUB_APP_SLUG, VERCEL_INTEGRATION_SLUG, and the Sentry integration slug.
  6. Supabase auth: add https://stackda.sh to the site URL and the redirect allow list, and update the GitHub sign-in OAuth app's callback.
  7. Supabase Vault and cron: re-create the secrets as stackdash_app_url and stackdash_cron_secret, and the job as stackdash-jobs-tick, as described in docs/operations/jobs.md after the code rename. Then unschedule devmacro-jobs-tick.

Acceptance criteria

  • https://stackda.sh serves the app over HTTPS
  • Sign in with GitHub completes on stackda.sh
  • Every provider connection completes its OAuth or install flow on stackda.sh
  • A test email arrives from [email protected] and passes SPF and DKIM
  • The jobs tick runs from stackdash-jobs-tick, and devmacro-jobs-tick no longer exists
  • Playwright e2e: none needed, since this changes remote configuration and no code

Files and areas

Remote only: DNS, Vercel, Resend, provider developer consoles, Supabase dashboard.
Non-goals: code and docs changes (#437), logo assets (#436).

Verification

Run each acceptance check against https://stackda.sh and record the result here.

Model: anthropic/claude-opus-5-5 | Reasoning effort: not reported by the harness

Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
6h 56m
PR unite (30g)
136

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di eddiejaoude/StackDash

Tutte le issue di eddiejaoude/StackDash

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.