![]() ![]() 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |