Skip to content
Search

Localias

lastmod 2026-03-02created 2025-10-062 edits

Custom local domain aliases for local development servers

About

  • A tool that lets developers manage aliases for local development servers, making it easy to run them behind a TLS proxy
  • Supports https://server.test → http://localhost:3000 redirection in both the browser and the command line
  • Port-free HTTPS URLs usable in both the browser and the CLI
  • Automatic TLS certificate issuance and /etc/hosts updates make it possible to build a production-like security, cookie, and CORS environment
  • Supports shareable YAML configuration and both foreground and daemon modes; the whole team can use the same aliases, and changes are applied to the proxy immediately
  • Internally uses Caddy to handle the HTTP→HTTPS proxy and mDNS (.local) broadcasting, so other devices on the same network (e.g. smartphones) can also connect
  • Works on MacOS, Linux, and WSL2
  • Advantages over hotel/chalet
    • Runs as a single binary with no NodeJS dependency
    • No system proxy settings needed; based on the hosts file, so it is consistent across browser and CLI
    • Supports multiple TLDs and automatic TLS signing for a warning-free HTTPS environment
    • Auto-discovered repo configuration makes team sharing simple, and process management follows a non-intrusive principle for flexibility
  • Typical use cases
    • Building an integrated local stack that exposes the frontend/backend as https://app.test and https://api.test respectively, to verify Secure Cookie, SameSite, and CORS exactly as in production
    • Checking responsive, PWA, and login flows in real mobile device testing by simplifying access to devices on the same network via .local domains
    • Standardizing the developer experience during team onboarding by sharing fixed domains instead of memorizing environment variables and ports

See also

Favorite site

author Zer0 sitemap