Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
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.
-
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:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
The best thing I did was probably set up Obsidian Live Sync after hearing about it in selfh.st weekly. Compared to the Syncthing setup I had before it is so much quicker, much easier to catch sync errors, and won't drain my damn phone battery as much! The more things I can move away from Syncthing the better so I will probably be looking at Immich for my photos soon as well.
On the management side, I've had my Docker stacks split across Dockhand and Komodo ever since a poorly executed move away from Dockge a few months ago. I finally thought about it and had the time to decide to give up on them both. I like some of the concepts of compose in a git repo and the fancier interfaces, but I just realised it was all over the top for what I need. I missed being able to simply SSH into a damn machine and
docker compose up -din an emergency. Compared to the constant deploy errors of Dockhand and the potential of scrounging application databases for in-DB compose data or attempting to deploy stacks from forgejo when forgejo itself is a stack deployed via git... going back to basic files is a blessing. Lesson learned!What that culminated in is all my stacks are now in Sencho (which clearly uses a lot of AI code sadly), but it was that or Dockge and I knew Dockge lacked a few things I wanted. The nice thing about Sencho (and Dockge) is that I don't need either of them because they are based around file-on-disk simple operation. I can cut it out of my setup entirely at any moment and not shed a tear. So much peace of mind leaving Dockhand. Now I just need to find a builder image or write a script to replace Komodo's build feature because I don't want to keep using it.