As long as you configure server side correctly, everything will work, including : launcher's self update, client's update, repair and installation.
Architecture is as follow :
download = a file that contains hash for all Client files used for repairing/installation/updates exemple : http://api.digitalsavior.fr/download
latest = Client's versioning used to tell launcher a new version is out exemple : http://api.digitalsavior.fr/latest
Client = folder containing all the client's files
launcher = Folder containing 3 files
-Launcher.exe = the launcher installator
-Launcher.zip = The launcher zip used for selfupdate
-manifest.json = to detect new updates exemple : http://api.digitalsavior.fr/launcher/manifest.json
Everything about launcher's selfupdate can be ignored, as you can set flag to false in config.json if you don't plan to release new versions of your launcher.
The rest has to be set, but i'll prob set flags to ignore client's updates / installation too, so that no configurations will be needed for this part.




Reply With Quote



