|
|
|
|
|
|
by juanse
1219 days ago
|
|
|
Amazing post Michael! I have been following your story for years. I have also a similar project backing, but not as technical as yours. I use also Raspberries for Smart Kiosks that are set to be in restaurants and increase the demand of the most convenient dishes at a time with great photography. I see that you think now of Debian packages as an optimal way for installations in your project. What would you say it is the best way yo keep a Raspberry system "auto-updated"? PD: My skills are way lower than yours. I use mostly Ruby scripts (SystemD) to contact a backend in Rails. |
|
|
>What would you say it is the best way yo keep a Raspberry system "auto-updated"?
I think Debian packages are better than what I was doing, but if I were starting from scratch, I'd try to use Yocto[0] or NixOS[1].
Take this with a grain of salt, because this is secondhand from another founder who had good experience with Yocto, but from what she told me it's optimized for the case of pushing out updates to embedded devices. One of the pitfalls of Raspberry Pis is that the microSDs are vulnerable to filesystem corruption, which can leave the device unbootable. I believe Yocto protects against that where there are always two bootable partitions, so you failover to the other partition and can recover.
[0] https://www.yoctoproject.org/
[1] https://nixos.org/