Thanks for your comment :)
I know rsync but I am not in control of the server in this specific project and the only way I have to update the code is through FTP… I am trying to make as much explicit as possible that this is not a “new fancy deploy technique” but people still seems to complain. Probably they just stop to the title or probably I still need to change something in the very first paragraphs… Any suggestion on this side is really really appreciated!
Not complaining so much as puzzled. Reason you provided makes sense. Haven’t seen people use (s)ftp in ages. There are ways to provide restricted ssh access for the purposes of rsync btw.
Sorry, it was not an attack to you of course.
I just wanted to figure out why people still tell me to use a more modern approach when I am stating as clear as I can that I can’t use anything else apart plain FTP in this very specific case and I wasn’t able to figure out a better FTP-based solution. A lot of people are even insulting me on Reddit, but that’s not a big deal for me honestly, it just make me laugh :)
What concerns me is that maybe I am missing some chance to improve the post or to learn some alternative solution, which would be a shame!
Didn’t even know this was a possibility! Thanks for the in depth writeup on the methods used. Might have to use this to replace my deployHQ setup.
Glad you appreciated the post, but please don’t use this as standard deployment mechanism for new projects. There are far better ways to deploy code (probably your deployHQ is already a better alternative), so use this only when you have a legacy project and when you are not in control of the development/deployment environment.
Yep. Just static sites that don’t justify the deployHQ cost. For a new project I’m using a gulp plugin to upload Shopify theme changes as I make them through their API. Has made the development process so much easier.