I understand the reasons why manufacturers don't do it, but given that real-time clock chips draw less than a micro-watt of power, I wish it were common practice to stick a supercapacitor big enough to power a RTC for a month or so on portable-size routers
I didn't realize this, but #Zensical is from the same developer(s) as, and is apparently a continuation of, Material for MkDocs π
> We're putting significant effort into ensuring a smooth migration from Material for MkDocs for all users. Zensical can natively read mkdocs.yml, allowing you to build your existing project with minimal changes.
this is relevant to Surfhosting because the (skeleton of the) doc archive is built with Material for MkDocs.
well, it took several hours of rage, but I now have a phpMyAdmin+phpPgAdmin LXC appliance that's completely separate from my database servers, is set up with minimal permissions (unprivileged container with nesting disabled), and uses about 60MB of RAM at idle. and since it's based on Devuan 6 which just came out, it should hopefully last for quite a while with minimal updates and maintenance.
the setup was not entirely straightforward due to my preference to disable nesting (which considerably reduces attack surface from container to hypervisor) and due to the phpmyadmin package setup scripts not handling any variance from the garden path. but now I have a complete setup document.
anyway, it ain't quite a modern Docker-like container setup running on Flatcar, but I'll get there eventually. and it does use less memory and CPU than such a setup. and with the experience I got, I can much more easily set up unprivileged LXCs based on Devuan 6 in the future.
I did some more digging on how to get my Tailscale traffic to bypass a Wireguard VPN which otherwise routes all internet traffic on OpenWrt without using the 'pbr' package, and found a rather strange document:
π.pdf
tl;dr it's definitely possible, but I'm going to have to bite the bullet and not use the simple "route all traffic over Wireguard and enable a 'killswitch' to prevent leaks" two-checkbox setup I've been using thus far.
#OpenWrt #Tailscale #Wireguard
hmmmm, not many reviews out there of the Banana Pi BPI-F3 board based on the 8-core SpaceMIT K1 SoC ... @npub18hdt...kf64 doesn't have one, and @npub1x028...4ytm hasn't looked at the CPU :blobthinkingcool:
given My price range (which, let's be honest, is $0 so I'd have to get one donated) and available shelf space, if I was gonna get a #RISCV board to tinker with and potentially offer access to devs online for purposes of building & testing software on the platforM, it'd alMost certainly be the @npub1klh7...aj2z BPI-F3.
I really wonder how much of a crimp is gonna be put into the current golden age of cheap computing devices over the next 2 years or so due to AI assholes vacuuming up every component they can get their hands on ... all fabs are now maxed out and there are shortages of RAm, NAND, and HDDs
