feat(deploy): add VPS-ready docker compose and health checks - #15
Merged
Conversation
Add Dockerfiles and compose spec to build API and web services together. Expose health endpoints for container probes in API and web runtimes. Document VPS deployment and contract checks in bilingual EN/ZH docs.
Clear stale compiler cache artifacts before each fixture run to avoid cross-test contamination, and run e2e tests sequentially for stable CI behavior.
Run package-level tests with explicit stream output so fixture checks remain stable while preserving deterministic guardrail command output.
Keep .env inputs minimal, remove domain/TLS knobs from root Compose, and pin Caddy/contract tests to a fixed :80 listener with explicit published HTTP port mapping.
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
1 participant
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.
Summary
Add a repo-root Docker Compose deployment path for RSSift on a
single VPS. The stack now builds both apps, runs migrations,
adds service health probes, and fronts traffic through Caddy.
What Changed
compose.yaml,Caddyfile,.dockerignore, and.env.exampleas the repo-root deployment contracton readiness instead of process launch timing
while keeping package-local ownership of runtime logic
English and Simplified Chinese requirements and plan docs
pnpm testexits cleanlyand root e2e runs avoid shared database races
Validation
pnpm typecheckpnpm --filter api test -- --runTestsByPathsrc/health/health.controller.spec.ts