Is there an idiots guide to self hosting?
Or maybe a two click solution? :)
Or maybe a two click solution? :)
tl;dr:
Go to search.brave.com
Search for "docker cheat sheet"
Check the first two links, write down whatever that is in there
Then search "How to install docker on (Your current OS)"
Click on whatever link appears first, blindly follow the step by step
Then search "Best things to self-host"
Check the first two links, see if something tickles your fancy
Then search for "How to install (ticklyfancy stuff) on docker"
Once again, blindly follow the step by step
Congrats! You are now a pro docker user.
Self hosting what?
In general
It's so easy to self host these days. I remember when you'd have to fuck around with Apache configs and fuck around with app config files etc. Now you just run docker. It's so great these days!
I'm still fucking with the apache configs (I fucking hate apache...). As someone with no docker experience whatsoever, are there any getting started guides you would recommend for someone looking to make the switch?
Oh, and different libraries, and compiling software to get the features you need, and the pain of moving something from one server to another because there was some unique weird environment setup needed on the host just to get it running.
And these days, just docker the shit out of everything.
Oh, those were the days :D Apache + PHP + MySQL. Then multiple hosted software on that same server. You were screwed when one app needed newer PHP and some other stuff didn't run with new PHP.
haha yeah. Those were the days. Kids these days have it easy. Did I mention "Get off my lawn!"?
docker-compose helped me wrap my head around docker. I can use run commands now, but prefer to either modify a compose file or create my own to spin things up.
Same here. I kept using the docker run commands that usually show up in Docker hub but started making my own compose files. So much cleaner feeling. I can keep everything all nice and neat in a single folder now. Makes backing up much easier too.
Running stacks is easier too. My entire media stack minus Plex is all in the same compose file. Need to change anything, just edit the docker-compose and up -d
Yep, this is what I do with my "media acquisition" stuff. I have Jackett, Sonarr, Radarr, Transmission all run from a single compose file.
I might add that don't just mindlessly copy-paste things. Try to understand what those commands do and why they are needed.
Okay. I keep reading about docker. What's the difference between a docker and just installing an app on rented server space?
Does each dock (?) have its own server? (Apache or nginx or whatever?)
Does each dock host a whole site, or do you have a dock for your database and a dock for your web app?
Docker is basically a virtual machine image you write your software in. Then when you run the software you don’t need to worry about compatibility or having the right dependencies installed, it’s all included in the docker image.
Think of Docker as being Nintendo cartridges that you can take to any friends house, plug them in, and play. Servers can run more than one Docker container.
The approach greatly simplifies writing code and having it work on your server, reduces errors, and adds a layer of security.
I've read and reread, listened and relistened to info on docker/containers and I still feel like I'm missing something tbh.
Let's say you have a docker container for something and it's for a Linux distro, that won't run on another OS, will it? Maybe not even a different Linux distro from the one it was made for (e.g. Ubuntu or Arch or Fedora or whatever).
To go off your example, Docker's not like an expansion module to make your Switch games work on a PlayStation or Xbox...Right? There seems to be some kind of mixed messaging on this, the way they're so readily recommended (which seems to be related to a presumption of familiarity that often isn't there toward those inquiring).
I guess I've also been confused because like...Shouldn't old installers handle bundling or pulling relevant dependencies as they're run? I'd imagine that's where containers' security benefits come into play though, alongside being virtualized processes if I'm not mistaken.
For simplicity its easiest to imagine it as a simulator or emulator. Its not trying to be your machine (called the host machine) pretend it doesn't actually use your os, or software.
Imagine each container is a fresh new machine on your desk with a blank hard drive. The image is basically the result of a set of instructions (a Dockerfile) that docker follows to install all the stuff you need to get the machine running.
Normally it starts by installing an os like alpine Linux (alpine publish this docker image and you simply build on top of that)
Then you install any extra utilities and software you might need to run the programming, maybe python or Java (again there are images themselves based on alpine managed and updated by official sources)
Finally you install what you want and tell the computer that's what to run when it boots up (often the software you want to run gives an official docker image which has done all this for you)
So when you run a docker image its actually done all this setup for you already and just stored the resultsin a way that it can apply it straight to your shiny new container in an instant and be ready.
Docker compose is instructions on how to set up a bunch of computers with a network.
What's the difference between a docker and just installing an app on rented server space?
Functionally? Not much. But people who selfhost typically want everything on computers they own. Whether it's for learning purposes, or to not have their stuff on "someone else's computer" selfhosting usually means you're running software on computers you own, almost always within your own house.
Does each dock (?) have its own server? (Apache or nginx or whatever?)
Each docker image usually has a web server built in. The philosophy of docker is that it contains everything needed to run the app. Even a small linux OS (LibELEC or Alpine are favorites for docker images). So while you're not managing the web server in a docker image each docker image will have its own web server if web access is needed
Does each dock host a whole site, or do you have a dock for your database and a dock for your web app?
Docker the program is what runs all the docker images on a computer. Each docker image is built as per the software's developer. Some docker images will have a web app and a database combined into a single image, while others will expect a separate database server running independent of the image (It won't care if the database server is a docker image or not; just that it has access)
I think you should just choose whatever software or project you want to selfhost, read how to do it, and learn by doing.
I'm a complete idiot but I learned how to self host from trying to set up a Jellyfin server on my Windows desktop. Now I host game servers, Matrix with bridges, Discord bots, and this Lemmy instance that I'm in. I (re)learned how to use Linux and fell in love with it too.
It's all about reading the manual I guess.
This is how I got a career in Software Engineering, literally had a strong motivation to build a clan website for my Counter-Strike 1.6 crew and I just ended up learning by maintaining self-hosted websites, forums, and voip. Kept doing it over and over by building other projects and then realized people pay for this skill...
Depends on what you want to self-host. In general, I would advise against self-hosting anything before you familiarise yourself with the basics of *nix, networking and cyber security.
You at least need to know enough to make sure that whatever you host is only available within your local network and is inaccessible from the outside.
Once that’s ensured, go nuts, experiment, learn, evolve.
In terms of how to start, really depends on your budget, what hardware you can spare, how much space you have at your place etc.
For the most basic playground it’s enough to have a raspberry pi or similar, or a very old laptop / desktop computer.
For something more swanky you can get old Dell servers (e.g. R420) online for around 100$ or so. They are quite power hungry though. Or you can get yourself a NUC and use that.
If all of this sounds like too much work, just get yourself QNAP / Synology NAS and see what it can do for you (it is way more limited in terms of options, but easier to setup and you can still have your Plex / file sharing / docker containers).
Instead of a Raspberry Pi you can look into used/refurbished Thin Clients which are way cheaper than a Pi at the moment.
I would strongly recommend to start experimenting in your local network too and not rent a VPS in the internet. There is a very high risk it will end up in someones botnet, if you don't know what you're doing. For your local network, make sure to not forward any ports from the internet into your LAN and disable UPnP and the like. After that you should be pretty safe from direct attacks from the internet.
For more detailed tips you should tell, what you want to self host. Start small and learn along the way.
I would like to self host a lemmy instance.
I know enough to have setup an ubuntu server with docker containers and servers on my local network, but except a minecraft server never exposed any kind of server to the web.
https://www.youtube.com/c/SpaceinvaderOne
This guy got me from 0 to having a bunch of useful internet facing services.
You could go through the following route:
If you don't have the means to get new hardware, you can use hyper-v or virtualbox for free on Windows or virtualbox/virt-manager on Linux on existing hardware.
Simple project to start with: install pihole and configure it as your DNS adblocking filter at home
While doing things like these, keep notes what you do by day, using those notes, put together your own howto manuals. Do not be afraid to fail, sleep over it and try again, don't be afraid to ask specific questions here or on other forums, IRC.
I think Unraid is a good place to start. Have a look through SpaceInvader One's channel and IBRACORP'S channel.
I am currently using yunohost.
I report that it works out of the box within the local network.
currently struggling to make use of zerotier to do that.
all the DNS stuff is like magic for me.
Did you take the route via a fixed IP and a bought domain?
Yunohost provides free domains (nohost.me, ynh.fr or noho.st) with Dynamic DNS, but i bought domain in Gandi. I use this simple script https://github.com/cichy1173/yunoDnsUpdater to update DNS if IP changes. I am thinking about buying fixed IP, but it is additional cost every month.
yes I know about the domains but port forwarding at my router is yet to be impossible for me. also I am unsure if I am ready to open my network to the outside yet.
do you rely on the built in safety measures or do you have additional security measures implemented?
Yunohost provides good set of tools to secure home server (Fail2Ban). Additionally, I use SSH on different port and with pubkey authentication. My Nextcloud instance uses geoblocker and 2FA. I am waiting for 2FA for Yunohost SSO (it should be added in Yunohost 11.x) It is good to not make all apps available in open way. I have some of them hidden with Yunohost SSO system. I do not host apps, that can be used anonymously, for example copy-paste tools or Nitter.
Not all routers provided by ISP support port forwarding. It can be locked for you. If you have normal IP address (even dynamic) you should be able to open this ports. My friend had to call his ISP and ask for opening the ports. Another way is to buy second router and use first router in bridge mode (which I do, because I started using OpenWrt).
yes kind of an alternative.
but i think it is even more since it also takes care about proxies, domains and everything gives you a nice UI for all and gives you implemented packages.
In some way yes, but Docker is containerization engine, which can be used to selfhost stuff. Yunohost is special OS for selfhosting and only selfhosting. Apps installed using Yunohost are not containerized, and they are made for easy deployment.
What would be the point of self hosting then?
Generally speaking installing stuff on a raspberry pi with docker and accessing it over a vpn is pretty safe and already straightforward.
Hmm maybe Unraid with the community store? When you got unraid running its just a matter of selecting an app from the store and hop: it runs. Kinda..
If I remember correctly, Yunohost does something similar, and it's fairly easy to setup. Anyone with experience who can say something more about it?
I initially bought a Raspberry Pi with an HDD attached to set up a NAS.
I watched this YouTube channel for a lot of info when I was getting started: https://www.youtube.com/c/TechnoDadLife
I got started (with minimal knowledge and a love for tinkering) by installing proxmox on an old computer (i3 with 8gb of ram) and then using Proxmox Helper scripts https://tteck.github.io/Proxmox/. I run home assistant in a vm within proxomox and have a docker instance running in a container in proxmox. It's all been fairly easy so far, although I'm not sure I'd call it a one- or two- click solution. I got started from the home assitant community, and I'm new to the self hosted community, so I may do things a little differently from others around here.
If, you use kubernetes, I can give you manifests to make it basically a two click install.
