#Recalbox 4.1 download
What make the download so quick is that the domain is pointing to many IP, and the dns round robin them. I get in the magnificent body a json with the new url to get when updating: I make a GET request to answer is 200 and the response has a body. In the morning, my people would make a last fight on SF3 3rd strike. While we enjoying pixels explosions and stuff, a new build is done on master, deploying the new files to. The day pass, here come the time of the apero.
![recalbox 4.1 recalbox 4.1](http://theminicaketv.free.fr/images/3page-img6.jpg)
Still, I make a GET request to answer is 204: No Content as I already have the last version for the stable branch.
#Recalbox 4.1 upgrade
I know that because i made an upgrade yesterday. The last stable (master) build of recalbox has been done the and has been upgrade to. This is the only way to make dns round robin when recalbox asks for a file, and prevent dns upgrade errors. Upgrade url are on different subdomains of recalbox. He knows that when you are on boardversion master-123456 and you want to upgrade on master (you want a stable upgrade) he will check if the current version available is fresher, and return the url of the upgrade. The service at is aware of available upgrade. This MUST be an automatic process at end. As we put some logs in emulationstation for example, if Kibana reports all is ok, we can open the upgrade to everyone. With this data we can use canary release : only a percentage of uuid will receive the upgrade in the first hour of a release. It's not the /proc/cpuinfo, maybe a random uuid.
#Recalbox 4.1 zip
#Recalbox 4.1 update
as the first release of 4.1.0 will be on the old process, we need to limit the concurrent download when the update will be available.6th step - canary time based for (MR !140 (merged) Issue #159 (closed)).the docker image for recalbox must be compatible with the old way to update.5th step - compatible docker image (MR !137 (merged) Issue #155 (closed)).the image must have old noobs compatibility (MR !144 (merged) Issue #164 (closed)).noobs cannot use query params, we must provide a special path.we must update noobs os.json by contacting them (this can be done in //).4th step - make noobs a part of the image (MR !131 (merged) !138 (merged) Issue #147 (closed) #156 (closed)).when searching an update for master (stable) the recalbox must contact recaleur to see if an update is available.3rd step - use to manage the new updates on master, with canary support (MR !129 (merged) and Issue #145 (closed)).we need to change the way recalbox check for upgrade when searching branch update:.2nd step - make possible branch update again (MR !124 (merged) and Issue #140 (closed)).the master release must be automatically released on a specific fqdn for each release.today, the image recalbox/archive:4.0.2 serve the stable files (for noobs essentially).1st step - the release of the 4.1 unstable on the recalbox infra (MR !117 (merged) !120 (merged) !121 (merged) !122 (merged) !123 (merged) and Issue #133 (closed)).Now that we can use docker images to deploy, we need to deploy unstable versions in the form of containers to the rancher infra. I want updated recalboxes to tell me when an update has succeed or failed.I want to be able to stop an update that is known to fail.
![recalbox 4.1 recalbox 4.1](https://i.ytimg.com/vi/NCvNBs7hn_w/maxresdefault.jpg)
This cannot be S3 or we are broke (seems like 700$/month is not a bad idea of what we should pay if we use it) That means the ability to test dev branches really easily, but also to test the release on master branch (stable) for some recalboxes before letting it spread So the need for recalbox update is the following:
![recalbox 4.1 recalbox 4.1](https://2.bp.blogspot.com/-Y32CLHC_8vc/WVwJdu0ko6I/AAAAAAAAFEM/ni0lUPLRUgcPIk5MG9CY_esRBTo6g_NLwCLcBGAs/s1600/ibm-pc.png)
Long time ago, we had few recalboxes pinging the /./recalbox.version file to know if an update were available.