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

Selfhosted

40882 readers
543 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 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
54
Experience with Yunohost (yunohost.org)
submitted 5 days ago by [email protected] to c/[email protected]
30 comments fedilink hide all child comments
 

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
[–] [email protected] 1 points 4 days ago* (last edited 4 days 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.

[–] [email protected] 1 points 4 days 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.

[–] [email protected] 1 points 4 days 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.

[–] [email protected] 1 points 4 days ago (1 children)

All those TLDs cost money

[–] [email protected] 1 points 4 days 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?

[–] [email protected] 1 points 4 days ago* (last edited 4 days 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.

[–] [email protected] 0 points 4 days ago

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