navig-devhost
Give any local dev server a real .test domain over trusted HTTPS in one command (hosts + mkcert + raw TLS relay), wired into
navig devhost.
Works on its own — its own CLI, no navig required · v0.2.0 · PyPI
On its own (no navig needed)
pip install navig-devhost
navig-devhost --help # no navig needed
With navig
pip install navig-devhost
navig devhost --help
Commands
| Command | What it does |
|---|---|
navig devhost add |
Register a dev domain: hosts entry + (optional) trusted cert. |
navig devhost doctor |
Check prerequisites: mkcert, its CA, admin for hosts edits. |
navig devhost list |
List registered dev domains and their live status. |
navig devhost remove |
Remove a dev domain: hosts entry + cert + registry record. |
navig devhost status |
One-line health per domain (hosts · cert · dev-up · serving). |
navig devhost up |
Run the HTTPS relay (foreground). Ctrl+C to stop. |
Local .test domains with trusted HTTPS for any dev server — one command, any project.
Turn http://localhost:7645 into https://cybesis.test without per-project proxy scripts.
A first-party navig plugin (free, toggleable) that wires together the three
pieces every local dev domain needs:
- a hosts entry on a dedicated loopback (coexists with your other
.testsites on:443), - a trusted mkcert certificate (real padlock, no browser warnings),
- a raw TLS relay in front of your plain-HTTP dev server.
No Playwright/nginx/Caddy — the relay is pure stdlib ssl/socket, and it terminates TLS then
pipes bytes verbatim, so keep-alive, SSE, and WebSocket/HMR pass through untouched.
Install
py -3.13 -m pip install -e plugins/navig-devhost # into navig's Python (Windows)
python3 -m pip install -e plugins/navig-devhost # macOS/Linux
navig plugin list # → navig-devhost … + wired
navig devhost doctor # check mkcert + admin
Prereq: mkcert (winget install FiloSottile.mkcert), then
mkcert -install once so its CA is trusted.
Use
# 1) register (adds hosts entry on next free 127.0.0.x + issues a cert) — needs admin
navig devhost add cybesis.test --port 7645
# 2) start your dev server however you normally do (→ http://localhost:7645)
# 3) run the relay (foreground; Ctrl+C to stop)
navig devhost up cybesis.test # or: navig devhost up (serves all registered)
# 🔒 https://cybesis.test → http://127.0.0.1:7645
Open https://cybesis.test.
Commands
| Command | What it does |
|---|---|
navig devhost add <domain> --port N |
Register: dedicated loopback + hosts entry + mkcert cert. --ip, --no-tls, --target-host. |
navig devhost up [domain] [--all] |
Run the HTTPS relay (foreground). No domain → all registered. |
navig devhost list / status |
Table: hosts ok · cert ok · dev-server up · currently serving. |
navig devhost remove <domain> |
Remove hosts entry + cert + registry record. --keep-cert. |
navig devhost doctor |
Check mkcert, its CA, and admin for hosts edits. |
Everything supports --json for scripting.
Notes / gotchas
- Dedicated loopback per site (
127.0.0.2,.3, …) so each.testcan own:443and coexist — matching the established house convention.addauto-picks the next free one. - Admin is needed only for
add/remove(they edit the system hosts file).up/list/statusneed no elevation — Windows doesn't gate ports < 1024. - Next.js dev: to silence the cross-origin dev warning under the new host, add
allowedDevOrigins: ['<domain>']tonext.config.js. (Vite needs nothing.) - State lives in
<navig config>/devhost/(registry.json+certs/).
First-party navig plugin · Apache-2.0 · reuses navig's hosts plumbing; zero Python deps.
Metadata
Release files for navig-devhost 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| navig_devhost-0.2.0.tar.gz | 27.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| navig_devhost-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.5 kB
Security for navig-devhost 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.