Composr on NGINX
Site staff
Does anyone have experience with using Composr on NGINX? Composr recommends Apache, Litespeed or IIS but I have access to a modest VPS and I'd like to use NGINX there, as the web server.
I expect to come up with the redirect rules myself, aside that, any other major compatibility issue?
Site director
!
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Site staff
Site director
Composr is only tested on, and optimised for, Apache and IIS.
However in principle it should work on any web server software.
There are a few notes to give, although the only one of likely major significance is the URL Schemes one..
| Note | Apache-approach | IIS-approach | Comments |
|---|---|---|---|
| URL Schemes | recommended.htaccess file | web.config file | If URL Schemes are desired then Rewrite rules will need manually writing for other servers, which will require expertise |
| Gzip/caching optimisation rules | themes/*/templates_cached/.htaccess, uploads/.htaccess, recommended.htaccess | None | For other servers just manually configure your preferred rules as desired |
| PHP base-line configuration | recommended.htaccess file (for PHP-module installations only) | None | Default configuration is usually okay, but sample .ini-based configuration is provided in the FAQ |
| 404 error configuration | recommended.htaccess file | web.config file | For other servers just manually configure if routing to Composr's 404 page is desired |
| Efficient IP bans | Written into .htaccess file | None | For non-Apache servers bans are enforced only within Composr's bootstrapping process (a little slower); bans may be manually added to web server configuration as desired |
| Disabling PHP in certain directories | .htaccess files strewn around | No default support | This is an extra layer of security but is not required because Composr prohibits the upload of .php files by users and white-lists accepted file-types |
| Disabling URL access in certain directories | .htaccess files strewn around | web.config file | This is an extra layer of security but is not required because executable PHP files that are not meant to be executed don't have any code that would activate by URL, and private files are protected by filename randomisation |
| Disabling unauthorised log file downloading | data_custom/.htaccess file | web.config file | The Composr error log is the only log that exists, and download is protected as it is a .php file; if additional logs are created manually then the web server should be hand configured to prohibit direct access |
| failover_apache_rewritemap_file option | Supported | None | Fail-over mode can work for Apache users without PHP even working, if this particular configuration is carefully implemented; this is not a feature supported on any other web server |
| MATURITY_FILTER_REQUESTED symbol | Supported (for PHP-module installations only) | No default support | As documented in the Tempcode programming tutorial, there is a workaround for configuring other servers |
| Documentation | Provided | Provided | While documentation is written with respect to Apache and IIS, concepts can be adapted by experienced users |
| Workarounds to quirks | Implemented | Implemented | Quirks present in Apache and IIS are worked around where required (such as ModSecurity, or maximum cookie size); it is not expected significant quirks will exist in other servers that can't be resolved by configuring of said servers |
In terms of operating system support, Composr is only tested on, and optimised for, Windows, Mac, and Linux. It may work on other operating systems supporting by PHP, such as BSD variants – so long as they are Unix-like.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
1 guest and 0 members have just viewed this.
