this post was submitted on 30 Dec 2024
42 points (97.7% liked)

Selfhosted

40938 readers
316 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]
42
Experience with Yunohost (yunohost.org)
submitted 1 week ago by [email protected] to c/[email protected]
20 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] 2 points 1 week ago (2 children)
  1. Unable to host apps without exposing them to the web
  2. Despite a simplified GUI, a lot of the system is still dependent on CLI
  3. they make you use subdomains and / as well. Like blog.website.com/blog
  4. Outdated apps (some much more than others)
  5. Poor/no support when something goes wrong
  6. An entire Debian generation behind (not sure if that one matters but it is weird)
  7. Can't run multiple of the same service

I've tried them all and it's overall the best but still has a whole lot of room for improvement

[–] [email protected] 2 points 1 week ago (1 children)

Some of these points are inaccurate. Numbers 3 and 7 are definitely dependent on the app in question. I also rarely have to do anything in CLI, a recent update moved an issue I had with LE certs from the CLI to the web admin. As far as support, the forum can be inconsistent and the XMPP chat is more responsive. Dev team is in France though, so timezone can cause delays.

[–] [email protected] 2 points 1 week ago (1 children)

Some of these points are inaccurate.

...any specific ones?

the XMPP chat is more responsive

I didn't even know there was an XMPP chat, but any chat seems like an awful way to get support...

timezone can cause delays

We're not talking about hours here, we're talking about days/weeks or months.

[–] [email protected] 1 points 1 week ago (1 children)

I specified the ones in my comment. I like chat support, but I understand it's not everyone's preference. I don't doubt your experience, just providing mine.

[–] [email protected] 0 points 1 week ago (1 children)

Nothing in your comment would make mine "inaccurate".

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

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.