docs: add Zeabur deployment readiness - #1
Draft
yihui-dev wants to merge 6 commits into
Draft
Conversation
|
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
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 verifypnpm exec tsc -p tests/tsconfig.jsonpnpm run tracker:buildpnpm 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.