Speaking for myself: 1. I want nginx to serve static files, and everything else to be reverse proxied to the webapp 2. The configuration file that allows /fav

Speaking for myself: 1. I want nginx to serve static files, and everything else to be reverse proxied to the webapp 2. The configuration file that allows /favicon.ico (and others) to be a file but / and other paths to be passed to the webapp is kind of ugly. Here's mine: location ~* ^/(favicon.ico|apple-touch-icon.png)$ { root $icons_path; } In my own case I've so far decided to accept the ugly config file, but as you can see, I haven't gotten around to adding even a robots.txt or any of the other files the modern web ecosystem expects; and adding them involves adding them one-by-one. I can see why someone would say, "Why make an ugly hack of an nginx config, when I can just define the favicon location in the metadata to a path easily configured to be files-only?"