#4981 - Documented nginx rewrite rules
| Identifier | #4981 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Documented nginx rewrite rules |
| Status | Open |
| Tags |
Roadmap: Over the horizon (custom) |
| Handling member | Deleted |
| Addon | core |
| Description | Enhance the build_rewrite_rules.php script to be able to generate sample rewrite rules for nginx.
Automatically put them into the tut_webhosting tutorial under a new section for sample nginx configuration. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
- Nginx is nice, it would be good to not have to rely on having Apache behind it
- Some hosting control panels are pushing Nginx-only now, not Nginx+Apache
Broadly we identified some good reasons for using Nginx:
- Faster for static files
- Allows having multiple sites running off of different ports (for webapps that need to run off of a webroot) but then transparently hosted on arbitrary URLs via reverse proxying
- More modern