Conversation
Signed-off-by: Michée Lengronne <michee.lengronne@coppint.com>
ace4195 to
c824dc1
Compare
|
@rndmh3ro What do you think ? The first travis failed because it deactivated itself (weirdly detecting a non existing more recent build). |
|
So you want to test nginx-configs that do not get loaded by the running nginx? |
|
For instance: |
This seems to be not correct. I just ran
This seems like a valid case to test. However shouldn't we then do something like this: If we just use the contents of a file to test it, how should we be sure that we test the whole configuration? The above way would also validate the config. |
|
Indeed. For instance, my personal use case is an nginx path present in I build my container with this command: As nginx.conf loads every other configs used by the nginx process, loding it with |
|
I'm not exactly sure what you're asking now. What do you think about my idea? |
|
I think it should work. |
It is usefull if you want to test an nginx install where configurations are not in the standard directory.