Skip to content

docs: add Zeabur deployment readiness - #1

Draft
yihui-dev wants to merge 6 commits into
mainfrom
agent/zeabur-selfhost-setup
Draft

docs: add Zeabur deployment readiness#1
yihui-dev wants to merge 6 commits into
mainfrom
agent/zeabur-selfhost-setup

Conversation

@yihui-dev

Copy link
Copy Markdown

What changed

  • Added the 17old Zeabur readiness note for the OpenAnalytics fork.
  • Recorded the version baseline, server purchase floor, DNS prerequisites, and the fact that Zeabur does not directly deploy Docker Compose.

Why

The project requires a multi-service deployment. This avoids treating it as a single Node service before the final Zeabur topology and domain are chosen.

Validation

  • pnpm run verify
  • pnpm exec tsc -p tests/tsconfig.json
  • pnpm run tracker:build
  • pnpm run test (2,991 tests)

Deployment impact

No runtime services, DNS records, domains, or secrets were created. The PR is intentionally draft until the server and deployment path are chosen.

@github-actions

Copy link
Copy Markdown

Thanks for the pull request. Before it can be merged we need you to sign the Contributor License Agreement — once, ever, for every future contribution too.

Read it, then post exactly this as a comment on this pull request:


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant