4 ms·
I'm kind of in this boat now with a couple of products. The catch is I need to do both local and OTA updates. This seems to be a rare feature that nobody is d
by karmicthreat 10y ago
I'm kind of in this boat now with a couple of products. The catch is I need to do both local and OTA updates. This seems to be a rare feature that nobody is doing.
I also am trying to get Resin.io like containers working. It seems like it would be an easier way to test and deploy.
- Matthias247 10y agoThat's also a requirement for me - local updates (via connected USB stick, triggered via reboot or web interface) should work also in addition to OTA. _In fact local updates would have an even higher priority. We fiddled around also a little bit with the container route. I liked it for quick iteration times (rebuild a docker container, pull it from local image registry to device and test it there). But we found out that we won't get by with just container updates, and that most updates would also need to contain a new kernel or kernel module versions.
- eystein 10y agoIt is not that uncommon for an updater to support both local and remote updates. For example, Mender has two modes of operation: standalone and managed [0]. Like you, many teams are still doing local updates, or transitioning from local to OTA, at least for some products. [0] https://docs.mender.io/1.0/Architecture/Overview#modes-of-operation https://docs.mender.io/1.0/Architecture/Overview#modes-of-op...
- deleted 10y ago[deleted]