Selfhosted

40209 readers

732 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:

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!

founded 1 year ago

MODERATORS

179

louislam/dockge: A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager (github.com)

submitted 1 year ago by [email protected] to c/selfhosted

21 comments fedilink hide all child comments

Features:

Manage compose.yaml
- Create/Edit/Start/Stop/Restart/Delete
- Update Docker Images
Interactive Editor for compose.yaml
Interactive Web Terminal
Reactive
- Everything is just responsive. Progress (Pull/Up/Down) and terminal output are in real-time
Easy-to-use & fancy UI
- If you love Uptime Kuma's UI/UX, you will love this one too
Convert docker run ... commands into compose.yaml
File based structure
- Dockge won't kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal docker compose commands

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 1 year ago (1 children)

            
              UI, just too many annoyances. Fkr example the cut off unhelpfull error messages
compose files, like this project calls it are taken hostage by portainer
git, while you can use a repository there is no comfortable way to test out changes and commit them to git. Would portainer use a sinple file structure for compose files that would not be a problem
Ads, they try to promote there business version via the UI.

[–] dinckelman 1 points 1 year ago

I could close my eyes to all of those, but the issue that pisses me off the most is that often enough Portainer just forgets which stacks it has ownership over, forcing you to delete the whole stack, dig up the old compose from its files, and create it again