Add Dockge to Deployment Automation

[kokomo123]

This should close awesome-selfhosted/awesome-selfhosted-data#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:

• Your additions are Free software
• Software your are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
• Submit one item per pull request. This eases reviewing and speeds up inclusion.
• Format your submission as follows, where Demo and Clients are optional.
  Do not add a duplicate Source 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`
• Additions are inserted preserving alphabetical order.
• Additions are not already listed at awesome-selfhosted
• The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
• You have searched the repository for any relevant issues or PRs, including closed ones.
• Any category you are creating has the minimum requirement of 3 items.
• Any software project you are adding to the list is actively maintained.
• The pull request title is informative, unlike "Update README.md".
  Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
  "Remove aaa from bbb" for removing, "Fix license for aaa", etc.

---

Please take some time to answer the following questions as best you can:

• Why is it awesome?

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.

• Have you used it? For how long?

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.

• Is this in a personal or professional setup?

Personal setup on my machines.

• How many devices/users/services/... do you manage with it?

You can manage quite a lot of docker containers running on Dockge, so as long as you have the resources.

• Biggest pros/cons compared to other solutions?

Biggest Pro: has no advertising of any kind, no licenses, no annoying banners, just a straight forward UI

• Any other comments about your use case, things you've found excellent, limitations you've encountered... ?
  N/A

[kokomo123]

I guess we can also ask ryangurn these questions as well instead of me answering it for them, correct @nodiscc?

[anonhostpi]

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.

[ryangurn]

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.

[ryangurn]

LGTM

[kokomo123]

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 👍🏻

[vorwd]

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

[anonhostpi]

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.

[vorwd]

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.