Proxy-only dev server manager for Linux.

Key feature: Clean subdomain URLs (*.localhost) routing to your manually-started dev servers.

cd ~/projects/lazydev
bun link
lazydev init

# 1. Start your dev server manually (in a separate terminal)
cd ~/projects/myproject
bun dev

# 2. Add the project (tell LazyDev which port to route)
lazydev add --port 3000 --name myproject

# 3. Start the proxy
lazydev start

# 4. Access in browser
# http://myproject.localhost

lazydev init              # Setup config, dnsmasq, port 80
lazydev add --port <n>    # Add project (requires --port flag)
lazydev remove <name>     # Remove project
lazydev list              # List all projects
lazydev start             # Start proxy daemon
lazydev stop              # Stop proxy daemon
lazydev restart           # Restart proxy daemon
lazydev status [name]     # Show status
lazydev logs              # View proxy logs
lazydev completions       # Install shell completions

1. You start your dev server (e.g., bun dev, npm run dev)
2. Add project to LazyDev with the port number
3. LazyDev proxies *.localhost requests to your dev server

Browser → http://myproject.localhost → LazyDev Proxy → localhost:3000 (your dev server)

Config file: ~/.config/lazydev/config.yaml

settings:
  proxy_port: 80

projects:
  myproject:
    port: 3000
    aliases: [mp]      # optional: access via http://mp.localhost
    disabled: false    # optional: temporarily disable

The original LazyDev attempted to manage dev server lifecycle (start/stop on idle). This worked for simple servers but failed with:

• Nuxt/Vite: Cold start + lazy compilation = race conditions
• Complex frameworks: Hot reload, workers, background processes

Proxy-only mode is simpler and more reliable - you control your dev server, LazyDev handles routing.

• Bun 1.2+
• Linux
• dnsmasq (for DNS)

sudo setcap 'cap_net_bind_service=+ep' $(which bun)

sudo dnf install dnsmasq
echo "address=/localhost/127.0.0.1" | sudo tee /etc/dnsmasq.d/lazydev
sudo systemctl enable --now dnsmasq

MIT