Honestly, what most people lack is foundational networking. How a TCP packet is constructed and routed, for example. The difference between routing and switching. How a TCP connection is built and destroyed. Stuff like that. And a basic knowledge of how a DNS request is made and resolved. And DHCP.
Agreed. Any link to good material?
I have this one bookmarked. Haven't taken it though, has decent reviews: The Ultimate Linux Home Server Course - Learn and improve your Linux skills through building your own home server
Wow, a shoe in!
I would have the same question for LinkedIn Learning
Many local libraries provide access to this incredible resource too. Check yours to see.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DHCP | Dynamic Host Configuration Protocol, automates assignment of IPs when connecting to a network |
| DNS | Domain Name Service/System |
| IP | Internet Protocol |
| TCP | Transmission Control Protocol, most often over IP |
3 acronyms in this thread; the most compressed thread commented on today has 5 acronyms.
[Thread #682 for this sub, first seen 16th Apr 2024, 11:15] [FAQ] [Full list] [Contact] [Source code]
There are a heap of general "Linux Administration" courses which will patch a lot of holes in the knowledge of almost all self-taught self hosters. I'd been using Linux for a while but didn't know you could tab to complete file names in commands till I learned it on Udemy ¯_(ツ)_/¯
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.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!