Resolve relative paths in vvv-nginx.conf since not allowed by Nginx

[westonruter]

This allows for vvv-nginx.conf to be located in a project's subdirectory, like the private directory on Pantheon:

server {
    listen       80;
    listen       443 ssl;
    server_name  vvv.pantheon.example.com
    root         {vvv_path_to_folder}/..;
    include      /etc/nginx/nginx-wp-common.conf;
}

[lkwdwrd]

Yes! +1 for this!

Luke Woodward – Associate Director of Engineering
10up Inc. http://10up.com | [email protected] | @lkwdwrd

On Wed, Mar 16, 2016 at 1:25 PM, Weston Ruter [email protected]
wrote:

This allows for vvv-nginx.conf to be supplied in a project's
subdirectory, like the private directory on Pantheon:

server {
listen 80;
listen 443 ssl;
server_name vvv.pantheon.example.com
root {vvv_path_to_folder}/..;
include /etc/nginx/nginx-wp-common.conf;
}

---

You can view, comment on, or merge this pull request online at:

#852
Commit Summary

• Resolve relative paths in vvv-nginx.conf since not allowed by Nginx

File Changes

• M provision/provision.sh
  https://github.com/Varying-Vagrant-Vagrants/VVV/pull/852/files#diff-0
  (5)

Patch Links:

• https://github.com/Varying-Vagrant-Vagrants/VVV/pull/852.patch
• https://github.com/Varying-Vagrant-Vagrants/VVV/pull/852.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#852

[westonruter]

@jeremyfelt shall I merge? 😄

[jeremyfelt]

I missed this one. Looks excellent! 👍

[rheinardkorf]

awesome!