Hi, my company has been trialing wyupdate in order to update one of our apps and so far we have been very impressed with it. Currently we plan on using it for one of our apps only but if it proves successful we would like to use it along with our other apps as well.
I am looking for some best practice advise on how we can go about deploying wyupdate to our customers. Our situation is that we have multiple customers (all healthcare) who all wish to host the update servers themselves within their own network for security reasons, so a cloud based solution is not an option. As each customers update server will have a different URL this means that we will have to create a wyBuild project for each customer in order to set the unique download url. With over 100 wybuild projects for just one application (and we hope to use wyupdate with several other apps in the future) it could get very messy to maintain. We also need to be able to handle any changes to the url for the downloads although I believe we can do this by including an updated wyc file in an update package.
My question is: what is the best strategy to tackle this kind of situation? Are we stuck with having many different wybuild projects for each application in order to maintain unique download urls or is there a better way of handling this.
Thanks
Hey Mark,
As each customers update server will have a different URL this means that we will have to create a wyBuild project for each customer in order to set the unique download url.
Not necessarily. You can use dynamic download sites using the %updatepath% variable in the download site and passing the -updatepath to wyUpdate.
Tell me if that helps.
