Production upload: plain FTP, no web.config from this repo #24

Merged
Sluijsens merged 1 commits from feature/asf-prod-plain-ftp into master 2026-11-18 22:14:21 +01:00
Owner

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).
Sluijsens added 1 commit 2026-11-18 21:24:29 +01:00
Production upload: plain FTP (no FTPS), no web.config from this repo, optional port
Continuous Integration / check (pull_request) Successful in 4m12s
Continuous Integration / build-test (pull_request) Skipped
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 44m28s
Continuous Integration / deploy-production (pull_request) Skipped
1f087581d4
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>
Sluijsens merged commit 93a8b31eb2 into master 2026-11-18 22:14:21 +01:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SLP_Software/AndreaSlopFotografie#24