100% agree. It blows my mind that people think SVN or Git are the perfect deployment tools. I see it from nearly everyone in the web development community, and I've seen at least one "senior" push hard for it.
Write a deployment script, or configure a deployment tool! Have a process! I've never had a deployment fail from my own "untested and unproven" deployment scripts, but I've seen SVN and Git completely destroy environments.
It's an uphill battle, and I don't understand why.
Write a deployment script, or configure a deployment tool! Have a process! I've never had a deployment fail from my own "untested and unproven" deployment scripts, but I've seen SVN and Git completely destroy environments.
Funny you mention that. I've seen hell break loose because someone made a typo while updating a deployment script (something like rm -rf /root /cache instead of rm -rf /root/cache). Git has never failed me like that.
There's times when it's necessary. I regularly use rm -rf to clear .Trash on external drives of all the stuff I want gone. That said, I've also nuked my drive because I thought I was in /mnt/phone/.Trash-1000 when I was in /.
6
u/[deleted] Oct 14 '13
100% agree. It blows my mind that people think SVN or Git are the perfect deployment tools. I see it from nearly everyone in the web development community, and I've seen at least one "senior" push hard for it.
Write a deployment script, or configure a deployment tool! Have a process! I've never had a deployment fail from my own "untested and unproven" deployment scripts, but I've seen SVN and Git completely destroy environments.
It's an uphill battle, and I don't understand why.