SamKirkland / ftp-deploy

Deploy websites over FTP with one command line
MIT License
89 stars 43 forks source link

After 10 minutes Server sent FIN packet unexpectedly, closing connection #28

Open szabolaszlo opened 1 year ago

szabolaszlo commented 1 year ago

Dear Developer Team!

After 10 minutes I always got this error, if I run with --dangerous-clean-slate Error: Server sent FIN packet unexpectedly, closing connection. at Socket.<anonymous> (/var/www/myproject/node_modules/basic-ftp/dist/FtpContext.js:125:56) at Socket.emit (events.js:326:22) at endReadableNT (_stream_readable.js:1241:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) (node:5131) UnhandledPromiseRejectionWarning: Error: Server sent FIN packet unexpectedly, closing connection. at Socket.<anonymous> (/var/www/myproject/node_modules/basic-ftp/dist/FtpContext.js:125:56) at Socket.emit (events.js:326:22) at endReadableNT (_stream_readable.js:1241:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) Many directory creation. It would be great if there will be an option for generate the ftp-deploy-sync-state.json somehow from the actual state. I think this option better then delete everything and copy everything again. Maybe the dry-run could do that.

So what is my thought for users who has already a production code on ftp server: Given, the repository master code equal the production ftp code When, run firstly the deploy with some kind of generete option just like dry-run Then, ftp-deploy-sync-state.json generated without any file deployed

I think this would very helpful for every symfony project becouse in case of a symfony project we have two thousand folders and ten thousand files.

Thank you very much!