this post was submitted on 26 Jun 2023
6 points (100.0% liked)

Selfhosted

40211 readers
1643 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I am interested in tech and would say I have more knowledge about networking than the average person, but there's still a lot that's way above my head. I've played around with Pis a little and have set up things like home assistant and foundry VTT before.

I got my hands on an old machine from work and want to upgrade it with some of my spare hardware, and ideally have it set up as my single home server. I would like to host plex, a few foundry servers, home assistant, and use it as a NAS. Basically combine everything I have right now into one more powerful machine.

Thing is... It feels really overwhelming to try and start. I'm not sure really sure how to go about the whole endeavor. What OS do I use? Do I use VMs, docker containers, is there pro or cons one way or the other? How can I make sure they're all accessible from the web securely?

Is there anything you guys can tell me to get me started? Some resources to walk me along setting a multipurpose home server?

top 7 comments
sorted by: hot top controversial new old
[–] snekerpimp@lemmy.world 2 points 1 year ago

Personally, after I graduated from pis I went to proxmox, for the simple reason of if I wanted to experiment with anything I could just spin up a new VM and test it out. Everything I have running in my lab is a VM. The only thing I run bare metal is opnsense, truenas and one pi.

Don’t be afraid to nuke everything and start again. Also make sure you take notes on what you do, what sites you visit, code you copy and paste. Obsidian and SilverBullet have been a godsend when it come to learning from my own mistakes.

[–] rambos@lemmy.world 2 points 1 year ago

I was on the same boat few months ago. Went for Debian OS and then docker containers for almost all services. Portainer is awesome web UI to manage all containers so thats what I install first. Starting up new services is about copy paste docker-compose with slight modifications for your needs. My server is accessible through wireguard connection and that should be one of the most secure ways and probably the easiest to setup afaik (downside of wireguard is that you have to setup each device to allow connection - AKA scanning qr code)

Just saying what I did, most people here are more experienced and Im still learning.

GL and HF

[–] Onion6068@feddit.de 1 points 1 year ago* (last edited 1 year ago)

This depends on the machine you have.

I would choose a hypervisor, if I had plenty of RAM (32 GB+) and CPU and wanted to have everything properly separated with the option to easily redo things, backup VMs and container, experiment with different setups and also wanted to learn new things. There are plenty of options. Proxmox might be the easiest to get started with and also to get help from the selfhosted community.

If I had limited resources, I would just use docker/docker-compose directly. It is more commonly used than lxc and doesn't have the overhead of a VM.

Regarding safe and secure access: This is a rabbit hole.

I personally don't use cloudflare, a lot of people do. Use a reverse proxy and generate a ssl certificate for all domains used. (Traefik, caddy, npm et cetera). Try to keep services up to date. Separate networks from each other. Think about which services you really have to expose publicly.

[–] poVoq@slrpnk.net 1 points 1 year ago

You could use a complete solution like TrueNAS or https://www.openmediavault.org/ but IMHO if learning is equally a goal you could also start with a standard Debian or Fedora Server Edition. Personally I use the latter and it is very nice to use with the Cockpit web-console and the good integration with Podman for running Docker containers.

[–] Tiritibambix@lemmy.ml 1 points 1 year ago

I feel you. I was where you are 2 years ago and it was really hard to start off.

I'd suggest starting installing Debian as an OS. Then, go for Docker.

If you feel lost, you can take a look at some videos from DBTech on YouTube. Look at his playlists to sort what you need.

Remember to document everything you do, because you'll forget what you did to make things work your way.

Have fun !

[–] spaghetti_carbanana@krabb.org 0 points 1 year ago (1 children)

Oh and by the way, it’s easy to feel overwhelmed starting out in this. My advice is to set yourself small, achievable goals to help break it up. Start by doing your hardware upgrade, then work out what your host OS will be and install it. Then work out how you want to use it, what you want to containerise, what you want to run in VMs.

be prepared to knock it all over and start again. Everyone rebuilds their environment, usually after learning how they could do it better. And most of all, have fun!

[–] iAmTheTot@kbin.social 2 points 1 year ago

be prepared to knock it all over and start again.

Definitely used to this already just messing around with my few Pis lol.