this post was submitted on 03 May 2024
21 points (74.4% liked)

Selfhosted

40198 readers
780 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 in the process of setting up a home server, and I am struggling to decide. I have previously used yunohost but in the meantime, freedom box has matured quite a bit. I have also looked at Tipi.

The use case right now is, running a wireguard server and probably some notes of sorts (to be decided). A web GUI for management and updating would be much desired.

Disclaimer: I don't have too much surplus of energy, due to a hectic life, so I would prefer something easy and without the requirement of docker/kubernettes

I will run on a Gigabyte Brix with:

  • AMD Ryzen 4300U (4 core)
  • 16 maybe 32 GB RAM
  • 512GB SSD

I am open to other suggestions.

P.S. I apologise if this has been debated before, but I have not really found anything.

Thank you in advance

EDIT: I have read your recommendations and arguments, and it is noted, I am watching docker tutorials now :)

you are viewing a single comment's thread
view the rest of the comments
[–] chiisana@lemmy.chiisana.net 4 points 6 months ago (1 children)

If you’re feeling that it will take too much time to maintain something you’re deploying, then there may also be toolset/skillset mismatch. Take Docker/K8s that you’ve called out for example; they’re the graduated steps to deploy things in the industry. Things deployed via Docker drastically reduces the amount of time to get up and running by eliminating large swaths of dependency management, as well as gives option to use tools on platform to manage self updates if that’s something desired (though this could potentially introduce failures by manual upgrade steps where required). You’d graduate to k8s as your infrastructure footprints start to grow. Learning the correct tools could potentially reduce the barrier to entry and time requirements on the apps front.

Having said that, it is probably better to ask the inverse: what is it that you’re trying to achieve and why?

Without a reason that resonates well with you, you’re not going to find time in your allegedly already life to maintain to keep it working. Nor will you be willing to find the time to learn the correct tools to deploy these things.

[–] Antaeus@lemmy.world 1 points 6 months ago

Thank you for your input. I work in IT as a support specialist consultant, and have dabbled quite a bit with technologies. I run linux as my primary operating system at home. Your insinuation of a mismatch might sound apt, but the wider picture is that there a some reason to my madness. However, the "push back" again my "no docker please" has been noted, and I will take a closer look at it, and see if I can't make myself understand the basics. Thank you!