How exactly does the client software download process work? I add a client, download the client side application to install…could you give me an overview of exactly what happens there?
I looked all over the server and do not see the client files anywhere, nor do I get how it preconfigures the client with all of the settings.
I ask as I have another project that this sort of work flow would be very helpful but never could understand how to make it happen?
It downloads the client installer from the internet, verifies its signature and then replaces the settings in a file in the installer. You can see the settings file here: https://github.com/uroni/urbackup_frontend_wx/blob/next/data/initial_settings.cfg It looks for the GUIDs in the installer and replaces the data in-between.
It comes from the backup server itself though? So if, for instance, you add to the client GUI a section that outlines who to contact for support (i.e. not you ) we can control where the updated files come from? If I get it correctly, there is a file on the server labeled “UrBackupUpdate.exe” that they would download and run as part of the update process and any changes we make to that file will propagate to our clients if we increment the version number in the “version.txt” file on the server?
I take it that the software generates its own key pair? But then what?
I apologize for all the questions, I am just struggling with this project as comments are few and far between. That is all well and good for the person who authors it, but it makes it difficult for others to follow as we do not have all of the code memorized and it takes a long time to reverse-engineer.