Closed dblatcher closed 11 months ago
this does also exist here; but more discoverability is always better, maybe worth making one the source of truth and the other linking back to it?
this does also exist here; but more discoverability is always better, maybe worth making one the source of truth and the other linking back to it?
👍 I've added a link to the trouble shooting guide in the setup guide ("There is more detail on this issue...").
My own experience was that I didn't notice the nginx warning in the output from setup and worked backwards from the security warning in the browser to figure out what was wrong.
Seen on auth, usage, image-loader, metadata-editor, thrall, leases, cropper, collections, media-api, kahuna (merged by @dblatcher 12 minutes and 1 second ago) Please check your changes!
What does this change?
Adds a section to the nginx trouble-shooting doc describing a nginx configuration problem I had running locally for the first time.
If I understand it right, this isn't an issue that is specific to this project, but since it involves configuring several subdomains to run locally, it seems not unlikely that setting it up will suface the problem.
How should a reviewer test this change?
n/a - docs only.
How can success be measured?
Hopefully useful to any future devs getting the same problem.
Who should look at this?
@guardian/digital-cms
Tested? Documented?