A few questions on if this can be done

Evening all,I was hoping someone might tell me the feasibility of a few ideas I have for using this,

would it be possible to somehow update iis websites, to keep them synced with a central version ?

would it be possible to have a tiered update system, for example say i have 100,000 applications that want to be upgraded and they span globally, I have servers locally to those applications that I would prefer they updated from, and then somehow updated the servers update directory from a central location, so I update my central repository and that feeds down, to the servers then to the applications ?

any pointers on doing the above would be much appreciated 🙂 (this is for an internal applications and websites hosted on an intranet)

Sure, something like this is possible. Exactly *how* you do this depends on the specifics of how you want to implement it, but the short version is that you will have "dynamic" download sites. That is use the -updatepath="<url>" wyUpdate commandline option and %updatepath% download site variable to specify dynamic download sites.

This way you can push out updates to tiers. I can get into specifics if you want.

Thanks, how would you then update the local servers though to a central version(manually having to upload each change to lots of servers doesn't sound like fun). Another one of my concerns in regards to this is that during the update of the tiered servers the engine see there is an update and start downloading a non complete update(could this happen or is there safe guards for this?)thanks again for the response

maybe a better question, is can you update an update directory through a secondary service ?

maybe a better question, is can you update an update directory through a secondary service ?

Yes. Simple make sure you're calling wyUpdate in the target directory, or make sure wyUpdate knows about the target directory by using the -basedir commandline option.

Another one of my concerns in regards to this is that during the update of the tiered servers the engine see there is an update and start downloading a non complete update(could this happen or is there safe guards for this?)

Upload your updates to a separate folder then either soft link them to the download site. That is, don't make the updates accessible until they've been uploaded. There are a thousand ways to do this depending on your server operating system, HTTP server software, etc.