this post was submitted on 29 Aug 2023
25 points (63.4% liked)

Selfhosted

39158 readers
408 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
25
submitted 1 year ago* (last edited 1 year ago) by LazerDickMcCheese to c/[email protected]
 

I got Jellyfin up and running, it's 10/10. I love this thing, and it reinvigorated my love for watching movies. So I decided to tackle all the other services I wanted, starting with Paperless-ngx...

What a nightmare. It doesn't have a Windows install so I made an Ubuntu VM. Don't get me started on Ubuntu. I just spent about 12hrs trying to get Portainer to cooperate and had to give up. I tried just installing Paperless the "normal way" and had to give up on that too.

My point: if you're getting started selfhosting you have to embrace and accept the self-inflicted punishment. Good luck everybody, I don't know if I can keep choosing to get disappointed.

Edit: good news! Almost everything I wanted to do is covered by Jellyfin which can be done in Windows.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 1 year ago (1 children)

I thought this too, I hated docker because it was supposed to be the solution of "works on my machine" and the only thing that did for me was force me to learn more configurations besides the configuration of the service you wanted to install.
And as you said, plus the hassle of having to run some Linux distro.
But little by little I had to get deeper into docker and Linux, mainly because of my work, and now I can easily deploy any service in the VPS I have or test it with WSL. I even started dockerizing some of my own flows like building and deploying my own projects with docker.

Believe me, it's worth all the time to learn docker and linux.
Start small, few lines or keywords each day, you won't have everything you want to deploy in a day or two if you don't already know all the technologies.
And remember, if you don't easily find something you can always come to ask in a post and we can try to help you!