Nginx changes

[ShaneMcC]

Description

I found https://github.com/gatsbyjs/gatsby-docker and https://www.gatsbyjs.org/docs/caching/ so I've made some changes to the base nginx config to include appropriate elements from each of those.

Realistically - How much difference this will make, given the reasonably small nature of everything, and that it's proxied via both cloudflare and the main site anyway is debatable, but it felt sane all the same ¯_(ツ)_/¯

[ShaneMcC]

I was looking at what caching should/should not be done for gatsby based on the fact that currently we have pushed a change to Diseased/Courtesan (#198) but this has not been properly picked up on the live site due to over-zealous caching somewhere.

See: https://werewolv.es/guides/roles/Courtesan vs https://wwes-h2p.ds.df.vg/guides/roles/Courtesan even though the first should be proxying the second.

Further: https://werewolv.es/guides/page-data/roles/Courtesan/page-data.json vs https://wwes-h2p.ds.df.vg/guides/page-data/roles/Courtesan/page-data.json

(Seems not everything has a hash-based filename - gatsbyjs/gatsby#15080 or so)

[StormPooper]

If this doesn't work we can poke Mark to look at Cloudflare options.

[ShaneMcC]

Yeah we're still having some issues - #203 is still cached wrong somewhere in the chain:

https://werewolv.es/guides/page-data/roles/Werewolf/page-data.json
vs
https://wwes-h2p.ds.df.vg/guides/page-data/roles/Werewolf/page-data.json

Now this could be because the old data was cached before the changes were put in place, but even force-refreshing, or adding a query-param doesn't seem to pass through whatever is caching it.

[StormPooper]

Suggest @Kirschstein tries to clear the cache as per their support page and if that works we can automate it via their API as part of the deployment.