Web Service Deployment Workflow

Problem Addressed

This skill targets release failures where the code works locally but the public site shows a blank page, APIs return empty arrays, or the CDN serves stale assets. It turns the path from source code to a publicly accessible, smoke-tested web service into a repeatable checklist for React/Vite front ends and Express BFF back ends.

How It Works

The workflow validates the full serving chain in order:
- Environment and DNS: check SSH access, tccli, domain permissions, and Node.js >= 22; confirm resolution with dig.
- Ingress and origin: configure Nginx static paths and API proxying; when using EdgeOne, set OriginProtocol carefully so HTTPS origin requests do not fail if Nginx only listens on port 80.
- Build and field mapping: clear CDN cache after each build; normalize inconsistent Tencent Cloud TEO fields, nested objects, pagination parameters, and timestamp formats in the backend.
- Verification: run Playwright smoke tests across pages and APIs, then sync the repository and clean temporary state.

Boundaries and Notes

This is optimized for Tencent Cloud Lighthouse/CVM with DNSPod or EdgeOne, and assumes root SSH, domain management rights, and Node.js >= 22. It is not a substitute for security audits or high-availability design. Common blank-page causes include leftover scaffold CSS, nonexistent Ant Design icons, JS hash mismatches, and stale CDN cache.