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

未关闭
  • 哪里不对？
#435 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
8/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
github, supabase
领域
cloud, devops, infrastructure

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
TypeScript
星标
1
派生
1
平均合并
6 小时 56 分钟
30 天内合并 PR
136

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

eddiejaoude/StackDash 的其他 Issue

查看 eddiejaoude/StackDash 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。