Openship version: 0.6.6, self-hosted
The ask
Allow giving a custom domain entry a short label/name, shown on the Domains & Routes cards (and anywhere else domains are listed).
Why
Today the cards are titled positionally — "Primary domain", "Domain 2", "Domain 3"… For a single-domain project that's fine, but multi-domain projects lose meaning fast. Real example from my setup: a Laravel + Reverb project has
relayhook.my → port 8000 (the web app)ws.relayhook.my → port 8082 (the Reverb websocket server)
The second card just says "Domain 2". A label like "Reverb websockets" would make the routing self-documenting — especially valuable months later, or for anyone else looking at the project. Same story for projects that add admin subdomains, API hostnames, or redirect-only domains ("old domain 301").
Sketch
- Optional
label field on the domain record (API + the Add/Edit domain dialog)
- Card title: label when set, else current behavior
- Purely cosmetic — no routing impact
Thanks for Openship — the domains flow with the DNS provider integration is already excellent; this would be a small polish on top.
Openship version: 0.6.6, self-hosted
The ask
Allow giving a custom domain entry a short label/name, shown on the Domains & Routes cards (and anywhere else domains are listed).
Why
Today the cards are titled positionally — "Primary domain", "Domain 2", "Domain 3"… For a single-domain project that's fine, but multi-domain projects lose meaning fast. Real example from my setup: a Laravel + Reverb project has
relayhook.my→ port 8000 (the web app)ws.relayhook.my→ port 8082 (the Reverb websocket server)The second card just says "Domain 2". A label like "Reverb websockets" would make the routing self-documenting — especially valuable months later, or for anyone else looking at the project. Same story for projects that add admin subdomains, API hostnames, or redirect-only domains ("old domain 301").
Sketch
labelfield on the domain record (API + the Add/Edit domain dialog)Thanks for Openship — the domains flow with the DNS provider integration is already excellent; this would be a small polish on top.