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

Abierto
  • ¿Algo no está bien?
#435 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, supabase
Área
cloud, devops, infrastructure

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
1
Forks
1
Merge medio
6 h 56 min
PR fusionados (30 d)
136

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eddiejaoude/StackDash

Todos los issues de eddiejaoude/StackDash

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.