Looking at this option.. anyone using it? Good, bad, ugly? In multi-server environments (multiple servers in one environment, like prod)?
We currently have link all environments to Git repos but it can be a little flaky… the simplicity of deployments look nice. I currently don’t have a non-prod environment with more than one server to validate how a deploy would work in that scenario so anyone’s experiences would be nice.
And my understanding is that the loading of a new deployment in an environment has a much more structured order compared to Git?
Thanks!
I am not sure I understand the question. We use PSU. We have multiple domains/environments. We divide PSU into Test, Dev, and Prod. Test is really one server in the Dev environment to be the guinea pig for new updates. Dev is multiple servers in multiple domains/environments. All code is written and tested in Dev.
We also use on-premise Git. Once code passes on a test instance in Dev, it can be saved to Git where its applied to all Dev instances. Git maintains version history and does what Git does. Its very simple with PSU. Check the boxes for what code/ features you changed, add a comment and check it in.
Our Prod environment is a one-way Git setup. Code from the Dev branch must be pushed to Prod. Only then is Prod updated. Code cannot be edited in Prod. Only code that passes testing in Dev and then is pushed to the Prod branch becomes available in Prod.
Works great. We also use SQL server. Adding additional servers to an environment is a breeze because the new server only needs 1) Their xml config setup, and 2) Any dependencies like custom PowerShell modules installed. Otherwise, all code and settings are just auto-configured from the PSU database when you install PSU.
NOTE: We also use CyberArk and all accounts are accessed from a secure API safe, and we also use custom functions so the same code will work regardless of domain/environment. Overall, I find PSU outstanding for multiple domains/environments with many instances deployed.
2 Likes
Deployments are a new way to deploy code in PSU environments. PSU packages the system up in I believe nupkg file to deploy from one server to the other. It is supposed to have other benefits as well such as load ordering where github just restores files in no particular order.
Not yet, but I’m very interested in learning from your experience if you get to it first 
Don’t tempt me 
Truthfully, I might be able to get something together in time though.. but I don’t know when. With it being newer I just can’t justify using it in prod… yet. I have seen people make enough mistakes with the git repo that required me to have to fix that this might be worth trying to prioritize.
Not using since: Git is easier to use and Deployments is laggy as hell 
I’ll bite
Can you expand on it being laggy? Just takes a long time compared to Git? Git is pretty quick.. I agree. But did it take significantly longer? Large environment?
thanks!
This sounds clean and like the git setup is working well for you. Back when I first started messing with PSU and Git, I tried to use Git and had nothing but problems. I ended up writing my own deployment script to run as a github action on a local github runner that would deploy the code to our PSU dev or prod server, depending on the github branch.
Looking at the Deployments PSU documentation, it looks very similar to what I’ve developed for our use. That said, I’ll probably stick with my own process as doing so gives me more control over the process and it’s been working very well with a few iterations made over the years.
1 Like
Git is working great. We use an on-premise GitLab. Adam customized PSU for Git features we wanted. It uses an Edit mode. Click Edit in PSU and make changes. Those changes are saved on the server where you made the changes. You can test those changes on that server. You can also undo or delete the changes.
If you click Save for Git editing, it shows a list of the files changed. This is nice because multiple users can make changes simultaneously. Next to each file listed is a checkbox. Check the ones you want saved (the ones you modified). Then create a comment for the change and click Save and they are pushed to GitLab on the branch you configured. The changes will now auto-apply to all servers in the Environment (Dev for us).
If the changes are deemed stable in the Environment (Dev) and pass testing, then go to GitLab and push the changes from Dev to the Production branch. All production severs are now auto-updated.
A feature I will be requesting is the ability to setup PSU so those pushes from Dev to Prod are done with a button in PSU. Would be nice if PSU users don’t have to know or directly use Git at all. It is easy to use right now, but could be easier. It has been very reliable for some time.