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 posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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
I had never heard of dockge before, but this sounds like the killer feature for me:
Does that mean I can just point it at my existing docker compose files?
My current layout is a folder for each service/stack , which contains docker-compose.yaml + data-folders etc for the service. docker-compose and related config files are versioned in git.
I have portainer, but rarely use it , and won't let it manage the configuration, because that interfered with versioning the config in git.
You add the compose via the DockGE UI, it then creates the necessary files and folders in
/opt/stacks/. Not sure whether it works the other way around: to create the folder, copy the compose file in there, and see if it is recognized.I've been using it for over a year, works very smooth.
Do you version your compose files in git? If so, how does that work with the dockGE workflow?
No, I don't, I only back up
/opt/stacksto borgbase. I imagine it should be possible, but it might depend on how the projects are arranged in git. Monorepo might give trouble, but separate repo's might work.I tried out Komodo, but gave up on it. I looked at dockge after, but opted not to try it out. I prefer the IaaC setup with my compose in a repo for versioning and rollback. And while I think you can probably combine the two, komodo was getting in the way most of the time. It centered around secrets management and generating those secrets at run time.
That said, I feel like if I expand beyond a single server I may go back to one of these tools