Setup local development environment using Nginx #427
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
SonarCloud Quality Gate failed.
|
seansica
changed the title
|
SonarCloud Quality Gate failed.
|
jondricek
deleted the
423-setup-local-development-environment-using-nginx
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of what has changed
We have introduced Nginx into our local development and production environments to emulate our production GitHub Pages environment more closely. This change involves adding a Dockerfile, helper scripts, and documentation for setting up and using the new development environment. The Dockerfile creates an image that runs an Ubuntu system with Nginx. This allows us to serve our static site locally using Nginx, which behaves more similarly to GitHub Pages than the previous Python-based server.
In addition, the more production oriented Dockerfile located at the root directory of the project was modified to serve the website using Nginx instead of Pelican.
Issues addressed by pull request
Closes #423.