Nginx conf for test and production
mekane opened this issue · 1 comments
Figure out strategy for differentiating between test and production in the nginx configuration. How does nginx include env vars / what does Docker give us?
Is there any mapping / association we can take advantage of?
(Consult with Cribbs, circle back to Marty)
Talked this over with Steve Z. Sounds like the best approach is to either wildcard the vendor, library, and staff domains, or to alias all the potential test and production names into the server directives. And for the cookie domains we'd assume we're always on carli.illinois.edu
The effect of this is that the same nginx conf would work for test and production, and only those two environments. Which is good in that the exact same images will work on test and production, so test can truly be a staging environment, functioning exactly like production.