Create a dedicated staging server for NGINX
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 would be ideal to have a staging server for NGINX that has the same setup as production (a subdomain that can be accessed directly, as well as a subdomain that goes through Cloudflare). This would allow for NGINX configuration changes to be tested safely without risking causing further outages in production.
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 reviewing the referenced nodejs.org issue and the repository's existing production NGINX and server configuration. Done means a staging server mirrors production, including direct and Cloudflare-routed subdomains, so NGINX changes can be tested without affecting production.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100