Git or Subversion? Or is this just a bad idea?
I have a handful of Windows servers that I need to monitor and keep tabs on a variety of custom metrics. These servers are all separate from each other, running in different sites on different networks and owned by different customers, but they're all monitored and managed by me.
I use Zabbix for monitoring, and it covers most of the basics but there are a bunch of custom scripts (batch and powershell) that I need to run periodically to perform various tests. Some scripts are common and others differ depending on the server. There's a dozen or so scripts that run.
The problem I'm having is *maintaining* these scripts. Some of them are common among all the servers. Other scripts are customer-specific. Manually keeping track of them on 50+ servers is getting very cumbersome.
So I had an idea to use a revision control system on my Zabbix server to handle this.
The scripts would go under the "trunk", and I would commit changes to them as needed. Each server would check out the repository and periodically update to the newest version. I can cut branches for servers that need something special, and maintain the scripts on all servers centrally via check in, merges, reverts, etc. as needed using normal revision tools.
I've considered the security implications of doing this - the biggest concern being that an attacker who gains access to by Subversion server could push malicious code to ALL servers simultaneously which would be a disaster. For that reason, this system must be very secure - and I need to not *forget to do anything* to secure it.
I'm most familiar with Subversion so I'm considering using that. But I also wonder if maybe Git would be better?
Or is this a bad idea / is there a better way to do this?
I use Zabbix for monitoring, and it covers most of the basics but there are a bunch of custom scripts (batch and powershell) that I need to run periodically to perform various tests. Some scripts are common and others differ depending on the server. There's a dozen or so scripts that run.
The problem I'm having is *maintaining* these scripts. Some of them are common among all the servers. Other scripts are customer-specific. Manually keeping track of them on 50+ servers is getting very cumbersome.
So I had an idea to use a revision control system on my Zabbix server to handle this.
The scripts would go under the "trunk", and I would commit changes to them as needed. Each server would check out the repository and periodically update to the newest version. I can cut branches for servers that need something special, and maintain the scripts on all servers centrally via check in, merges, reverts, etc. as needed using normal revision tools.
I've considered the security implications of doing this - the biggest concern being that an attacker who gains access to by Subversion server could push malicious code to ALL servers simultaneously which would be a disaster. For that reason, this system must be very secure - and I need to not *forget to do anything* to secure it.
I'm most familiar with Subversion so I'm considering using that. But I also wonder if maybe Git would be better?
Or is this a bad idea / is there a better way to do this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.