Open kokomo123 opened 4 months ago
I guess we can also ask ryangurn these questions as well instead of me answering it for them, correct @nodiscc?
I would say that its Biggest Pro is definitely how beginner-friendly it is to those who are inexperienced with docker compose files. It makes writing and deploying those files extremely easy.
I have used Dockge extensively. It compliments Portainer very well.
I guess we can also ask ryangurn these questions as well instead of me answering it for them
What is going on? Which questions? The answers above look good. I am not sure why a UI is a con, but that's an opinion I am not firm on (either way, pro or con)
Feel free to @ryangurn in the future too if needed.
I guess we can also ask ryangurn these questions as well instead of me answering it for them
What is going on? Which questions? The answers above look good. I am not sure why a UI is a con, but that's an opinion I am not firm on (either way, pro or con)
Feel free to @ryangurn in the future too if needed.
Will mention you in the future for stuff like this, yeah I meant the questions up above. UI isn't really a con, so updated on that 👍🏻
I really enjoyed Dockge, but ended up back with Portainer for management. I use cli to deploy my stacks but for quick reference for things like IP identification for next available, I found Portainer was more appropriate for my needs. Dockge def deserves a place on this board though -- but maybe in the same category as Portainer currently is: Software Containers.
I feel it doesn't fit with Deployment Automation when reviewing the titles in that category. As this is to manage Docker Compose stacks, it seems to make most sense with other container titles. Just my unsolicited 2-cents --
Portainer is lackluster when it comes to compose files, but Dockge does lack finite control over the containers.
I think they would be better described as compliments rather than competing container managers.
I think they would be better described as compliments rather than competing container managers.
Agreed there, they do work well together and I wouldn't classify them as competitors either.
This should close https://github.com/awesome-selfhosted/awesome-selfhosted-data/issues/534
Thank you for taking the time to work on a PR for Awesome-Sysadmin!
To ensure your PR is dealt with swiftly please check the following:
Demo
andClients
are optional. Do not add a duplicateSource code
link if it is the same as the main link. Keep the short description under 80 characters and use sentence case for it, even if the project's webpage or readme uses another capitalisation.Demo
links should only be used for interactive demos, i.e. not video demonstrations.- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
Language
tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.Please take some time to answer the following questions as best you can:
It's awesome as you can easily adapt to the interface if you were using uptime kuma previously. It functions as an alternative to Yacht, Portainer, etc. It also simplifies docker container deployment by letting you start, stop a stack as well as inserting docker-compose files.
I have tried it out for a bit of time and it works to be a good, decent UI for managing docker containers I would say.
Personal setup on my machines.
You can manage quite a lot of docker containers running on Dockge, so as long as you have the resources.
Biggest Pro: has no advertising of any kind, no licenses, no annoying banners, just a straight forward UI