nginx página única js app pushstate vs wordpress regras de reescrita

Question

Gostaria de adicionar: Subpasta cliente / cliente contendo backbone js app (com pushstate) / admin subpasta contendo backbone js app (com ou sem pushstate)

E quando abro meu link no navegador, ele realmente abre o index.html do aplicativo de página única, mas assim que Eu adiciono o / gallery / 1 / date ao url que abre a página wordpress 404 em vez de pushstate.

Este é o meu bloco de locais nginx:

# {{ ansible_managed }}

location ^~ /admin {
    #alias /var/www/project/admin/public/;
    try_files $uri $uri/ /index.html;
    rewrite ^/admin/(.+/)$ /admin/index.html last;
}

location ^~ /client {
    #alias /var/www/project/client/public/;
    try_files $uri $uri/ /index.html;
    rewrite ^/client/(.+/)$ /client/index.html last;
}

# Prevent PHP scripts from being executed inside the uploads folder.
location ~* /app/uploads/.*\.php$ {
    deny all;
}

location / {
   try_files $uri $uri/ /index.php?$args;
}

# Set the max body size equal to PHP's max POST size.
client_max_body_size {{ php_post_max_size | default('25m') | lower }};

include h5bp/directive-only/x-ua-compatible.conf;
include h5bp/directive-only/extra-security.conf;
include h5bp/location/cross-domain-fonts.conf;
include h5bp/location/protect-system-files.conf;

Edit: Este todo o bloco de servidores: (include wordpress.conf contém o exemplo de código acima)

    # Ansible managed: /home/ivan/Dev/fapps/trellis/roles/wordpress-setup/templates/wordpress-site.conf.j2 modified on 2016-02-27 10:16:10 by ivan on ivan-ubuntu

server {
    listen 443 ssl http2;

  server_name   fapps.dev  ;
  access_log   /srv/www/example.com/logs/access.log;
  error_log    /srv/www/example.com/logs/error.log;

  root  /srv/www/example.com/current/web;
  index index.php index.htm index.html;

  charset utf-8;

  # See Virtualbox section at http://wiki.nginx.org/Pitfalls
  sendfile off;

  add_header Fastcgi-Cache $upstream_cache_status;

      include h5bp/directive-only/ssl.conf;
    include h5bp/directive-only/ssl-stapling.conf;

    ssl_dhparam /etc/nginx/ssl/dhparams.pem;
    ssl_buffer_size 1400; # 1400 bytes to fit in one MTU

                add_header Strict-Transport-Security "max-age=31536000; includeSubdomains; preload";

    ssl_certificate         /etc/nginx/ssl/example.com_self_signed.pem;
      ssl_trusted_certificate /etc/nginx/ssl/example.com_self_signed.pem;
      ssl_certificate_key     /etc/nginx/ssl/example.com_self_signed.key;

  include includes.d/example.com/*.conf;
  include wordpress.conf;

  location ~ \.php$ {
    try_files $uri =404;
    error_page 404 /index.php;

    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
    fastcgi_param DOCUMENT_ROOT $realpath_root;
    fastcgi_pass unix:/var/run/php-fpm-wordpress.sock;
  }
}

server {
  listen 80;
  server_name fapps.dev www.fapps.dev;
  return 301 https://$host$request_uri;
}

server {
  listen 443 ssl http2;
  server_name www.fapps.dev;
  return 301 $scheme://fapps.dev$request_uri;
}

    

Answer 1

O último elemento na sua diretiva try_files deve ser o URI do aplicativo ( /admin/index.html e /client/index.html , respectivamente).

Na verdade, o rewrite é provavelmente redundante.

Tente:

location ^~ /admin {
    try_files $uri $uri/ /admin/index.html;
}
location ^~ /client {
    try_files $uri $uri/ /client/index.html;
}

Veja este documento para detalhes.