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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 30 days old, your post is exempt from this rule as long as you continue to engage in comments.
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
To manage my docker containers I migrated from and to multiple tools. I started directly with Unraid with individual containers. Then I discovered docker compose and stacks. So I migrated to portainer. Splitting the postgres and mariadb databases were the worst thing in this. Then I tried dockge, so migrated from portainer to that. It lacked some portainer functionality, but was fine for a short while.
Finally I discovered Komodo and migrated to that as it's FOSS. Now I'm only on Komodo, I have no server limit (5 on portainer), had all the functionality of portainer and more. It is my go-to docker manager and the one I recommend to everyone. The only "issue" is that you need to write the name of the stack and click confirm twice if you want to redeploy, restart, stop, destroy. Or you have to click confirm twice after saving when you edit your files. Not much of an issue and it can also protect from accidental clicks. My next step will be to migrate my stacks compose and env files from UI defined to files on the server that I can sync.