178
louislam/dockge: A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager (github.com)
submitted 1 year ago by Chewy7324@discuss.tchncs.de to c/selfhosted@lemmy.world
14 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
[-] sup@lemmy.ca 22 points 1 year ago

Finally! Goodbye Portainer!

[-] tristan@aussie.zone 7 points 1 year ago

Not sure this would entirely replace portainer for me since that manages multiple machines, but I am keen to play with this

[-] Flying_Hellfish@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

This was my first thought as well. This isn't a replacement for portainer agents on mulitple docker hosts, hopefully that's something that is doable in the future.

[-] eager_eagle@lemmy.world 6 points 1 year ago

I ditched portainer earlier this year to use the command line only, and don't miss it at all. If you're only using docker compose, I really don't see the point of it.

[-] ShortN0te@lemmy.ml 4 points 1 year ago

The CLI is just fine. But a Dashboard can give you a much better and faster overview of everything. (Color highlighting and so on)

[-] doeknius_gloek@feddit.de 2 points 1 year ago

What's wrong with Portainer?

[-] ShortN0te@lemmy.ml 4 points 1 year ago
  • 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@lemmy.world 1 points 11 months 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

this post was submitted on 22 Nov 2023
178 points (100.0% liked)

Selfhosted

40198 readers
408 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz