106
submitted 1 month ago by erev@lemmy.world to c/selfhosted@lemmy.world

I've been around selfhosting most of my life and have seen a variety of different setups and reasons for selfhosting. For myself, I don't really self host as mant services for myself as I do infrastructure. I like to build out the things that are usually invisible to people. I host some stuff that's relatively visible, but most of my time is spent building an over engineered backbone for all the services I could theoretically host. For instance, full domain authentication and oversight with kerberized network storage, and both internal and public DNS.

The actual services I host? Mail and vaultwarden, with a few (i.e. < 3) more to come.

I absolutely do not need the level of infrastructure I need, but I honestly prefer that to the majority of possible things I could host. That's the fun stuff to me; the meat and potatoes. But I know some people do focus more on the actual useful services they can host, or on achieving specific things with their self hosting. What types of things do you host and why?

you are viewing a single comment's thread
view the rest of the comments
[-] earth_walker@lemmy.world 18 points 1 month ago

I self host jellyfin, nextcloud, owncast, tandoor, komga, photoprism and searxng. I use nginx proxy manager for a reverse proxy and SSL cert automation. Works great for me but I would like to get into traefik sometime.

I self host for privacy reasons, also it's fun, it's a learning opportunity and sometimes self-hosted services are functionally better than the other options out there.

[-] zingo@lemmy.ca 3 points 1 month ago

I use nginx proxy manager for a reverse proxy and SSL cert automation. Works great for me but I would like to get into traefik sometime.

I got tired of the NPM and went to traefik for 2 reasons.

  1. NPM kept locking me out of my account (admin), like 4 times during the time I was using it. That meant that it was not reliable enough for daily use.

  2. From what I heard is that the NPM project only has 1 developer and so they can't really respond and fix security flaws in a proper timeframe.

I'm using traefik now for internal traffic while VPN in if I need internal services while out and about.

Jim's Garage has a great YouTube video on setting it up.

[-] infeeeee@lemm.ee 2 points 1 month ago

From what I heard is that the NPM project only has 1 developer and so they can’t really respond and fix security flaws in a proper timeframe.

It's mostly just nginx with a webui. You can even see the nginx config files if you bash into the container. It has the same bugs as upstream nginx. Do not expose the management port to the internet.

Plus compared to normal nginx, it's harder to misconfigure it. Most of my services are just the default config, so I can't mess it up accidentally.

About lockouts: Once also happened me, but that was just a messed up update, next update fixed itself. If you lock yourself out you can usually edit the db directly, it defaults to sqlite, but I used it with mariadb.

[-] earth_walker@lemmy.world 1 points 1 month ago

How did you set up a VPN to securely connect to your services over the internet? I have looked for guides to do this and haven't had much luck. I would really like to implement this in my setup.

[-] zingo@lemmy.ca 2 points 1 month ago* (last edited 1 month ago)

I can once again refer to Jim's Garages video about setting up wireguard on Docker. Very easy.

Wg-easy, with a nice interface.

[-] earth_walker@lemmy.world 1 points 1 month ago

Thank you, I wasn't sure if that video was re: Traefik or VPN. I appreciate the suggestion.

this post was submitted on 15 Jul 2024
106 points (97.3% liked)

Selfhosted

39143 readers
389 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