this post was submitted on 30 Dec 2024
54 points (93.5% liked)

Selfhosted

60789 readers
299 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I was wondering about the pros and cons about self hosting your services via Yunohost. I currently have all my services hosted in docker containers on a Debian homeserver. As I was planning on a fresh install, setting up an Ansible script to simplify backup & restoring and bake in a centralized user management system (currently I annoyingly have separate passwords for each service for my 5 users).

Now I was wondering if I could get some experience reports from Yunohost users. What are the problems you faced? Are you satisfied? Are there so many services you couldn't find that you rather went the selfhosted way and integrate Authelia or a similar service? Any ideas and feedback is welcome that can help make up my mind.

you are viewing a single comment's thread
view the rest of the comments
[–] danceswithcats@lemmy.ml 1 points 2 years ago* (last edited 2 years ago) (2 children)

Point three: not true. My blog is TLD. With nonpublic services, which a lot of private server functions are, what's the problem with a subdomain?

Most Google services are reached through subdomains, aren't they? They certainly were when I was forced to use them.

[–] Ulrich@feddit.org 1 points 2 years ago

Point three: not true

Yes it is

My blog is TLD

I didn't say every service was this way

what's the problem with a subdomain?

Nothing. The problem is when they make you use both.

[–] danceswithcats@lemmy.ml 1 points 2 years ago (1 children)

Also, you can run as many TLDs on a yunost instance as you can afford and your machinery can stand. I've got two IP addresses on mine: one for front end apps and one for backend.

[–] Ulrich@feddit.org 1 points 2 years ago (1 children)
[–] danceswithcats@lemmy.ml 1 points 2 years ago (2 children)

Yes. Hence:

you can run as many TLDs on a yunost instance as you can afford and your machinery can stand.<

And Docker will somehow magically free one from the cost, will it? How will hating on a free and open source project that has put self-hosting within reach of thousands of people address the costs of computing?

[–] Ulrich@feddit.org 1 points 2 years ago* (last edited 2 years ago)

Hence it is not a reasonable solution.

No one's hating on anything. If you actually read my comment I expressed precisely the opposite, while answering OPs question.

[–] danceswithcats@lemmy.ml 0 points 2 years ago

Actually, don't bother. I don't care.