Timo Stark
Timo Stark
@amg-web Sorry for my late response. The approach is not totally down to Unit as Unit need the corresponding Ruby version on your system to make the Module work. As...
Thanks @remicollet for pointing this out! Did you have a link to the C API changelog just for documentation? That would be perfect!
Fix is already developed and will be part of the next release. Thanks for reporting it to us.
@lone-cat let me share the updated docker-entrypoint.sh with you in a minute. Happy for you to test. Sorry the script changes did not get merged. Sorry for still having trouble...
@lone-cat the fix is ready for you to test Can you test this fix in the `docker-entrypoint.sh` script? ```shell 59,70c59,61 < for i in {1..5}; do < if [[ -S...
Hi @lone-cat - Thanks for testing the fix! Appreciate it! No - This is a "docker initial start issue" only and will not apply if you reconfigure Unit using the...
We are not making use of `/etc/`. UNIT should be initially configured using our control API. This method provides checks of the configuration syntax and makes sure the configuration is...
Thanks @thresheek 👍🏼👍🏼
Hi @Pavlusha311245 thanks for reaching out. As all of your applications are PHP-based, why did you not run all the applications on Unit and use the `application` object to route...
Hi @Pavlusha311245 I have looked at your configuration and created a smal test on my side using the following configuration ```json { "listeners": { "*:80": { "pass": "routes" } },...