I am making great progress on a little online game I am programming.
The thing is that features (not to be confused with feature creep) and minor bugfix changes are occurring at a rapid rate - daily.
What is the easiest way to keep a client upto date with changes happening to frequently?
One thought I had (yes you will scream at me for this), is to have a persistent R/O SMB share and actually execute the game itself across the internet (all of the media will still be installed client side) so the executable itself would be far less than 100kb. This way, once approved changes are made and the executable is placed on the share, everyone would be upto date at next program launch.
I was thinking of having the exe stored on a Raspberry Pi, so there wouldn't be any other critical files that a hacker could comprimise. Just have it dedicated as the 'LaunchPad' server so to speak.
The installer package would install media and the link to the exe '\\servername\program.exe'. Bandwidth shouldn't be a real issue I wouldn't imagine. On a 200Gb allowance this should cater for a max of 2097152000 program launches per month (excluding overheads and other internet factors).
If I got anywhere near this figure then I would have to obviously look at a more robust approah as 2097152000 hit, might be an indicator of a somewhat successful game.
The main concern is hacks to the server with an open SMB port. Unless there are other factors I have not even considered.
What are your thoughts on this approach?