Update strategy for the RevPi Connect
Update strategy for the RevPi Connect
Do you have a strategy for updating the RevPi Connect? Imagine if I was to deploy a large number of them around the world and want to keep them up-to-date OS-wise, how would I go about? Preferably I would like to test the new version before pushing it to the devices, and then I would like to be able to deploy it to all devices, if possible at a scheduled time.
Re: Update strategy for the RevPi Connect
Hi,
there are couple of options.
* Being a Debian based system, you could enable automatic upgrade of apt packages from your own debian repository. If you're happy with a new package version, push the update into the repo and they're installed on next cron job run.
* Use a configuration tool like ansible. Either push mode when you've got ssh access, or pull mode to pull from a public repository.
* There are other tools to keep fleets of devices up2date, e.g. hawkbit.
there are couple of options.
* Being a Debian based system, you could enable automatic upgrade of apt packages from your own debian repository. If you're happy with a new package version, push the update into the repo and they're installed on next cron job run.
* Use a configuration tool like ansible. Either push mode when you've got ssh access, or pull mode to pull from a public repository.
* There are other tools to keep fleets of devices up2date, e.g. hawkbit.
Re: Update strategy for the RevPi Connect
Thanks, I will look into those!
