Add NeXdocMan software definition

[Arelius-D]

Thanks for taking the time to suggest an addition to awesome-sysadmin!

To ensure your Pull Request is dealt with swiftly, please check the following (check the boxes [x]):

• Submit one item per pull request. This eases reviewing and speeds up inclusion.
• Your addition is Free software.
• You have searched the repository for any relevant issues or PRs, including closed ones.
• Any software you are adding is not already listed at any of awesome-selfhosted, dbdb.io.
• Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
• The file you are adding is formatted as described in addition.md.
• Demo links should only be used for interactive demos, i.e. not video demonstrations. If login credentials are required to access the demo, please link to the credentials directly.
• Comments and unused optional fields have been removed.
• The file you are adding uses kebab-case file naming, for example my-awesome-software.yml.
• Values for platform should match the platforms required to install and run the software.
• Any software project you are adding to the list is actively maintained.
• Any software project you are adding was first released more than 12 months ago.
• Any software project you are adding has working installation instructions.
• You understand that your Pull Request will be merged at least ~1 week after approval, depending on maintainers time.

---

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

• Why is it awesome?
  It is a streamlined shell utility that fully automates the installation, update lifecycle, and system pruning for Docker and Docker Compose on Debian-based systems.

• Have you used it? For how long?
  Yes, in active use for host and container automation for over a year.

• Is this in a personal or professional setup?
  Both. Used in homelab setups and standard VPS environments.

• How many devices/users/services/... do you manage with it?
  Used to deploy and manage containerized services across multiple virtual hosts and nodes.

• Biggest pros/cons compared to other solutions?

  • Pros: Simple TUI interface, handles dependencies and stack pruning out of the box, zero bloat.
  • Cons: Restricted to Debian/Ubuntu-based environments.

• Any other comments about your use case, things you've found excellent, limitations you've encountered... ?
  Significantly reduces setup and maintenance overhead for host orchestration.