> What is not well documented IMHO is that you don't have to load the config at runtime - if you place the JSON file in the (compile time changeable) /var/lib/unit directory it will be loaded on startup, similar to a traditional /etc config file. But it also will get updated at runtime, if configuration is uploaded on the config socket, making it persist service restarts, hence /var is more appropriate than /etc.
Thank you very much for this example, and calling out the config file option.
Do you find that you get any use from the config api in your setup (vs pushing a new container)?
I imagine it might be more useful if nginx unit acts like a k8s ingress like setup?
As for:
> both webserver and php configuration are in one file[1].
Thank you very much for this example, and calling out the config file option.
Do you find that you get any use from the config api in your setup (vs pushing a new container)?
I imagine it might be more useful if nginx unit acts like a k8s ingress like setup?
As for:
> both webserver and php configuration are in one file[1].
That's just the line in the Docker file:
I found the actual file more illuminating:https://github.com/PrivateBin/docker-unit-alpine/blob/master...