I recently got into the world of self-hosting, and although I’m doing it through a VPS I’ve learned many interesting things, even so, I’ve only had my VPS contracted for 10 days, and of those 10 days, 8 I spent burning my head learning concepts that I had never heard or understood, and actually it’s funny because I remember that’s what it was like to learn to use Linux.
To begin with, I started with Ubuntu 22.04 and docker, in some situations installing the service was simple, running a command in my console and opening a browser in localhost and the port used, simple, but as I was installing services I found some that they simply exceeded my patience and knowledge, as was Peertube where I simply do not understand why I need to put a name and a password to a thousand different databases, and many times they use concepts like <SECRET KEY> I don’t have the slightest idea what it means.
And so, I came across Yunohost, who makes the selfhosting process miserably easy, but so easy it honestly makes me feel dirty, to the point that I remember dualbooting Windows simply out of fear of Linux.
Now, I have 100% intentions to learn all those concepts that I don’t know and manage my servers on my own and it’s not that I’m “afraid” to do things on my own, but I need a stable server where I can have my services hosted, I can’t create a docker instance to realize the following week that I restart the server to update that I forgot to point to a persistent volume and I lost all my data, which didn’t happen to me but it was possible because in the end I do this for hobby and I’m experimenting.
And I don’t know, I don’t feel exactly “good” with Yunohost, I mean, it works great but what if for example I want to host something that is not in their list of supported services? I basically screwed myself. I feel like I’m in the same situation where I dualbooted Windows just for fear of Linux.
Edit: Thank you all for commenting! I am not answering them one by one because it would take me too long, but I want to clarify that I do read the messages and I agree with most of the comments, if not all! Although yes, I won’t keep burning my head over it, while my VPS works, I’ll learn everything I can virtualizing on my own PC.
Holly crap that looks amazing. I just installed Ubuntu server and got paperless working, but I think I’m gonna redo it with yunohost. Thanks for the lead!
Ok that didn’t work, back to unbuntu…
If it works for you and allows you to start learning, there’s no problem with it. Too many people seem to think that if you haven’t compiled whatever yourself, it’s not true “self hosting” but you should do what works best for you to get to the goal you want.
You’re absolutely right! It is still participating in the hobby. It’s not as immersive in it but it’s participation nevertheless. I do like to encourage people to make things more challenging to increase their levels of learning and satisfaction though.
I’ve never used Yunohost, but I’ve tried many other ways of self hosting. From barebones Linux machine to using truenas now.
Proxmox and truenas are the best I’ve used. Proxmox and the LXC containers are just so very cool :) But I did end using truenas, simply because of truecharts.
I don’t want to spend forever installing something new, so using a shortcut is pretty cool and nothing wrong with that if it works 💪
Yunohost is, to me anyways, a good stepping stone in learning the hosting side of things. You can have something up and running while you learn the rest.
I don’t think you should feel bad about it, everyone needs some kind of “training wheels” or “guard rails” when they’re first getting in to any hobby.
I think of it in terms of my other hobbies, would I have started off in electronics repair if I had to fix a modern motherboard for my first project? Maybe, but I would have struggled mightily. Instead I started doing simpler circuits and worked my way up while learning theory and technique.
Yunohost is awesome, if only for the dyndns. I try to host most of the stuff in docker but dyndns never quite worked for me unless it was the yunohost one.
Youre good. Self hosting is what you define it as. No one elses opinion of it matters.
I run a combo of homelab apps and vps apps.
All that matters is if it works for you
Do what you want. Everyone started somewhere. If yunohost is yours then so be it. If you like it, stick to it. If you grow tired of it, move on.
Bro, just chill and enjoy. Use what works for you. If you ever want to leave your comfort zone there are thousand options to still keep it simple.
Firstly, you are to praised for wanting to learn as many today only want to learn what is pertinent to making money and not learning for the pure good that it does. Secondly, you should not feel bad about using Yunohost. Everyone needs to start somewhere and everyone was once a newbie. Have you given any thought to purchasing a laptop or desktop on the used marketplace to use as machine to learn Linux on? I highly recommend people go that route. A Lenovo T430 - 450 can usually be had for about 130-160 dollars. This will help making learning an all-in experience. I found that being immersed in the world of Unix-like operating systems was essential for my own learning. I am self-taught when it comes to Linux and the BSDs. The best system admins know that in the Unix world you’re constantly learned. The kernel and tools that comprise the operating system are many and rather vast.
Let me ask you this: What is your goal in self-hosting? Think about why it is that you want to do it and work on one service at a time. I self-host my own Mastodon and Lemmy services in docker containers on an Arch Linux box in my home. Do they have 100% uptime? Um, yeah no, because it is a learning environment and in learning you have to permit yourself to make mistakes. The learning lab environment is one that will teach you to carefully plan updates, server migrations, server hardware upgrades, etc. It teaches you the non-technical side of things like planning.
I have also seen a lot of folks try to run before they have learned to walk and want to zoom right to technical complexities of self-hosting. Please take the time to learn Linux and start with the basics. Become comfortable with the command line and the troubleshooting tools that are available to you. By learning the basics and progressing towards your goal steadily, you will find yourself less frustrated and the learning experience more enjoyable and personally valuable.
I swear you will never, ever be satisfied with anything you do with your mindset. Just chill. It’s a hobby. There is no right way to do it.
There are bazilion things to learn and not enough time. You can’t expect to do everything what enterprise level sysadmins do with big money to spend or, for that matter, to do something that seems like everyone’s doing. We do what we can.
One day you start with Ubuntu and then you hear all the crap about it and you use Debian. It’s all fine but then you use Alma/RockyLinux because that’s what real servers are using. And then you set up 30TB of zfs storage for what, 20-30gb worth of some family photos. You learn shell and python to automate simple things but everyone’s using Rust now so you have to use Rust because python is a slow crap. You want fancy website? How about learning JS, TS, React, Vue, Angular, Svelte? Why stop there? Learn Node/deno. Are you into home automation? Learn how to solder things to Arduino. Why are you not using Proxmox? Learn how to use that too. Do you even firewall? Learn pfSense. Docker’s nice but real servers use K8. Learn that too.
Next thing you know you now own a whole rack of machine that costs more than what most of the small companies have and an imposter syndrome.
Have fun. This rabbithole is sure fun but you will never catch up everything.
So true. I’ve done most of the things you list lol
I was just pondering upgrading my current ‘old-computer’ server, but it suits my needs right now and and upgrading would only serve to increase the % available numbers of the hardware.
It is a really deep rabbit hole, but you’re right, self control is necessary.
Its all good, I use yunohost as well and have a second server for the stuff that arent on their list like minecraft server for example, if you want to host something that isnt on their list, you can set up a second server on raspberry for example and play with reverse proxy.
Nah fuck that, work smarter not harder
Working smarter is in understanding how your computer, systems, and services work. Yunohost is good for getting started and wading the waters of doing it yourself. The real fun and satisfaction in the hobby is putting in the hard work, learning, and growing smarter for it.
Don’t let elitism ruin the adventure for you. Enjoy your success while you take time to learn other crap.
I spent days trying to go from 0-100 figuring out the technical stuff and was making myself very stressed out and upset. I decided to just go to Yunohost and it just made things dead simple and in retrospect, enjoyable.
When I’m ready to learn I’ll spin up a new server and try to implement the same services the “hard” way, but for now I’ll continue to enjoy all the benefits of self hosted with a dead simple solution for implementing it. Don’t let e-peens get you down.
If you want to really use your server, yunohost might even be good for you. because other people help harden the configs and prepare updates… you can even participate on their github or forum if you want to have a look at how things work. but they don’t use docker.
btw: yunohost is based on debian. so if you’re missing some software… you can just install docker and install your software. or create a new user account for it. or use some other container engine or virtualization tech. it’s all there. you might want to have a look at their ‘redirect’ app. It can do reverse proxy. I use it for exactly that, to reverse proxy into my containers with ‘extra’ software.
As other people pointed out: You don’t always have to start at zero and learn everything. it’s okay to sometimes start with something working and see how they did it. maybe disassemble and reassemble parts and try to contribute. there is no need to feel ‘dirty’ because of that.
If there’s an automated set up, absolutely go for it, you shouldn’t be doing the same mundane task over and over again. I, however, recommend at least once to do it yourself/go over the docs just to understand how to troubleshoot when stuff breaks or if it interests you how the software works. For example: A lot of people think that Watchtower queries the docker repo to see when it was last updated and that’s how it processes it’s updates. The truth is, watchtower downloads the entire image, checks it against your currently used image and if it’s not the same it updates. What then happens is that server maintainers set the poll interval really low (like 10-15m) and end up using a lot of bandwidth.
