Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
They are nice for keeping tools around on spare SD cards that you might not want to run normally. Like that is a good way to look at Parrot or Kali Linux setups.
Checking out how to build an OS from scratch is also handy. It can be an interesting low risk way to explore building Gentoo, Arch, or Linux From Scratch.
The main appeal IMO, is that you have microcontroller like input, output, and serial communications already setup in the kernel with access in user space. As long as the kernel is supported by the Rπ foundation, (it is proprietary undocumented hardware that only they can support), you are getting the security updates required to keep the thing online automatically and safely. The best stuff to build is unique stuff for you that uses these aspects. Like make a little bathroom clock with a little TFT LCD display that tells you the local weather. Then set up some RSS feeds for local community stuff you do not want on your main mobile device, like maybe local political activity, library and community center events, concerts, clubs, etc.
For server stuff, I would stick with devices with purpose built hardware. Like, a micro SD card is slow and unreliable, and the lack of nvme is bad. In most cases it is cheaper to use other old devices that already have screens unless you want to share a hardware design that is repeatable, you need something secure to keep online, or you need serial or input/output. Those are the main benefits.
The thing is, the Rπ is what it is. It is the path of least resistance. The software support is approachable and great. The price is cheap. However, the non profit thing is a scam. The Rπ foundation is basically an arm of Broadcom. The Rπ is a chip from a set top TV box with 3/4 of the die unused. Broadcom uses excess fab capacity to make the Rπ chips and sell them at materials cost. This is not charity. It is controlling the grass roots market to make competitive scaling business ventures difficult. This is why Rockchip is not crushing them already. The Rockchip RK3588 chip is fully documented and open source. In this space, there is little to no innovation, it is only about price on ancient trailing fab nodes. This is the ladder to climb that leads to Intel, AMD, Samsung, and Qualcomm. The Rπ is the guy kicking anyone that tries to climb. So... use it for what it is good for, but in most cases, other hardware is better, and there is nothing wrong with saying so, or moving past the Rπ. I'm lying next to a RK3566 machine right now, sorting out issues with the ARM version of Fedora Workstation, looking at how to build the native WiFi module for it from source, and maybe try debugging an issue in that module's code that is causing a memory race condition. Although that last one is past my typical pay grade. - So I'm not all fluff here.
That is just my $0.02.