This is just fyi

1. The whole system is JS based and uses some conventions
2. It will ask github for the release packages - and then it will assume that the same file exists in the content-installation folder on /Packages
3. It will then return the url /packages/[last github release file name] to the browser
4. The browser will then take that url and ask it's own server to install this
5. The server (hosting the new 2sxc) will then get the file and install it

This may be a bit strange. originally we just got the files from GitHub, but ca. 2016 Github blocked the requests after they had a big DDOS attack. So this is why we have to keep our own copy :(