raspberryapi VS gokrazy

Two notable modules: Echo as a web framework & shirou/gopsutil for fetching OS data. Multiple endpoints are available to retrieve host, process, ram + CPU + disk usage, and temperature information. Also offers the possibility to run admin tasks (change the hostname, add a user, etc.). The documentation is in progress but many endpoints are already documented here -> https://raspberryapi.com/ - Repo here https://github.com/layerzzzio/raspberryapi Have fun

Switching to gokrazy[0] was the best thing I did for my Raspberry Pi uptimes. I think a lot of that is because it defaults to using read-only partitions so the common issue of SD cards falling over when you run apt upgrade no longer happens.

But I also think that gokrazy's simplicity and design helps it be just a solid, reliable foundation to build on top of.

[0]: https://gokrazy.org/

The idea there sounds a lot like https://gokrazy.org/, which builds a minimal go userland, wrapping one or more user provided go applications, and bundles in a linux kernel.

Targets mostly at single board computers, and I think it downloads pre-built kernels (and bootloaters if needed), rather than trying to build them directly, since getting a working cross compilation toolchain set up and plumbed into the kernel compilation process is still a pain.

I've personally only used yocto/open-embedded for that which does nicely handle building the cross-compilation toolchain, kernel image, and modules. But it is kinda overkill for that task, being designed to build a whole userland too.

reminds me of https://github.com/gokrazy/gokrazy which does similar things.

https://gokrazy.org/ would like a word

Fun! We have support for running on gokrazy (https://gokrazy.org/) already, and that's probably where Unikernel Linux is more applicable for us, for when people just want a "Tailscale appliance" image.

I'll email you.

gokrazy exists! https://github.com/gokrazy/gokrazy

https://github.com/gokrazy/gokrazy for one example