VIMC-3908: Add the data visualisation tool to montagu

[richfitz]

I've taken the opportunity to have us track "stable" for nginx, which will keep us more up to date.

Minimal changes in here to the conf in the end

[EmmaLRussell]

Is the idea that this '/visualisation' route will eventually be present on all environments (so that's where we are eventually going to put the actual public-facing data vis tool)?
And the index.html is just what will be served until the script in vimc/montagu#167 is run, overwriting it with the report pathspecified there?
In which case we may be deploying this to prod before public viz is ready to go on prod? So maybe index.html should be a little more public-facing if there's a chance any external users might find their way to it, even if it's just to change 'Hello world' to 'Coming soon'?

[richfitz]

Is the idea that this '/visualisation' route will eventually be present on all environments (so that's where we are eventually going to put the actual public-facing data vis tool)?

Yes, once the paper is published

And the index.html is just what will be served until the script in vimc/montagu#167 is run, overwriting it with the report pathspecified there?

This file primarily exists to make sure the directory does (though we could do that easily enough with an exec mkdir on vimc/montagu#167). For reasons unknown the /visualisation route gives a 403 to me, but I'm not that bothered by that.

In which case we may be deploying this to prod before public viz is ready to go on prod? So maybe index.html should be a little more public-facing if there's a chance any external users might find their way to it, even if it's just to change 'Hello world' to 'Coming soon'?

This should be fine to deploy to prod (having something we could not deploy would be problematic!)