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

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
    • NeshuraAEnglish
      18•7 months ago

      A lot of smaller things, at least for me. The biggest grievance I have with it is the garbage tier UX between hitting “Deploy” on a stack and getting ito to do so. Error messages in the notification bubble get cut off, are unhelpful amd/or disappear too fast. That and the L9g Voewer sucking ass are my main problems with it and why I’ll definitely check this out.

      • @Voroxpete@sh.itjust.worksEnglish
        5•7 months ago

        Not to mention that there’s no way to view those errors messages after the pop disappears (which happens automatically after a few seconds), so God forbid you hit the washroom or check Lemmy while your stack is deploying, no you have to watch that fucker like a hawk.

        It is fucking ridiculous that I have to copy and paste error messages just to see what they say.

      • rentar42
        4•7 months ago

        Portainer has so many tiny broken places that I effectively treat it only as a read-only view. It lists my containers and shows my logs and nothing much else.

        It could in theory do quite a bit more, but starting from the fact that it doesn’t quite do docker-compose, but its own thing that’s somehow similar but different there’s just too many tiny issues with it.

        Also, it’s quite aggressively pushing the paid option without a way to turn that off (or at least turn it down to tolerable levels).

        • @Voroxpete@sh.itjust.worksEnglish
          6•7 months ago

          “Read only view” is exactly how we’ve started treating it. We used to deploy entirely through Portainer, now we work from the command line and just use Portainer as an information layer. And it frankly sucks at that. Doesn’t even give you preformance metrics.

        • 𝕽𝖔𝖔𝖙𝖎𝖊𝖘𝖙English
          3•7 months ago

          Also, it’s quite aggressively pushing the paid option without a way to turn that off (or at least turn it down to tolerable levels).

          I use an ad-blocker to strip those out

    • @ShortN0te@lemmy.mlEnglish
      4•7 months 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.
      • dinckelEnglish
        1•7 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