I am running nginx in a container created with a docker-compose yaml file.
Here is a sample docker-compose.yml and environment file:
https://github.com/marioja/Mailu/tree/test-mailu/test-mailu-docker-compose.
The marioja/rainloop:1.9.TEST image is created using this Dockerfile in
GitHub:
https:
Francis, see my response inline:
Hi there,
There's lots of information here, and I'm not sure what specific parts
relate to an nginx issue.
I don't have a full answer, but there are some suggestions below that might
help point at where the problem and fix might be.
> I am running nginx in a c
.
See below in your reply I posted a question.
Francis Daly Wrote:
---
> On Sun, Feb 06, 2022 at 10:08:49PM -0500, marioja2 wrote:
>
> Hi there,
>
> > I checked and the output when starting from docker-compose up -d or
> > d
See below for more questions (I snipped repetitive stuff that was not
necessary for understanding):
Francis Daly Wrote:
---
> On Sun, Feb 06, 2022 at 10:08:49PM -0500, marioja2 wrote:
>
(snip)
> The request that you care about is a
It just dawned on me that the difference between the case where result is
attachment and the case with result is error code is most likely related to
the application reacting to a difference in the environment. Maybe a file or
folder permission. I did check both directory tree and could not see a
d
It took a while and it was starting at me in the face but I did figure it
out. The script that starts the container would make changes to some
php-fpm7 (fastcgi process manager) after it got started. Obviously, this
did not take effect until the restart of the container. This explains the
differ
