News for hackers. Stuff that matters.
Re:Rsync, GUIs, power, control, design, and decisions by SkyMarshal on Tuesday July 09, 2019 @12:37PM (#20393620)
Or just script it, include good comments explaining why you used all the switches you used, and back up the scripts to your favorite backup service. Available everywhere and explained well so you don't forget why you choose the switches you did.
Re:Rsync, GUIs, power, control, design, and decisions by dvtrn on Tuesday July 09, 2019 @12:45PM (#20393744)
Good suggestion here.

I created a single serving Ansible docker image with a couple of playbooks for this very purpose --devs were asking frequently to pull schemas or dump from various data sources internally "Hey I forgot the command to do this, what was it again?".

Eventually I gave them a Dockerfile, wrote up some documentation on how to change hosts in the run command if they so desired, questions all but stopped immediately, and the devs loved it.

I now get a new question "hey, can you make one of those but to do this?"

"Sure, here's a playbook for it, put this in that directory on your local machine and it'll be available in the container". Combined with dynamic host inventories, it's made me a few friends lol

Re:Rsync, GUIs, power, control, design, and decisions by mixmastamyk on Tuesday July 09, 2019 @12:48PM (#20393802)
And in the scripts, use the long-form flags, so many comments are unnecessary.