Create A records to your Tencent Cloud public IP:
element-plus-x.comv1.element-plus-x.comv2.element-plus-x.com
- Copy
scripts/docs/nginx/element-plus-x.confto/etc/nginx/conf.d/element-plus-x.conf. - Create the redirect target file:
sudo mkdir -p /var/www/element-plus-x/root
echo 'set $root_target https://v1.element-plus-x.com;' | sudo tee /var/www/element-plus-x/root/redirect.conf- Create base directories:
sudo mkdir -p /var/www/element-plus-x/v1/releases /var/www/element-plus-x/v2/releases
sudo mkdir -p /var/www/element-plus-x/v1/current /var/www/element-plus-x/v2/current- Test and reload:
sudo nginx -t
sudo systemctl reload nginxUse Certbot to issue TLS certificates for the three domains. Example:
sudo apt update
sudo apt install -y certbot python3-certbot-nginx
sudo certbot --nginx -d element-plus-x.com -d v1.element-plus-x.com -d v2.element-plus-x.comConfigure these secrets in the repo settings:
DOCS_DEPLOY_HOSTDOCS_DEPLOY_PORTDOCS_DEPLOY_USERDOCS_DEPLOY_SSH_KEYDOCS_DEPLOY_BASE_DIR(suggested:/var/www/element-plus-x)
Use the Docs Deploy Verify workflow for the first end-to-end server test.
- Trigger it manually from the default branch.
- Point
source_refto the branch or tag you want to build. - It uploads to
${DOCS_DEPLOY_BASE_DIR}/verify/<line>/<verify_id>. - It does not switch
current, does not changeroot/redirect.conf, and does not reload nginx.
Use the Docs Release workflow for release uploads and cutover.
switch_current=falseuploads the release without switching live traffic.switch_current=trueupdates the<line>/currentsymlink.update_root_redirect=trueupdates the root domain redirect when the release should become the default docs line.