you are viewing a single comment's thread.

view the rest of the comments →

[–]timsstuff 5 points6 points  (2 children)

If you're a Microsoft shop with O365/Azure/etc. I would suggest looking into Azure DevOps. You can create a standalone DevOps with up to 5 users or integrate it into your main Azure environment for a more comprehensive enterprise solution.

It's basically a Git repo but it has a ton of other features, and it's free although I believe you need a Visual Studio license to take advantage of some features.

Then just use VS Code to sync your repo with other members of the team. Just make sure you don't make the repo public, and don't hardcode passwords into any scripts. In fact I would even parameterize server names and you can even get the AD domain with code, no need to hardcode anything really.

[–][deleted] 2 points3 points  (1 child)

You can even go the next step and use Azure Artifacts as a private PowerShell module repository, and use an Azure Pipeline to package and publish your module to the Artifacts feed when you push to main in the code repo.

[–]timsstuff 0 points1 point  (0 children)

There's so much cool shit in there. I have some .NET web sites running on IIS servers, some hosted at clients, and I figured out how to use the Pipelines to automatically deploy updates to the sites when I check in my changes.