regarding switching, ready at any moment
Also beware about potential comment vandalizm
I usually post my slides as google slides these days tho
Will release in 1h if no negative feedback
Created winsw/winsw#630 . I will not be releasing WinSW until the YAML configuration support is actually added for users and documented
Yes. My plan was, select the configuration type(XML or YAML) by configuration file provided by the user. For that, we have to integrate both new CLI and YAML Support. That was how I did the demo. But there is another workaround we can do. Find the configuration file with the same name as the executable and select the configuration type (XML or YAML). If both are available then continue with XML. If that workaround sounds good I can implement that. Otherwise, we can integrate both new CLI and YAML support. What do you prefer?
Anyway how should I continue on that? I can allocate time for this.
Taking our time and the velocity, it is likely that New CLI does not get finished in time. So I suggest to focus on the deliverables critical for the next evaluation
Is there a reccomended way for updating the wrapped application that winsw is wrapping? Can we just swap out the file mentioned in the config and it will continue happily? Does it need a restart or an uninstall?
@dave-q Windows doesn't allow replacing running executable files. See https://github.com/winsw/winsw/issues/184#issuecomment-666890996 for some workarounds.
A service restart is required in order to run the new version of the wrapped application.
@dave-q @NextTurn If this is not about runtime update, there is a feature which allows to download new application binaries on the startup. https://github.com/winsw/winsw/blob/master/doc/xmlConfigFile.md#download
1 reply