update NGINX conf

[JulienPeloton]

The NGINX conf proposed in #116 contains a lot of interesting pieces that are not used in the prod server. Tarot on aside (will be added with #116 ) -- it would be good to compare with our conf on the server and include pieces like upstream and location.

@jouvin for review later :-)

[Theodlz]

Hi @JulienPeloton, just to clarify a few things:

• SkyPortal auto-generates an nginx configuration at startup, so the nginx conf added in the recent PR isn't really an addition it's just overwriting the vanilla skyportal one.
• I never quite understood why there was another nginx configuration on the icare production machine, but yeah it means we run the one that's hardcoded on the machine + the skyportal one, already.

Would you be able to share w/ me & antoine (via slack maybe) the one that runs on the production VM (the hardcoded one, not the skyportal generated one)

[Theodlz]

@JulienPeloton actually the newly added nginx config is already working just fine, you can see it here:
https://skyportal-icare.ijclab.in2p3.fr/api/tarot_proxy/

[JulienPeloton]

Hello Théophile --

I never quite understood why there was another nginx configuration on the icare production machine, but yeah it means we run the one that's hardcoded on the machine + the skyportal one, already.

Because the base nginx configuration is handled globally at the level of the IT service for all VM with services that we supervise, to have heterogeneous configuration (version controlled, etc.). We have then addition/deletion specific for some services, but again, that's version controlled at our level.

Would you be able to share w/ me & antoine (via slack maybe) the one that runs on the production VM (the hardcoded one, not the skyportal generated one)

sent :-)