}
        }

        # Redirect everything under /code to the Fossil instance
        location /code {
            include local/code;

            # Extended caching for URLs known to include unique IDs
            location ~ /(artifact|doc|file|raw)/ {

                include local/code;


                add_header Cache-Control "public, max-age=31536000, immutable";




                access_log off;

            }
        }
    }

----

As you can see, this is a pure extension of [the basic nginx service

We separate that out because nginx refuses to inherit certain settings
between nested location blocks, so rather than repeat them, we extract
them to this separate file and include it from both locations where it’s
needed. You see this above where we set far-future expiration dates on
files served by Fossil via URLs that contain hashes that change when the
content changes. It tells your browser that the content of these URLs
can never change without the URL itself changing, which makes your
Fossil-based site considerably faster.(^Beware: If you use logical
versions in URLs like `/file/trunk/path/name/…` the rule above will
apply to them, too, requiring your users to toss the cache before
they’ll see updates to the referenced content. Trading off caching
versus the possibility of stale data is a delicate dance. You can make
this arbitrarily complex. You might give a cache time of a day or a week
for URLs more likely to change and reserve the really-long times for
those impossible to change without changing the URL.)

Similarly, the `local/generic` file referenced above helps us reduce unnecessary
repetition among the multiple sites this configuration hosts:

      root /var/www/$host;

      listen 80;