ground-init
mkfs
| ground-init | mkfs | |
|---|---|---|
| 5 | 1 | |
| 34 | 10 | |
| - | - | |
| 7.0 | 10.0 | |
| 11 days ago | over 1 year ago | |
| Python | Go | |
| MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ground-init
-
I don't think the cheapest APC Back-UPS units can be monitored except in Windows
I have a 550ES, works fine. Some models will require apcd instead of nut, but I have configs for using Proxmox with both here: https://github.com/rcarmo/ground-init/tree/main/samples
- Install a machine with something that is almost, but not quite, cloud-init
-
Gokrazy Is Cool
I never had any serious issue with SD cards since the Pi 2B (and I've kept Pis running for years).
Anyway, for those wanting to deploy more generic apps, that is why I initially wrote https://github.com/piku/piku - you still have to flash the OS (and rpi-imager does that with sane defaults these days), but once you're done you have Heroku-like deployments for any language runtime you install on the Pi.
I also have https://github.com/rcarmo/ground-init, a cloud-init like shim that simplifies setting up machines (I'm a big fan of cloud-init, but since Raspbian doesn't support it and Ubuntu on ARM requires some fiddling to make it work I decided it wasn't too hard to roll my own).
(I probably should look into glueing that into rpi-imager, but there is are only so many hours in the day...)
- Rcarmo/ground-init: Install a machine with almost, but not quite, cloud-init
- Ground-init – set up your desktop automatically
mkfs
-
Gokrazy Is Cool
What a coincidence! I've just been playing with Gokrazy a couple weeks ago, and just kept thinking "this is so cool". If you're building some sort of an appliance, and want the least amount of reliance on / hassle maintaining the base OS, it definitely is a viable choice.
It can also run programs that are not written in go, by using a little neat hack to build/embed a binary inside a Go package; this is e.g. how Gokrazy sets up persistent storage: https://github.com/gokrazy/mkfs
I don't think it's for everyone; if you're relying on your base OS / package manager for a lot of stuff, or just want to run Docker containers, I think there are simpler/better ways to set things up. But it's absolutely great at what it's made for; doubly so with the Raspberry Pi's finally being back in stock.
What are some alternatives?
router7 - router7 is a small home internet router completely written in Go. It is implemented as a gokrazy appliance.
u-root - A fully Go userland with Linux bootloaders! u-root can create a one-binary root file system (initramfs) containing a busybox-like set of tools written in Go.
consrv - Command consrv is a SSH to serial console bridge server, originally designed for deployment on gokrazy.org devices. Apache 2.0 Licensed.
juicefs - JuiceFS is a distributed POSIX file system built on top of Redis and S3.
gocryptfs - Encrypted overlay filesystem written in Go
bigfile - Bigfile -- a file transfer system that supports http, rpc and ftp protocol https://bigfile.site
goofys - a high-performance, POSIX-ish Amazon S3 file system written in Go
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.