Liam Crilly

It might also help to restart only the faulty application instead of the entire service. https://unit.nginx.org/configuration/#process-management > Also, you can `GET` the **/control/applications/** section of the API to restart an...

`python:*-slim` Doesn't contain curl(1) which can limit the ability to manage/configure Unit in a container. Until we have a zero-dependency, fully-featured CLI tool…

> I think adding the -slim based python images alongside of, rather than instead of the full python base image should serve everyone. But then we're also publishing Docker images...

> I'm curious what's generating these messages The `*40` and `*41` entries look suspiciously like the connection ID value in a github.com/nginx/nginx error log. Makes me wonder if this is...

For compactness (don't hate me!) ```json { "action": { "return": 301, "location": "`${'https://' + host.substr(host.startsWith('www.')*4) + uri}`" } } ```

That's how Docker works, Andrew :) https://github.com/nginx/unit/blob/master/pkg/docker/template.Dockerfile#L89 We expect people to use container logging conventions, but sounds like in this case real log files are required. @sidz This topic should...

Hi André, The explanation of these log events can be found here: https://unit.nginx.org/troubleshooting/#troubleshooting-log All event/message severity levels are written to the Unit log file. For Docker images, these typically are...

Oops. My mistake - good catch! I will propose that we change the official Dockerfiles so that the Unit log goes to stderr. Especially as we don't want to conflict...

@ac000 is this ready to be closed or moved to a discussion?

There is a known issue with Spring Boot ≥3.0 (https://github.com/nginx/unit/issues/869)