The hosting partner offers FTP over TLS after all (Bryan, 2026-11-19, via SLS-Main), so the production upload no longer is plain FTP.
upload-production.sh: explicit FTPS (AUTH TLS) is forced: ftp:ssl-allow yes, ftp:ssl-auth TLS, ftp:ssl-force yes, ftp:ssl-protect-data yes, ftp:ssl-protect-list yes; no fallback to plain FTP; certificate verification on (ssl:verify-certificate yes); passive mode; host is given as ftp://host
Unchanged: the three rounds, the folder restrictions, no backup files, FTP_PORT check
Tests (e2e/deployScripts.e2e.ts): every lftp session has the TLS settings and none has ssl-allow no or verify-certificate no
Docs: deploy-and-ci.md (section FTPS to production replaces Plain FTP), cms-integration.md, workflow comments
Not in this PR: the FTP-only correction in aidlc-docs/features/asf-production-iis/plan.md; that file is only on branch feature/asf-production-iis (SLS)
The real FTPS connection is not tested here; Bryan tests it with the PROD_HOST_* secrets. If the host has a non-public certificate, the CA file is needed and Bryan is asked first.
The hosting partner offers FTP over TLS after all (Bryan, 2026-11-19, via SLS-Main), so the production upload no longer is plain FTP.
- upload-production.sh: explicit FTPS (AUTH TLS) is forced: ftp:ssl-allow yes, ftp:ssl-auth TLS, ftp:ssl-force yes, ftp:ssl-protect-data yes, ftp:ssl-protect-list yes; no fallback to plain FTP; certificate verification on (ssl:verify-certificate yes); passive mode; host is given as ftp://host
- Unchanged: the three rounds, the folder restrictions, no backup files, FTP_PORT check
- Tests (e2e/deployScripts.e2e.ts): every lftp session has the TLS settings and none has ssl-allow no or verify-certificate no
- Docs: deploy-and-ci.md (section FTPS to production replaces Plain FTP), cms-integration.md, workflow comments
- Not in this PR: the FTP-only correction in aidlc-docs/features/asf-production-iis/plan.md; that file is only on branch feature/asf-production-iis (SLS)
- The real FTPS connection is not tested here; Bryan tests it with the PROD_HOST_* secrets. If the host has a non-public certificate, the CA file is needed and Bryan is asked first.
No production deploy and no release branch.
Generated with [Claude Code](https://claude.com/claude-code)
The hosting partner offers FTP over TLS after all. upload-production.sh now forces
AUTH TLS (ssl-force, protect-data, protect-list), verifies the certificate and stays
passive; the three rounds and the folder restrictions are unchanged. Docs, workflow
comments and the lftp tests follow.
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 hosting partner offers FTP over TLS after all (Bryan, 2026-11-19, via SLS-Main), so the production upload no longer is plain FTP.
No production deploy and no release branch.
Generated with Claude Code