You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/projects/docker-compose-debugger.md
+39-20Lines changed: 39 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,24 +6,41 @@ Browser-based tool that turns messy Docker Compose output into clean, readable d
6
6
7
7
## Features
8
8
9
-
### Service Cards
9
+
### Three views
10
10
11
-
Parsed per-service view showing image, ports, volumes, networks, environment, and extras (restart policy, hostname, depends_on, resource limits). Empty sections are omitted. Switch between YAML and Cards views with the tab bar.
11
+
-**Table***(default)* — service overview + User/Group comparison + Volume comparison, all in one place. Best for quickly spotting UID/GID mismatches or which services share which host paths.
-**YAML** — full sanitized YAML output, ready to paste into a gist.
12
14
13
-
### Markdown Table
15
+
### Copy as Markdown — GitHub or Discord
14
16
15
-
One-click "Copy as Markdown Table" generates a table with columns for Service, Image, Ports, Volumes, and Networks — paste directly into Discord or GitHub issues.
17
+
Two dedicated buttons:
18
+
19
+
-**Copy MD (GitHub)** — `### heading` + bare pipe-table markdown. Renders as a real table on GitHub.
20
+
-**Copy MD (Discord)** — `**bold**` labels + each table wrapped in a fenced code block. Discord doesn't render pipe tables, so the fence preserves alignment in monospace and prevents `_underscore_` / `*asterisk*` characters in volume paths from triggering inline formatting.
21
+
22
+
Both formats include the Services overview, User/Group comparison, and Volume comparison sections.
23
+
24
+
### User / Group merging
25
+
26
+
The "User" column merges three sources of identity into a single value so you can spot mismatches at a glance:
27
+
28
+
- explicit `user: <UID>:<GID>` directive
29
+
-`PUID` / `PGID` env vars (linuxserver convention)
30
+
-`group_add` and `UMASK` in the comparison table
31
+
32
+
Lookups are case-insensitive (so a typo'd `Puid` still surfaces). When the directive matches `PUID:PGID`, only one value is shown; when they conflict, the directive is shown with the env values annotated.
0 commit comments