home server spin-off: Plannings #185
Labels
No labels
Ansible
basic support
Ansible
NFS server
Ansible/pxe
Ansible/Wildfly
distribution
bug
distribution
release test
distribution
rfe
documentation
improvement
documentation
new
documentation
review request
documentation
update
meeting
need info
project
backup&restore
project
home server spin-off
project
LocalKDC
project
strengthening updates
status
in progress
status
on hold
status
pending activity
No milestone
No project
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
server/tickets#185
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal is to detail the objectives of the project:
Modification are possible any time when experiences require an adaptation.
Probably the starting point would be the expected user experience. For a lot of SOHO setups, you're not really going to use things like Ansible, and are likely to do things interactively.
That also probably means Cockpit and other web UI based applications needs to be a bigger part of the focus.
I agree, I'm comfortable on the command line, but someone new to using Fedora is probably not going to be.
I still only have limited knowledge of ansible and prefer to do most things via the CLI. It's comfortable for me. (20 years ago, not so much...)
I'm hopeful that our home server spin could achieve the following:
Perhaps our home server spin could be a little more user friendly than our stock enterprise ready Fedora Server, but may not have the simplicity that you see with a distro or project like Freedombox or ZimaOS.
I don't know that we aim to be the next PFsense, ZimaOS, or Freedombox. I suspect we aim to be the OS they would consider being based on if they had to drop the one they currently use (FreeBSD, CasaOS and Debian, respectively).
100% agree with @eseyman. I don't envision our home server spin being anything like those examples either. I really see it as the next level up in the home lab experience. You have some experience with a "fully curated" experience like ZimaOS or Freedombox, and now you would like to have the flexibility to run your own self-hosted apps that you find, but can't install on the "fully curated" because those apps are not in their respective "stores" or list of "approved apps". This was my and my son's experience. First we used "Freedombox" where we started to see the power of having our own self-hosted apps on our network, then he wanted to be able to have a place where he could host his own personally developed web apps, so we moved to Fedora Server, and now I would love it if we could have a "home lab spin" that provides the sane defaults that would benefit the intermediate home lab user.
At the same time if we can make the "on ramp" to self-hosting easier than knowing everything that is to be known about container technologies or everything that needs to be known about running docker or podman from the command line and can give a "configured, secure" experience to home lab enthusiasts I think that would be an exciting Fedora spin.
It would also probably be a better place of focus for ARM, since SBC servers are almost exclusively SOHO servers.
Yes, as written in the wiki, my original intention was / is to focus on some dedicated properties:
one is environment friendlyness and affordability, which is a pointer to aarch64. According to mytesting, e.g. an Rockship RK3588 consumes less power ans an Intel n100, specifically in a home server profile (with many idle cycles).
Another is to provide a much better configurability as the common NAS etc.
And to make home server as much like the professional variant, with the exception of the file system, where BTRFS makes life for home admin much easier. Ans the intial (pre-) configuration is much easier as well.
Dee the wiki here on forge for Details.