Hey Rusty,
If the text files are edited locally, post-installation, will this confuse the update process and make it fail? Or worse still; will the update complete, but i'll be left with a corrupted text file?
You'll never be left with a corrupt install -- wyUpdate installs updates in a transactional manner. That is, updates either install correctly and the user will have the new version of your software or the update will fail and wyUpdate will rollback to the old version of your software.
If you know a user will be editing a particular file, you can handle this case a few different ways:
- If the file is installed once but you never update it (e.g. config files), then you can just exclude the file from wyBuild and wyUpdate will never touch the file.
- You can include the "possibly-edited-by-user" files in only the latest version tab in wyBuild. Then wyBuild will see there's no old file to create a patch from and it will just include the full file. When wyUpdate installs the update it will copy the full file over any changes your user made.
- If you want to preserve the user's changes but allow the user to optionally replace files, then include the "possibly-edited-by-user" files under a different name (e.g. filename.ext.default) and then run an app or script after the update that offers the user the ability to replace their changes.
Tell me if this helps.
Are people successfully updating web site files with wyBuild?!
Yes, it's not as common as updating plain-old desktop apps, but we have quite a few customers that update websites with wyUpdate.