The production upload is plain FTP now (the production package offers no FTPS or SFTP).
deploy/upload-production.sh: never tries TLS (ftp:ssl-allow no), passive mode, optional FTP_PORT (from PROD_HOST_PORT). It no longer puts a web.config on the server: the host and its web.config come from the CMS pipeline. Three rounds (everything except HTML, then all HTML, then cleaning up) into the prerendered-pages folder of the CMS host (PROD_DEPLOY_PATH); it deletes nothing outside that folder.
The job deploy-production uses the secrets PROD_HOST_ADDRESS, PROD_HOST_PORT, PROD_HOST_USERNAME and PROD_HOST_PASSWORD.
Tests in e2e/deployScripts.e2e.ts adapted, plus a test for FTP_PORT.
Docs: section "Plain FTP to production" in docs/deploy-and-ci.md with the risks and measures (own FTP account with rights only on that folder, unique password only as a secret, rotate after the first rollout, ask the host about SFTP or FTPS).
Nothing here turns production on: deploy-production still only runs by hand from a release branch and with Bryan's go. The exact folder on the IIS host (PROD_DEPLOY_PATH) is still open (plan A2).
The production upload is plain FTP now (the production package offers no FTPS or SFTP).
- deploy/upload-production.sh: never tries TLS (ftp:ssl-allow no), passive mode, optional FTP_PORT (from PROD_HOST_PORT). It no longer puts a web.config on the server: the host and its web.config come from the CMS pipeline. Three rounds (everything except HTML, then all HTML, then cleaning up) into the prerendered-pages folder of the CMS host (PROD_DEPLOY_PATH); it deletes nothing outside that folder.
- The job deploy-production uses the secrets PROD_HOST_ADDRESS, PROD_HOST_PORT, PROD_HOST_USERNAME and PROD_HOST_PASSWORD.
- Tests in e2e/deployScripts.e2e.ts adapted, plus a test for FTP_PORT.
- Docs: section "Plain FTP to production" in docs/deploy-and-ci.md with the risks and measures (own FTP account with rights only on that folder, unique password only as a secret, rotate after the first rollout, ask the host about SFTP or FTPS).
Nothing here turns production on: deploy-production still only runs by hand from a release branch and with Bryan's go. The exact folder on the IIS host (PROD_DEPLOY_PATH) is still open (plan A2).
The production package only offers plain FTP. The upload goes into the
prerendered-pages folder of the CMS host; the host and its web.config come from
the CMS pipeline.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The production upload is plain FTP now (the production package offers no FTPS or SFTP).
Nothing here turns production on: deploy-production still only runs by hand from a release branch and with Bryan's go. The exact folder on the IIS host (PROD_DEPLOY_PATH) is still open (plan A2).