[Superfud]

Sounds like a simple solution which gets the job done. Using whiskey_disk would reduce your typing by a bit (repeatability is nice for things done all the time), but if you don't have any post-commit tasks you have to run on each deploy, stick with what you have.

Where you'd really see benefit would be when you have multiple config files (with database credentials and addresses, for instance) that vary per server and environment involved. In addition, if you need to run post-deploy actions such as building assets, or run database migrations, a tool would help you.

However, until you feel the pain of your current setup, no need to change what works :)