Configuring nginx-app.conf to find the /index.php files

[Jay-Nicolas Hackleman]

Hi,

I have recently moved over to the PHP flex environment after the standard environment dev server kept crashing. I am used to working with php on hosting providers like godaddy, bluehost, hostgator etc. Meaning that if I navigate to:
"mydomain.com/path/to/file" - then the server loads "mydomain.com/path/to/file/index.php" and everything just works. If I specify a specific file name and extension in the browser: then that specific file would load.

From what I can understand: I have to do something by providing my own "nginx-app.conf" file when deploying, but I can't figure out how to write the location object to make it work...

Here is what I have now:

location / {
  # try to serve file directly, fallback to front controller
  try_files $uri /app.php$is_args$args;
}

which I pulled from one of the tutorials - but it's not working as desired.

Can someone please help me out?

[Jordan (Cloud Platform Support)]

You can serve static files by specifying the 'document_root' in your app.yaml, and App Engine will take care of configuring Nginx for you as described in the Serving Static Files documentation. 

- Note: Google Groups is for general product discussions and not for technical support. If you require further technical support it is recommended to post your detailed questions to Stack Overflow using the supported Cloud tags. 

[Jay-Nicolas Hackleman]

Am I running static files if I'm running php? 

I've asked the question on stack:
https://stackoverflow.com/questions/48409013/how-do-i-configure-my-nginx-app-conf-file-to-serve-index-php-if-found-in-the-su

[Jordan (Cloud Platform Support)]

For files such as HTML, CSS, and Javascript you would use the static document root. For PHP specific scripts you can follow the documented recommendations. This configuration will fallback to serving your index.php in the case that a requested file does not exist. 

- It is good that you asked this in Stack Overflow with the proper tags. The support teams associated to the tags will be notified, and all further communications about this should occur there.