Hello!
Christopher Baines skribis:
> Ludovic Courtès writes:
>
>> It’s nice that we have but I noticed that, unlike
>> most or all other configuration records that we have, it’s possible to
>> create an record that leads to a syntactically
>> invalid nginx config file.
>>
>> For example, if y
Ludovic Courtès writes:
>> I wonder if some errors could be caught at build time, before attempting
>> to start the service.
>>
>> If in the derivation to build the configuration file, nginx is run
>> against the built config file with -t, that might spot errors at
>> derivation build time.
>
>
Hi,
Christopher Baines skribis:
> Ludovic Courtès writes:
>
>> It’s nice that we have but I noticed that, unlike
>> most or all other configuration records that we have, it’s possible to
>> create an record that leads to a syntactically
>> invalid nginx config file.
>>
>> For example, if you
Ludovic Courtès writes:
> It’s nice that we have but I noticed that, unlike
> most or all other configuration records that we have, it’s possible to
> create an record that leads to a syntactically
> invalid nginx config file.
>
> For example, if you have a location block like this:
>
>
Hi Gábor,
Gábor Boskovits skribis:
> I would like to add some more information to this, which I encountered when
> trying to find a solution to the last-modified issue:
>
> 1. the nginx configuration can only be extended using server blocks, so it
> is not possible to inject a location or a nest
Hello,
Ludovic Courtès ezt írta (időpont: 2019. szept. 12., Cs,
9:58):
> Hello Guix!
>
> It’s nice that we have but I noticed that, unlike
> most or all other configuration records that we have, it’s possible to
> create an record that leads to a syntactically
> invalid nginx config file.
>
>
Hello Guix!
It’s nice that we have but I noticed that, unlike
most or all other configuration records that we have, it’s possible to
create an record that leads to a syntactically
invalid nginx config file.
For example, if you have a location block like this:
(nginx-location-configurat