Problem
aipol.kaps.or.kr currently resolves to aipol-app-vm (20.41.101.22) and nginx serves /var/www/aipol-portal/current, but .github/workflows/deploy-azure-public-site.yml labels an Azure Static Web Apps upload as production. A successful SWA deployment therefore does not update the canonical public site.
Required change
- keep SWA as an explicit preview/dev target only
- deploy the reviewed
site/ artifact to a versioned VM release directory
- verify artifact identity before activation
- run
nginx -t
- atomically switch
/var/www/aipol-portal/current
- automatically roll back on local/live verification failure
- verify the canonical domain with Chromium and RSS checks
- restore the unrelated drifted public-site tests so the official gate can run cleanly
- document the VM as the canonical production target and remove ambiguous SWA prod wording
Acceptance
A workflow run from one reviewed SHA proves Dev/preview and canonical VM production use the same artifact, and https://aipol.kaps.or.kr/global/ changes without an out-of-band manual release.
Problem
aipol.kaps.or.krcurrently resolves toaipol-app-vm(20.41.101.22) and nginx serves/var/www/aipol-portal/current, but.github/workflows/deploy-azure-public-site.ymllabels an Azure Static Web Apps upload as production. A successful SWA deployment therefore does not update the canonical public site.Required change
site/artifact to a versioned VM release directorynginx -t/var/www/aipol-portal/currentAcceptance
A workflow run from one reviewed SHA proves Dev/preview and canonical VM production use the same artifact, and
https://aipol.kaps.or.kr/global/changes without an out-of-band manual release.