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 used portainer only as fancy docker dashboard and to start stop services. It was buggy and even with the git implementation really frustrating to use. Also that they do not store the compose files is simply not ok.
Dockge fully replaced portainer for my needs.
I love Dockge. Have also replaced Portainer with it.
But I hate that I can't just restart a single container easily with it. It's a small enough issue since most of the time I need to restart the entire compose file because of dependencies, but still.
You can go to the terminal tab and just run the cli command.
Not perfect, but something to avoid needing to ssh in at least.
Yeah that's usually what I do on a computer. But I didn't have easy access to a computer, so I manage my server from my phone. So ssh is usually easier lol
To be fair, Dockge is very, very new. I imagine features like that will turn up soon enough.
Oh most def.
I guess I'm complaining that it isn't already there, but honestly I love Dockge. Won't be going back to Portainer. Pretty much since the beginning I've been using compose files, and it always bugged me how Portainer handled them.
Dockge is what I've always wanted, tbh. Just some QoL stuff here and there, but I'm very happy with it :)
Agreed. Really annoying.
The complete and utter lack of a mobile friendly interface is beyond frustrating. No android, i don't want you to snap zoom to the search bar every fucking time i go to my stacks page!?
Dockge looks interesting, I gotta check that out
Just for you to known, they store the compose file. It's in their compose folder on the data volume.
Oh yeah, sorry i know. Was too lazy to type it out. They number the created compose files in numbered directories instead of naming it after the stack.
The problem is, that they do not support at all the direct modification of those files and the abstraction of numbering them instead of giving them real names is annoying when you want to start them via cli.
Technically true, but if you actually try to interact with those compose files directly then shit gets really fucky.
Portainer does store compose files though? I've manually used docker compose commands from the folders Portainer saves them in. They're labeled with numbers instead of project names which makes it difficult to know which one you're looking for, but I use rga so that wasn't as much of an issue for me as it would have been otherwise. It was tedious, but the compose files very much exist on your hard drive.
Yes i am aware,i commented on another post. The problem is that interacting with those directly messes things up. I want a panel that allows me to use cli and gui at the same time without breaking things.