On 04/08/18 10:57, Chris Green wrote:
On Sat, Aug 04, 2018 at 10:26:13AM +0100, Laurie Brown wrote:
On 04/08/18 10:07, Chris Green wrote:
On Sat, Aug 04, 2018 at 09:16:42AM +0100, Jenny Hopkins wrote:
On Wed, 1 Aug 2018 at 16:40, Chris Green cl@isbd.net wrote:
On Wed, Aug 01, 2018 at 03:17:23PM +0100, Bill Hill wrote:
On 01/08/2018 09:07, Chris Green wrote:
> I have several bits of customised configuration that I would like to, > somehow, keep in sync on all the above machines, these are things like:- > > ~/.vilerc - editor configuration > ~/.dircolors - colours for ls
Yes, I do something similar from a folder synchronised by syncthing, I guess that's about as good as I'm going to get.
--
Read up on Puppet - you can run it as a master on your main computer and have it push files, update requests etc. to the others.
Coo, what a load of 'corporate speak', I've yet to find out what it actually does!
... I've found the open-source installtion instructions now, somewhat better. However it does seem that the 'cure' would take more effort than the 'disease' in my case if I used Puppet.
Chris, Puppet (or Chef) would be a gross over-kill for what you want to do.
Yes, that was the conclusion I came to on looking at Puppet.
Ansible would do it (via cron or manually) as it pushes instructionsover SSH (it has no agents on the remote machines), but it does require password-less SSH to work.
There are a number of free tutorials out there, including from RedHat (who now "own" Ansible).
I'll take a look at Ansible, thanks. Outgoing password-less ssh from one machine that's well locked down isn't a *huge* risk. As it is I have ssh keyphrase outgoing from my main machine which uses my login password as the key-phrase so it's effectively passwordless as I tend the leave the machine on (with me logged in) all the time. :-)
The account that runs Ansible commands for you (simply put, it's a clever wrapper that sends shell commands via SSH to remote machines) doesn't need to have any special privileges beyond the ability to connect to the remote machine.
Once connected, one can then structure the command to assume root privileges temporarily if required on the remote machine. Ansible has both a CLI interface, and scripts, which are (essentially) known as playbooks. My guess is that you would use the CLI option.
There's a learning curve! but it's simple enough once you get your head around it.
https://www.digitalocean.com/community/tutorials/how-to-install-and-configur...
There are tons of tutorials out there, this one seems quite good, if a bit of a skim over:
https://blacksaildivision.com/ansible-tutorial-part-1
Cheers, Laurie.