Network and homelabDocker Service Inventory and Port Map Tracker
One sheet for every service, host, port and backup flag. Finds duplicate ports before a container fails to start. What you get: Excel tracker (example + blank) with conflict detection per host/port/protocol, host summary with...
$12one-time price, instant download
Buy now for $12- Checkout runs on Gumroad, which takes payment, sends your receipt and delivers the files.
- Problem with a file? Message us and we will fix or replace it. Refund terms.
Formats: Excel (.xlsx), Python script
Try a free working sample first →
What you can check before you buy
v1.0version · file dated Oct 14, 2026
4visible sheets in the workbook
381formulas, all readable in the cells
0formula error cells after a full recalculation
nonemacros in the spreadsheet file
Checked on Oct 14, 2026: the workbook service-inventory-port-map-BLANK.xlsx was opened and fully recalculated in LibreOffice and no cell showed an error. This is our own check against the sold file, not an outside audit. The template was drafted with AI assistance; its formulas are checked with automated tests and worked examples.
Also included: compose_ports.py (a plain Python script you can read before running; no spreadsheet macros).
Inside the workbook (from the real file)
input cellformula (hover for the formula)heading
Sheet: Start_here (13 rows, 7 columns)
| Docker / Service Inventory + Port | | | | | | |
| 1. Sheet 'Services': one row per P | | | | | | |
| 2. 'Port status' marks CONFLICT wh | | | | | | |
| 3. Sheet 'Hosts': list each host o | | | | | | |
| 4. Sheet 'PortCheck': type a host, | | | | | | |
| 5. Optional: python compose_ports. | | | | | | |
| The workbook ignores bind address | | | | | | |
| The example has deliberate conflic | | | | | | |
| Never put passwords or API keys in | | | | | | |
| Colour key: yellow = you type her | | | | | | |
Sheet: Services (301 rows, 15 columns)
| Service | Stack / compose project | Host | Image:tag | Bind IP | Host port | Container port |
Sheet: Hosts (21 rows, 7 columns)
| Host | Rows (published ports) | Conflicts | Backup = N rows | Backup coverage | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
Preview shows the first rows of each sheet as calculated. Your copy has the full sheets.
About this template
One sheet for every service, host, port and backup flag. Finds duplicate ports before a container fails to start.
What you get: Excel tracker (example + blank) with conflict detection per host/port/protocol, host summary with backup coverage and a free-port checker; Python compose_ports.py that scans docker-compose files (short port syntax), writes CSV and reports conflicts honoring bind addresses; example stacks; 9 workbook tests + 8 script tests.
Who it is for: Self-hosters running more than a handful of containers across one or more hosts.
Files:
- `compose_ports.py`
- `examples/portmap-output.csv`
- `examples/scan-output.txt`
- `examples/stack-media/docker-compose.yml`
- `examples/stack-tools/docker-compose.yml`
- `service-inventory-port-map-BLANK.xlsx`
- `service-inventory-port-map-EXAMPLE.xlsx`
How to use: open the EXAMPLE file first to see every formula working (yellow cells = your inputs, blue-grey = formulas); then use the BLANK file for your own data. See Start_here sheet / included notes. Test examples are in the Tests sheet or `--selftest` where included.
What it is NOT: Not a container manager or monitoring tool. The script does not parse long port syntax, ranges or variables: it warns instead of guessing.
Questions
What file types do I get?
An Excel tracker in .xlsx format, supplied as an EXAMPLE file and a BLANK file, plus a Python script, compose_ports.py. README.md and SOURCES.md are included, along with example compose stacks and sample output.
Can I edit the formulas?
Yes. The workbook has 381 formulas across 4 sheets. Yellow cells are your inputs and blue-grey cells are formulas, so you can see which is which. Open the EXAMPLE file first to see every formula working.
Does the script replace checking my setup myself, and how do I start?
No. It scans docker-compose files that use short port syntax, writes a CSV and reports conflicts, honoring bind addresses. It is not a monitoring tool and it warns about syntax it does not parse. To start, open the EXAMPLE workbook, then enter your own data in the BLANK file. The Start_here sheet and the included notes explain the steps.
Refunds: refunds follow the rules of the marketplace where you buy; if a file is broken we fix or replace it (
details). It is a planning tool, not tax, legal, financial or engineering advice. Check rates, limits and rules against the official source before you rely on them.
How we check our files.
