-
Notifications
You must be signed in to change notification settings - Fork 554
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OTA Updates #1
Comments
Or just take a diff of whats on master or a tagged version for docker-compose and apply the patch if the user agrees |
So flow would be.
|
I haven't worked with patch files yet, so not sure how it works. But here was my approach: |
to make a patchfile diff -u docker-compose.yml docker-compose.yml.new > version.patch version.patch contains ALL the changes. Applying the patch patch docker-compose version.patch |
We need a way for the users to reliably update their umbrel node over-the-air.
Whenever a new release of
umbrel-compose
is made, it should prompt the user on his dashboard about the new update, and should only install the update after the user explicitly confirms.The update prompt should also include a changelog listing all the changes.
My experience with mender.io didn't bear much fruit in this regard, as mender only allows a maximum of 24 hours for the update to be deployed on a device after it's been released (as their product is focused on IoT devices and not end-user interactive devices).
Nonetheless, the update scripts that I wrote when testing mender's update module can still very much be used by our custom solution.
The text was updated successfully, but these errors were encountered: