Add ShipIt to deployment automation list in README

[DiegoStefanini]

Add ShipIt - self-hosted infrastructure management platform for Proxmox homelabs.

• Website: https://diegostefanini.github.io/shipit/
• Source: https://github.com/DiegoStefanini/shipit
• License: MIT
• Language: Node.js / TypeScript

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 you 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 replaces the need for multiple tools (Portainer + SSH terminals + Proxmox GUI)
  with a single dashboard. Zero agents on managed hosts — everything works over SSH
  and the Proxmox API. Lightweight enough to run on a 2GB CT.

• Have you used it? For how long?

  Yes, I built and use it daily to manage my homelab. About 6 months in development,
  running in production for the last 2 months.

• Is this in a personal or professional setup?

  Personal homelab — Proxmox server with multiple VMs and CTs running Docker services.

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

  3 hosts (2 CTs + 1 VM), ~5 Docker services, centralized logging and security
  monitoring across all of them.

• Biggest pros/cons compared to other solutions?

  Pros: No agents needed, lightweight (SQLite, no external DB), Proxmox-native
  (reads metrics via API), CrowdSec integration built-in, self-deploy with rollback.
  Cons: Proxmox-specific (not for generic Docker/K8s), single-user auth only,
  still early stage.

• Any other comments about your use case, things you've found excellent, limitations you've encountered... ?
  The project has 160 tests (116 API + 44 E2E with Playwright) and a CI pipeline.
  MIT licensed. I'm actively maintaining it and open to contributions.