While working on #1443 I stumbled over some issues with the current setup of the nginx configuration files:
- Changes to the
https.conf require manual intervention when updating instances that run on https.
- Hardcoded / wrong domain names (https://greedybear.honeynet.com does not exist).
- Cipher list in
https.conf is in part obsolete.
http.conf and https.conf duplicate the upstream and all four location blocks.- Location
^~/admin is identical to location /.
- Path /static/ has no caching or compression.
- The size limits for dev and prod mismatch.
While working on #1443 I stumbled over some issues with the current setup of the nginx configuration files:
https.confrequire manual intervention when updating instances that run on https.https.confis in part obsolete.http.confandhttps.confduplicate the upstream and all four location blocks.^~/adminis identical to location/.