Hacker News new | past | comments | ask | show | jobs | submit login

That's an incredibly process-immature way of managing deployment.

How do you know what version you have deployed unless you copy everything you deploy to some archive somewhere?

How do you roll back?

How do you find out if you monkey-patched something?

Deploying Docker images or static binaries is vastly superior and no more difficult. It's just a new paradigm.




I don't think I even disagree with you here, but to use arguments for version control as your arguments for docker images and static binaries seems odd.

All three of the issues you raise would be solved by involving a VCS somewhere in your FTP deployment.

Incidentally, claiming that either option is "no more difficult" than FTP upload or even using VCS is either disingenuous or at least a little blinkered. FTP can work as simply as copying files between "folders", I've successfully taught my non-techy parents to use FTP. Setting up docker images or static binaries requires significantly more understanding of what's going on but of course provide speed, consistency and scalability benefits.


"Vastly superior" how? I can have those features with a tool like deployer (written in PHP) and the only dependency is SSH.




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: