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
  • ShortN0teEnglish
    4·
    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.
    • dinckel@lemmy.worldEnglish
      1·
      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