Feature: Switch from Apache2 to Nginx #118
Open
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.
As an optional feature, this bash script allows the user to switch from Apache2 to Nginx.
If you're not familiar with Nginx, it's a lean, modern web server that's commonly used to serve static files and often acts as a reverse proxy. While Apache2 is primarily a web server that can be configured to act as a reverse proxy, Nginx is designed with performance in mind, serving static content and proxying requests by default. Although Nginx is optimized for static content and reverse proxying, it can also be extended to support dynamic content (such as PHP) through modules like FastCGI.
Since switching to Nginx I've seen a noticable reduction in response-times running the Stargate project on a Raspberry Pi. Interface feels snappier and quicker, even the api returns results quicker.