Windows Scripts - Version Control

[mbedford]

Hi,

 

Does anyone use any form of version control on your Windows startup\shutdown\logon\logoff scripts?

 

We have a fair number of scripts in place and at the moment the management of those files is left to me actually telling my team that I have changed something. Would be nice to have something like Team Foundation Server in place for these but I'm not sure that application is the right place to go.

 

Any idea's or suggestions?

 

Mike

[pete]

I use a git repo for the scripts I write. I keep meaning to migrate them to Gitlab* community edition (or similar) to make it easier for others to check in their stuff.

 

*the self-hosted, only got myself to blame if I delete the wrong DB version.

[gshaw]

Failing that a SharePoint documents library would give you previous versions as well if you want to keep it all within O365

 

We use a SharePoint site for Change Management logging so any changes I make to scripts etc. get logged there as they occur.

[mbedford]

Good idea's however, I am concerned about maintaining the current folder structure and leaving the source files in there original location. If I change the "logon.script" (yeah thats made up!) i would like to be able to publish\checkout that change directly to the original location which is within \\domain\netlogon\folder\folder......

 

Sharepoint would use its own storage location and Git, well i dont know it very well, but given the sensitive nature of the scripts, is hosting them on Git a good idea?? im not criticising, that's a genuine question?

 

Mike

[pete]

and Git, well i dont know it very well, but given the sensitive nature of the scripts, is hosting them on Git a good idea?? im not criticising, that's a genuine question?

 

Mike

 

I think you're confusing "Git" (the source control tool - https://git-scm.com/) with "Github" - a place where people make their git source repositories available to others, usually publicly unless they're paying.

 

My git repository sits on an inhouse server and is only accessible via SSH. If I migrated to GitLab (gitlab.com), I'd be using their Community Edition which you install on your own server and provides a web interface to the git repo, again secured by HTTPS and AD authentication.

 

My scripts don't have any sensitive data in them - any authentication is done machine-to-machine using kerberos, SSL certificates, public key auth or some other shared secret.

[mbedford]

I think you're confusing "Git" (the source control tool - https://git-scm.com/) with "Github" - a place where people make their git source repositories available to others, usually publicly unless they're paying.

 

My git repository sits on an inhouse server and is only accessible via SSH. If I migrated to GitLab (gitlab.com), I'd be using their Community Edition which you install on your own server and provides a web interface to the git repo, again secured by HTTPS and AD authentication.

 

My scripts don't have any sensitive data in them - any authentication is done machine-to-machine using kerberos, SSL certificates, public key auth or some other shared secret.

 

Ah, i did not realise that. Thank you I will take a look. I dont generally have anything of huge privacy concern in our scripts either, but they are thousands of lines long and if I were go through them with a fine toothpick, im sure I would find something I wasn't happy been public :-)

 

Thanks

Mike

[dhicks]

Any idea's or suggestions?

 

I find that Google Drive for storage, along with Drive Notepad, makes for a surprisingly usable development environment. Drive Notepad does syntax highlighting for various languages, and I use rclone to deploy files to servers.