▲ 173 ▼ louislam/dockge: A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager (github.com) submitted 2 years ago by Chewy7324@discuss.tchncs.de to c/selfhosted@lemmy.world 20 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
[–] sup@lemmy.ca 22 points 2 years ago (3 children) Finally! Goodbye Portainer! permalink fedilink source hideshow 6 child comments replies: [–] tristan@aussie.zone 8 points 2 years ago (1 child) Not sure this would entirely replace portainer for me since that manages multiple machines, but I am keen to play with this permalink fedilink source parent hideshow 2 child comments replies: [–] Flying_Hellfish@lemmy.world 4 points 2 years ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] neshura@bookwormstory.social 4 points 2 years ago Sounds easy enough to implement tbh, will maybe take a look later how much work that'd be because it's a must have for me as well permalink fedilink source parent [–] eager_eagle@lemmy.world 6 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] ShortN0te@lemmy.ml 4 points 2 years 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) permalink fedilink source parent [–] doeknius_gloek@feddit.de 2 points 2 years ago (2 children) What's wrong with Portainer? permalink fedilink source parent hideshow 4 child comments replies: [–] neshura@bookwormstory.social 17 points 2 years ago* (2 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. permalink fedilink source parent hideshow 4 child comments replies: [–] Voroxpete@sh.itjust.works 5 points 2 years 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. permalink fedilink source parent [–] rentar42@kbin.social 4 points 2 years 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). permalink fedilink source parent hideshow 6 child comments replies: [–] Voroxpete@sh.itjust.works 6 points 2 years 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. permalink fedilink source parent [–] Rootiest@lemmy.world 3 points 2 years 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 permalink fedilink source parent [–] pacjo@lemmy.dbzer0.com 2 points 2 years 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 permalink fedilink source parent [–] ShortN0te@lemmy.ml 4 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [+] dinckelman@lemmy.world 1 point 2 years ago* (last edited 10 months ago) [deleted] permalink fedilink source parent
[–] tristan@aussie.zone 8 points 2 years ago (1 child) Not sure this would entirely replace portainer for me since that manages multiple machines, but I am keen to play with this permalink fedilink source parent hideshow 2 child comments replies: [–] Flying_Hellfish@lemmy.world 4 points 2 years ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] neshura@bookwormstory.social 4 points 2 years ago Sounds easy enough to implement tbh, will maybe take a look later how much work that'd be because it's a must have for me as well permalink fedilink source parent
[–] Flying_Hellfish@lemmy.world 4 points 2 years ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] neshura@bookwormstory.social 4 points 2 years ago Sounds easy enough to implement tbh, will maybe take a look later how much work that'd be because it's a must have for me as well permalink fedilink source parent
[–] neshura@bookwormstory.social 4 points 2 years ago Sounds easy enough to implement tbh, will maybe take a look later how much work that'd be because it's a must have for me as well permalink fedilink source parent
[–] eager_eagle@lemmy.world 6 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] ShortN0te@lemmy.ml 4 points 2 years 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) permalink fedilink source parent
[–] ShortN0te@lemmy.ml 4 points 2 years 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) permalink fedilink source parent
[–] doeknius_gloek@feddit.de 2 points 2 years ago (2 children) What's wrong with Portainer? permalink fedilink source parent hideshow 4 child comments replies: [–] neshura@bookwormstory.social 17 points 2 years ago* (2 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. permalink fedilink source parent hideshow 4 child comments replies: [–] Voroxpete@sh.itjust.works 5 points 2 years 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. permalink fedilink source parent [–] rentar42@kbin.social 4 points 2 years 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). permalink fedilink source parent hideshow 6 child comments replies: [–] Voroxpete@sh.itjust.works 6 points 2 years 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. permalink fedilink source parent [–] Rootiest@lemmy.world 3 points 2 years 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 permalink fedilink source parent [–] pacjo@lemmy.dbzer0.com 2 points 2 years 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 permalink fedilink source parent [–] ShortN0te@lemmy.ml 4 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [+] dinckelman@lemmy.world 1 point 2 years ago* (last edited 10 months ago) [deleted] permalink fedilink source parent
[–] neshura@bookwormstory.social 17 points 2 years ago* (2 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. permalink fedilink source parent hideshow 4 child comments replies: [–] Voroxpete@sh.itjust.works 5 points 2 years 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. permalink fedilink source parent [–] rentar42@kbin.social 4 points 2 years 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). permalink fedilink source parent hideshow 6 child comments replies: [–] Voroxpete@sh.itjust.works 6 points 2 years 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. permalink fedilink source parent [–] Rootiest@lemmy.world 3 points 2 years 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 permalink fedilink source parent [–] pacjo@lemmy.dbzer0.com 2 points 2 years 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 permalink fedilink source parent
[–] Voroxpete@sh.itjust.works 5 points 2 years 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. permalink fedilink source parent
[–] rentar42@kbin.social 4 points 2 years 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). permalink fedilink source parent hideshow 6 child comments replies: [–] Voroxpete@sh.itjust.works 6 points 2 years 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. permalink fedilink source parent [–] Rootiest@lemmy.world 3 points 2 years 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 permalink fedilink source parent [–] pacjo@lemmy.dbzer0.com 2 points 2 years 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 permalink fedilink source parent
[–] Voroxpete@sh.itjust.works 6 points 2 years 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. permalink fedilink source parent
[–] Rootiest@lemmy.world 3 points 2 years 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 permalink fedilink source parent
[–] pacjo@lemmy.dbzer0.com 2 points 2 years 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 permalink fedilink source parent
[–] ShortN0te@lemmy.ml 4 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [+] dinckelman@lemmy.world 1 point 2 years ago* (last edited 10 months ago) [deleted] permalink fedilink source parent
[+] dinckelman@lemmy.world 1 point 2 years ago* (last edited 10 months ago) [deleted] permalink fedilink source parent