this post was submitted on 22 Nov 2023
179 points (98.4% liked)

Selfhosted

40198 readers
777 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
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
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/[email protected]
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] 23 points 1 year ago (14 children)

Finally! Goodbye Portainer!

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

What's wrong with Portainer?

[–] [email protected] 17 points 1 year ago* (last edited 1 year ago) (5 children)

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.

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

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

[–] [email protected] 6 points 1 year 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.

[–] [email protected] 3 points 1 year 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

[–] [email protected] 2 points 1 year ago

Also, it's quite aggressively pushing the paid option without a way to turn that off

https://github.com/ngxson/portainer-ce-without-annoying

load more comments (1 replies)
load more comments (3 replies)
load more comments (8 replies)