![]() ![]() This is where most of the customization happens for me. The next level up is the local configuration, which applies to all sites hosted on this local server. Each site inherits a set of local server configuration values because it’s actually overriding other configuration values from the level above. SiteDomain: specifies the site’s domain name.LogFile: specifies where the nginx log is located for this site.Include: starts the configuration hierarchy mentioned above.Here’s a brief description of the configuration directives: Let’s start with the configuration of an individual site: 1 The beauty of this design shines through when you look at the details more closely. This model creates a logical hierarchy for configuration: 1Ī - local server defaults (apply to all sites)Īwstats.th.conf - configuration per website ![]() Finally, site-specific configuration lives in the nf file. Future versions may overwrite that file, so local server-wide changes should be made in, which will not be updated by future package updates. Here’s how this works: nf provides the default configuration from the upstream project and Ubuntu package maintainers. The configuration files are layed out like this: 1 AWStats configuration on Ubuntu utilizes a traditional package/distro/local hierarchy. The first thing we need to do is configure a site. I opted for the second, since I have prioritized hosting static content on my server.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |