Cheng Zhou
19 lines
1.5 KiB
Markdown
19 lines
1.5 KiB
Markdown
# Remove Tencent Cloud Publish Design
|
|
|
|
**Goal:** Remove the GitHub-to-Tencent-Cloud image publishing pipeline and all repository-owned private registry defaults so the repository no longer carries any built-in cloud publish path.
|
|
|
|
**Decisions**
|
|
- Delete the GitHub Actions workflow that SSHes to Tencent Cloud and triggers remote image builds.
|
|
- Delete the repository-owned remote build-and-push script.
|
|
- Remove default private-registry image references from `docker-compose.yaml` and rely on local builds as the default path.
|
|
- Rewrite current documentation and historical plan documents so they no longer describe Tencent Cloud, private registry credentials, or registry-based deploy flows as active repository behavior.
|
|
|
|
**Architecture**
|
|
- `docker-compose.yaml` remains the deployment entrypoint, but defaults to local image builds for `backend`, `backend-init`, and `frontend`.
|
|
- CI no longer contains any branch-triggered publish job for Tencent Cloud or any self-hosted registry.
|
|
- Historical design records are retained only as edited documentation that says the publish path has been removed.
|
|
|
|
**Operational Notes**
|
|
- Anyone who still wants custom image names can set `BACKEND_IMAGE` or `FRONTEND_IMAGE` explicitly, but the repository no longer provides private-registry defaults or a publish pipeline.
|
|
- Verification should prove that no active references to `TCLOUD_*`, `REGISTRY_*`, `publish-images`, or `build-and-push-registry.sh` remain outside of the new cleanup documentation.
|