We have many customers, but they are on different versions of our software, and more importantly should not always be running the "latest" version.
Based on their license, they are allowed up to a minor version, including any builds. For example, if licensed for version 3.4, they should install the latest build from that version, i.e. 3.4.100, when possible builds are 3.4.1, 3.4.20, 3.4.100, 3.5.0 etc.
Rather than the license checking just return a yes / no type of answer as it does now, is there any way it can return a maximum version the license can be used for?
Currently our workaround is we have many folders for the update.txt file i.e. https://host.abc.com/3.4.1/update.txt, https://host.abc.com/3.4.20/update.txt, and https://host.abc.com/3.4.100/update.txt. Each one containing just the allowed update. We then need to override the url in the client for each check based on max version. But this is very messy, resulting in lots of duplication of files, and lots of manual work each time we release a new version. Multiply this by the installers for each installation, currently around 10, and this makes a lot of manual work.
Is there a better way, there we can limit an update version or request a specific version so I can have a single update.txt per installer and put all the updates in a single folder?
FOLLOW US
Get the latest news in Application Packaging