Selfhosted

39435 readers

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

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

What should I run and why? (lemmy.world)

submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]

32 comments fedilink hide all child comments

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

[–] [email protected] 5 points 6 months ago (2 children)

I was trying to stick to technologies that I know and that I am comfortable with.

I have watched some docker tutorials, and it just seems more complicated to me. All tutorials requires a terminal and I am trying to avoid having to having an open port 22.

So, that's the main reasons.

[–] [email protected] 7 points 6 months ago* (last edited 6 months ago)

It’s a fair response. Some uf us aren’t flush with time.

I’d survive SSH for installing Portainer and then you can run most of it from its GUI. If you use Docker Compose it will be super easy to make changes to your setup as well. Just change the file and redeploy your badboys.

I’m a recent dad absolutely strapped for time, but I still managed to set up a headless Debian server with close to zero Linux knowledge. There are so many amazing guides out there, especially on GitHub.

Good luck whatever you go for.

[–] [email protected] 4 points 6 months ago

You can use any port for SSH—or you can use something like Cockpit with a browser-based terminal instead of SSH.