On 20.10.20 15:24, Niresh wrote:
I have a binary file that is basically compiled C application code. If I
send an upgrade command to the controller from the server, the
controller should take that binary file from the server, replace the old
one and run with the updated binary file.
I've distributed custom software as deb packages hosted by a private apt
repository (Sonatype Nexus OSS). Mass-updates got manually triggered via
ansible (which required the aforementioned SSH jumphost).
You can do something similar - package your binaries as a deb package,
host an apt repository and figure out how to trigger updates. Or you can
roll your own update scripts and repo. Or you can search for third-party
solutions. I assume most of the underlying problems are the same - a
trigger mechanism, a hosted package repository, authenticated data pipe,
service restarting, recovery from botched upgrades etc.
--
Kind regards,
Tarmo
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/0552ff7a-cca0-b8fe-de2b-85aeee5d3251%40gmail.com.
