Production upload over FTPS (explicit TLS, no fallback) instead of plain FTP
Continuous Integration / check (pull_request) Successful in 2m9s
Continuous Integration / build-test (pull_request) Skipped
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 9m9s
Continuous Integration / deploy-production (pull_request) Skipped
Continuous Integration / check (pull_request) Successful in 2m9s
Continuous Integration / build-test (pull_request) Skipped
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 9m9s
Continuous Integration / deploy-production (pull_request) Skipped
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>
This commit is contained in:
@@ -369,13 +369,13 @@ jobs:
|
||||
name: dist
|
||||
path: web/dist
|
||||
|
||||
# Gewone FTP (het productiepakket biedt geen FTPS) naar de map met
|
||||
# FTP over TLS (FTPS, explicit, zonder terugval) naar de map met
|
||||
# voorgerenderde pagina's van de CMS-host, in drie rondes (zie
|
||||
# deploy/upload-production.sh): eerst alles behalve HTML, dan alle HTML,
|
||||
# en pas daarna oude bestanden opruimen. Zo verwijst een bezoeker nooit
|
||||
# naar een bestand dat er nog niet staat. De host zelf en zijn web.config
|
||||
# komen uit de CMS-pijplijn. Deze job kan pas draaien als er een webhost is.
|
||||
- name: Upload naar productie (gewone FTP)
|
||||
- name: Upload naar productie (FTPS)
|
||||
env:
|
||||
FTP_HOST: ${{ secrets.PROD_HOST_ADDRESS }}
|
||||
FTP_PORT: ${{ secrets.PROD_HOST_PORT }}
|
||||
|
||||
Reference in New Issue
Block a user