The docs mentions: > The control API is the single source of truth about Unit’s configuration. There are no configuration files that can or should be manipulat

The docs mentions: > The control API is the single source of truth about Unit’s configuration. There are no configuration files that can or should be manipulated; this is a deliberate design choice (https://unit.nginx.org/controlapi/#no-config-files https://unit.nginx.org/controlapi/#no-config-files) So yeah, the way to go is to run something like `curl -X PUT --data-binary @/config.json --unix-socket /var/run/control.unit.sock http://localhost/config/ http://localhost/config/` right after you start your nginx-unit. The way to manage a separate config step depends on how you manage to run the process nginx-unit (systemd, docker, podman, kubernetes...). Here's an example I found where the command is put in the entrypoint script of the container (see toward the end): https://blog.castopod.org/containerize-your-php-applications-using-nginx-unit/ https://blog.castopod.org/containerize-your-php-applications...