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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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
Self-hosting is a very individual journey - everyone wants different things and finds they own way to meet their own requirements. So there isn't really one guide that covers everything.
Anyway, as a general road map:
Create a Virtual Machine on your PC. Install Linux inside the VM.
Play around in the VM to learn Linux basics. When you break the OS you can just wipe the VM and reinstall.
In the VM, try some docker containers until you're comfortable-ish with docker.
Maybe try Yunohost in the VM. You might find Yunohost saves you a lot of time and hassle.
Get hardware suitable for your goals.
Install Linux, configure networking and docker containers on real hardware.
Quick question to the Linux inside the VM; I came across suggestions for a "headless" server, which, if I understood correctly, means no GUI. Is it better to get straight into that, or install a Linux with GUI and use the CLI from that?
Good question.
A GUI will be easier to get into - you can use a gui file browser app to learn the layout of the file system, you can use a GUI text editor to change config files, that sort of thing. It'll mean you can do a few basic things intuitively which will be less intimidating. So from a maintaining momentum and morale point of view it might be best to have a GUI initially even though you have to learn all the cli stuff eventually anyway and you'll most likely be running a headless server on real hardware eventually.
Alright, thank you. This will be the first step. Debian in a VM, full GUI to learn all the basics.
Genuinely, I really appreciate the guidance here, I really want to learn to be as independent as possible tech wise and I’m really excited to get started with this.