Create CI for testing the NGINX config
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
As a lesson learnt from https://github.com/nodejs/nodejs.org/issues/5149, it'd be nice to have CI setup in this repository that validates the NGINX config for nodejs.org. I'm not sure the best way to do this, but perhaps just spinning up docker-compose with a mocked file system behind it that contains some fake dist/website files, and then a small E2E test suite that checks valid responses and 404s are all working as expected (including the localisation fallback behaviour).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository's NGINX configuration and any existing Docker Compose or CI setup. Review how a mocked dist/website filesystem could support checks for valid responses, 404s, and localisation fallback behaviour. Done means CI exercises these cases and fails when the NGINX configuration or responses are invalid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, nginx
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100