Changing the FTP site

[Francois Lepinay]

Hi, I have been using wyBuild for several years, I now need to change my FTP provider therefore changing the FTP site. I'm not sure how to proceed, I know we can have more than one FTP server but how does it work? Also, if I remove the old FTP server after a few months, what happend to users that may not use frequently my application and did not update in a few months?

Thanks

[Sam]

The way to do this is to use domain names (i.e. don't use IP addresses in your download site, because you might not always control that IP).

The way you can change old addresses is to remove the old site, add the new site, then rebuild wyUpdate. Include the latest client.wyc in your new update (and everyone who updates to that version will get the client.wyc file with the new download sites.

[Francois Lepinay]

I am using a domain (not the IP addr) but unfortunntely I need to change the domain. If I remove the old site and put a new one and include the client.wyc in my update what happens to users who would only open the application in 6 months from now? Their application still has the old site, do I need to update the old site and the new site for 6 months? Can I (or should I) have both sites in my wyBuild to co-exist during a transition period, and if yes is the first site be the first one to be called?

Thanks

[Sam]

The last update to push to the old site should just be a simple update -- the only file you need to change is the client.wyc file. This client.wyc file will include the new location of further updates.

So, if 6 months from now a user updates your app first they'll update to this old version with the client.wyc fie. Then if they check again, it will check on your new site.


Does that make sense?

[Mordachai]

In terms of keeping the old site around forever... just dump it after a reasonable amount of time.

You can either email them a replacement .wyc file, or supply a link to a full downloadable installer (assuming you guys produce one). They'll get some sort of error about being unable to check for updates, but that doesn't sound insurmountably bad to me.

[NOTE: I'm assuming that your software supplies a way for them to contact support that will continue to work after your domain name changes. Otherwise, you may be stuck with maintaining the old site for much, much longer]

Of course, we'd all be best served by making sure that our updates are being hosted in a domain name that we have complete confidence in controlling forever, so as to avoid this issue entirely