ctms/docs/plans/2026-03-30-remove-tcloud-publish-implementation.md

Remove Tencent Cloud Publish Implementation Plan

For Claude: REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

Goal: Remove GitHub-to-Tencent-Cloud publishing, private registry defaults, and related documentation from the repository.

Architecture: The repository keeps local Docker build support for backend, backend-init, and frontend, but removes all built-in publish automation and private-registry defaults. Documentation is rewritten so Tencent Cloud and self-hosted registry deployment are no longer described as current behavior.

Tech Stack: GitHub Actions, Docker Compose, FastAPI, Vue/Vite, Markdown documentation

---

Task 1: Remove publish automation

Files:

• Delete: .github/workflows/publish-images.yml
• Delete: scripts/build-and-push-registry.sh

Step 1: Delete the GitHub workflow

Remove the workflow that SSHes into Tencent Cloud and runs remote image publication.

Step 2: Delete the remote publish script

Remove the repository-owned script that logs into the private registry and pushes images.

Task 2: Remove private-registry defaults from compose

Files:

• Modify: docker-compose.yaml

Step 1: Switch runtime defaults to local image names

Remove REGISTRY_HOST-based defaults from backend, backend-init, and frontend.

Step 2: Keep local build support intact

Retain the existing build: blocks and any required build args for the frontend.

Step 3: Verify rendered compose

Run: docker compose config Expected: PASS without any REGISTRY_HOST-derived default image names.

Task 3: Rewrite active docs

Files:

• Modify: README.md
• Modify: docs/guides/release-checklist.md

Step 1: Remove Tencent Cloud and private registry sections

Delete active deployment guidance that references GitHub Actions, Tencent Cloud, REGISTRY_HOST, or private registry authentication.

Step 2: Keep deployment instructions aligned

Document the repository as local-build-first and external-deploy-managed.

Task 4: Rewrite historical design records

Step 1: Remove superseded Tencent Cloud/private registry records

Remove the standalone Tencent Cloud private registry design and implementation records after the active publish path has been deleted. Keep only this cleanup plan as the historical trace.

Step 2: Remove superseded Nginx removal records

Remove the standalone Nginx removal design and implementation records because the repository-managed Nginx entrypoint was later restored. Keep 2026-03-31-restore-nginx-design.md as the current historical record for that reversal.

Step 3: Remove references to active publish files

Update any references to .github/workflows/publish-images.yml, scripts/build-and-push-registry.sh, or private-registry defaults if those files/configs no longer exist.

Task 5: Verify cleanup

Files:

• Verify only

Step 1: Render compose

Run: docker compose config Expected: PASS

Step 2: Search for active Tencent Cloud/private registry references

Run: rg -n --hidden -g '!/.git' -g '!frontend/node_modules/**' -g '!docs/plans/2026-03-30-remove-tcloud-publish-design.md' -g '!docs/plans/2026-03-30-remove-tcloud-publish-implementation.md' -S "Tencent|腾讯云|TCLOUD|publish-images|build-and-push-registry|REGISTRY_HOST|REGISTRY_USERNAME|REGISTRY_PASSWORD" . Expected: no active repository references remain.