feat: add Dokploy to Software->PaaS

[nktnet1]

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.
  • I found Add info dokploy and websoft9 to PaaS #596, although that was closed due to having multiple items
• 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?

Allowed me to easily manage my homelab and workplace without relying on third-party platforms.

• Have you used it? For how long?

Yes - 8 months

• Is this in a personal or professional setup?

Both

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

3 VPS, 20+ users, 50+ services.

• Biggest pros/cons compared to other solutions?

  • Horizontal scaling
  • Zero-downtime for docker-compose

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

There are additional terms to the LICENSE, so it's not strictly Apache-2.0 for certain use cases. Some relevant links:

• https://github.com/Dokploy/dokploy/blob/canary/LICENSE.MD
• Queries regarding licenseing and advertising as open source Dokploy/dokploy#3

[Technetium1]

According to your link about licensing, this doesn't seem to be FOSS, but rather a mixed custom license. Until cluster & compose sections are separated, this doesn't seem right to add: Dokploy/dokploy#3 (reply in thread)

[nktnet1]

@Technetium1 re-opening this - licensing has been clarified

• https://dokploy.com/blog/we-are-updating-dokploys-open-source-license