I assume most users here have some sort of tech/IT/software background. However, I’ve seen some comments of people who might not have that background (no problem with that) and I wonder if you are self-hosting anything, how did you decide that you would like to self-host?
You must log in or register to comment.
I’m a farmer that was an IT guy a decade or so ago, which I guess is a background in it, but that’s not why I do it. Self-hosting is a self-reliance thing. I like to fix my own equipment, metal and silicon.
When it comes apart, I want to know the reason, and I like to invent new ways to do things, which means I have to be able to control my infrastructure.
Honestly it would be really cool to see more self hosting in the farming space. I want to see a iot system that it run by the farmer.
Before we know it there will be a server room at each farm
Teacher here. No professional affiliation with PCs, Linux or self-hosting. Started out with a Synology NAS and got my first experiences with Linux, CLI, Docker, etc. Switched to Unraid last fall and I self-host quite a lot of services now. 100% self-taught.
I love unRAID so much. It’s crazy how just a simple GUI can help solidify docker concepts.
Are you me?
Medical device engineer here (mechanical engineering). I host jellyfin, game servers (Minecraft, factorio, valheim, etc), my website, and a bunch of other minor services I find useful.
I got into it originally through a combination of poor internet, and being fed up with Google and others discontinuing products/features. The internet problem is solved now, so my only goal is not being reliant on someone else’s cloud.
I don’t work in IT/Tech at all, but I’ve been an enthusiast since I was young, at first piggybacking off of my dad, then developing my own interests as I got into high school and college. I started self-hosting because I found it interesting and as time progressed I saw the benefits of operating things locally. I only host things within my own network though, because I’m not yet comfortable with how to safely set up external access.
Self hosting is your pathway to a tech background.
University for comp sci, in my experience around the space, is a complete waste of time. Just a piece of paper that may or may not equip the recipient with some skills that may or may not be relevant.
University is ok if you’re starting at zero and don’t even know what’s out there. It’s for exposing students to a a breadth of topics and some rationale of why things are as they are, but not necessarily for plugging them into a production environment.
Nothing beats having your own real world project, either for motivation or exposure to cutting edge methods. Universities have tried to replicate that with things like ‘problem based learning,’ and they probably hope that students will be inspired by one or two of the classes to start their own out-of-class project, but school and work are fundamentally different ways of learning with fundamentally different goals.
When they were installing the alarm at my house I noticed that the main guy had nextcloud on his phone and it sparked a nice conversation about privacy. He has no technical background but managed to self-host it on his old laptop with one of those distros that have an easy UI for self-hosting (don’t remember which one exactly). He’s a pretty cool guy.
Proxmox or Unraid?
I clean construction site toilets. I wanted to run my own game and media severs and ended up with a Dell Poweredge, a synology 1u NAS and some ubiquity gear
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DNS Domain Name Service/System NAS Network-Attached Storage NUC Next Unit of Computing brand of Intel small computers Plex Brand of media server package RPi Raspberry Pi brand of SBC SBC Single-Board Computer VPN Virtual Private Network
7 acronyms in this thread; the most compressed thread commented on today has 4 acronyms.
[Thread #944 for this sub, first seen 31st Aug 2024, 22:05] [FAQ] [Full list] [Contact] [Source code]
I have no formal IT education. But I grew up on computers when command line was how you got things done.
Warehouse worker who self hosts stuff here.
It all started when I was a teenager and I lost access to my photobucket account…
My father in law was a commercial pilot and he had a home server just to keep photos and travel writing while he was flying and away from home a lot. I helped him upgrade some of that to the cloud, since that makes for sense when on the other side of the country, but he still has a bunch of stuff at home.
I work in retail, but my homelab isn’t super extensive just a nas, a Plex server, and a couple proxmox boxes.
Closet I’ve ever come to being in IT was back when I was still in college and took some a networking class and some web development classes but that was many moons ago.
Mechanical engineer here self-hosting my own Lemmy and Pixelfed instances in a Yunohost VM on an old Ubuntu box. It just feels better being my own admin.
Kudos for self-hosting fediverse stuff, man.
Thank you!
Former USAF JAG here (lawyer). I was always a tech geek, undergrad major was in MIS actually, but I didn’t enjoy coding. Always ran Plex on the side, built my own computers, etc. Grew up with my Dad using Linux everywhere (I found this annoying as I just wanted to play games on Windows).
I didn’t enjoy law (surprise!). I was disillusioned with the criminal justice system too. Quit the law in 2020. Then suddenly had quality time by global happenstance to rethink my life path.
I work in IT now. Restarted at the bottom of a new career but I’m in deep nerd territory now - Proxmox servers, Home Assistant, networks with VLANs, OPNsense router, 22U server rack, Linux as my daily driver, etc.
Much happier now.
As someone who majored in CS and is now in a software engineering position, the people in tech who come from a completely different field are always my favorite. On top of just proving people wrong about the “right” way to get into the field, they’ve been around, they know how to think about problems from other perspectives, and they’re usually better at working with other people.
Honestly, I think more people should minor in CS, or if they did their undergrad in CS, they should have to do their grad work in something else. The ability to compute things is only useful if you’re well versed in a problem worth computing an answer to, most of which lie outside of CS.
I’m currently doing comp sci but have always debated doing comp eng or ee. However, I don’t want to do comp eng or ee as a career, just more as a side hobby. So I’m sticking with comp sci and I’ll do all the comp eng and ee stuff at home.
I think you need to be at least somewhat technical
You don’t have to have a technical background though. Anyone from any background could learn it if they wanted too. A technical background obviously helps though.
