Running without a container

Envoryx is meant to run in its container, and that’s the set-up everything else in these docs assumes. But the binary also runs directly on a Linux host with Docker (envoryx serve), for example while you hack on Envoryx itself. A few things work differently then.

The proxy can’t join the project networks from outside a container, so it talks to each project through its published port on 127.0.0.1:<port> instead. Binding ports 80 and 443 needs the right to use low ports - sudo setcap cap_net_bind_service=+ep ./envoryx gives it that - or you move the proxy elsewhere, e.g. ENVORYX_PROXY_HTTP=:8080 and ENVORYX_PROXY_HTTPS=:8443.

Paths are simpler: there’s no translation between container and host, so ENVORYX_CONFIG_DIR and ENVORYX_PROJECTS_DIR just point at folders on the host (they default to /config and /projects). One thing you lose are the network aliases. Project containers resolve names through the Docker host’s DNS, so a project can’t call http://shop.test from inside its own containers the way it can when Envoryx runs as a container.

All settings are environment variables - see the configuration reference.