NETWORKING

Your projectson your local network.

Develop on your machine through .localhost. When needed, dwell up --lan additionally shares your application routes on the local network using matching .local names.

Get started Documentation

THE COMPONENTS

How the network works.

Dwell connects your application routes to a local gateway. LAN sharing adds a separate gateway on the selected private IPv4 address.

Local domains

Your primary address follows the configured host. .localhost stays on your machine; depending on the system, the URL Dwell prints may include a port.

mein-projekt.localhost

HTTPS & certificates

Dwell can create a certificate containing the .local names for LAN routes. HTTPS is available when the certificate can be created and your device trusts it. HTTP remains accessible.

https://mein-projekt.local

Optional LAN access

dwell up --lan mirrors running application routes to .local. Reachable devices on the LAN can access them; Dwell does not create an internet tunnel.

mein-projekt.local

Auxiliary services

An active backend includes Mailpit and phpMyAdmin on a separate tools host by default. They are shared on the LAN only with the explicit --lan-tools option.

tools.mein-projekt.localhost

What you need to know

Version 1 has no separate LAN authentication. Every device in the reachable LAN segment can access shared application routes. Check what your application makes available there.

Missing mDNS support, firewalls, VPNs or Wi-Fi client isolation can prevent access. Sharing is best effort: a LAN failure is reported separately and does not automatically mean that local startup failed.

Control sharing deliberately.

Run these commands in your running Dwell project. The LAN setting is saved in project configuration. After successful sharing, Dwell displays the active URL and a QR code.

Technical details in the repository

Enable LAN sharingbash

dwell up --lan

Disable LAN sharingbash

dwell up --no-lan