[wp-trac] [WordPress Trac] #18852: Nginx rewrite rules

WordPress Trac noreply at wordpress.org
Sat Jul 6 02:56:29 UTC 2013


#18852: Nginx rewrite rules
-------------------------------------+-----------------------------
 Reporter:  johnbillion              |       Owner:  johnbillion
     Type:  enhancement              |      Status:  accepted
 Priority:  normal                   |   Milestone:  Future Release
Component:  Rewrite Rules            |     Version:  3.3
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |
-------------------------------------+-----------------------------

Comment (by jeremyfelt):

 It would be great to see Nginx pushed a bit more alongside Apache in the
 WordPress workflow.

 I do think a lot of the value will come from having a well vetted config
 available **before** WordPress is installed. Either as part of the Codex
 or, better, as a default conf file of sorts that can be moved on the
 server with instruction.

 It seems somewhat more of a chicken/egg thing than Apache has been. Your
 ideal PHP-FPM configuration and basic handling of static assets will
 probably already be setup in order for you to get through the
 installation. Once installed, offering a more complete setup may be
 helpful, though I'd be interested in seeing examples of the different
 configs that would come out of that process.

 The `nginx-wp-common.conf` that we've [https://github.com/10up/varying-
 vagrant-vagrants/blob/master/config/nginx-config/nginx-wp-common.conf
 pieced together in VVV] has served pretty well thus far, though I'm sure
 there's plenty of room for improvement. Ignoring the Vagrant/VM specific
 directives like `gzip off;`, it may be a good starting point for
 discussion and I'm willing to make tweaks to that default config as needed
 if it can provide a good testing ground for core.

 My overall opinion is probably that core can help guide correctly on
 Nginx, but will probably never be able to automatically solve the things
 that the ease of `.htaccess` just working allows for.

 From the perspective of solving annoyances, it **would** be nice to have
 the `$is_nginx` global so that WordPress can report its "got_rewrite"
 status properly without a plugin.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/18852#comment:26>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list