The button is also found under āFilesā - just hover over it and select what you changed, otherwise everything gets reloaded (which takes some time).
Just out of curiosity, why do you edit files under āFilesā?
In general, it would be great if PSU would check whether the disk has a different version when the user starts editing a file and ask whether āreload configuration filesā should be executed before editing.
(I guess that it doesnāt take much effort to perform this check, and it protects customers from strange/unexpected problems.)
Iāve come across this, I have auto refresh turned off because i donāt want my apps to recycle (not sure if this is just for the app code or scripts too) If I know Iām going to be modifying scripts outside of the PSU GUI, I have a script with Sync-PSUConfig in it, I run that whenever I need things to update in PSU.
Thank you very much for your answer and your proposal for your manual workaround.
Unfortunately, I couldnāt find the āauto refreshā option anywhere. Could you please tell me where to find it?
I much prefer working with āauto refreshā because I always want the last change I made to be active (otherwise I wouldnāt make any changes), so I donāt want to have to specify that the change should be activated
I donāt think it was auto deploy, maybe the terminology has changed between v4 and v5 as I cant find it in my console but there was essentially a watcher on the Repository directory that checks for file changes and then restarts the apps you have in order to update them if any changes are made, I think that this only applies to apps and not scripts though.
@Schittli - You could always create a script and schedule to run every x mins for Sync-PSUConfig