#Minimserver ignore the generator#
#Minimserver ignore the full#
#Minimserver ignore the code#

disableLiveReloadĭisable automatic live reloading of browser window. Allowed values in this list: 'page', 'home', 'section', 'taxonomy', 'term', 'RSS', 'sitemap', 'robotsTXT', '404'. disableKindsĮnable disabling of all pages of the specified Kinds. You can turn it off, but we would really appreciate if you don’t, as this is a good way to watch Hugo’s popularity on the rise.

#Minimserver ignore the generator#

Hugo will, by default, inject a generator meta tag in the HTML head on the home page only. htaccess, a Netlify _redirects file or similar using a custom output format. The motivation with this is to be able to generate 301 redirects in an.

Note that even if disableAliases is set, the aliases themselves are preserved on the page. Will disable generation of alias redirects. The site root / will then redirect to /en/. Render the default content language in subdir, e.g. defaultContentLanguageĬontent without language indicator will default to this language. Also see Module Mounts Config for an alternative way to configure this directory (from Hugo 0.56). The directory from where Hugo reads data files. copyrightĬopyright notice for your site, typically displayed in the footer. The directory from where Hugo reads content files.

When building, removes files from destination not found in static directories.

canonifyURLsĮnable to turn relative URLs into absolute. The options in site config is the same as in page front matter, see Front Matter Cascade. Pass down default configuration values (front matter) to pages in the content tree. Include content with publishdate in the future. The directory where Hugo finds asset files used in Hugo Pipes. The directory where Hugo finds archetype files (content templates). Users may choose to override those values in their site

#Minimserver ignore the full#

The following is the full list of Hugo-defined variables.

#Minimserver ignore the code#

So your build command should be hugo -environment staging which will load the G-SSSSSSSS analytics code in your staging website Now you need to tell Hugo that you are using the staging environment. Similarly in staging/config.toml you just need to have one line: Now when you run hugo (build command), by default hugo sets Environment=production, so the G-PPPPPPPP analytics code will be there in your production website This is due to the fact that Hugo is going to merge this on top of _default/config.toml. You need to mention only those parameters which are different or new for the production environment. You don’t need to mention all other parameters like title, baseURL, theme etc. In production/config.toml you just need to have one line: This works since, by default Hugo sets Environment=development when you run hugo serve which uses the config files from _default folder This ensures that no Google Analytics code is loaded in your development server i.e. In _default/config.toml you don’t need to mention googleAnalytics parameter at all. This is how you need to configure your config.toml files considering the above scenario:

You want to use separate googleAnalytics IDs for your production & staging environments (say):.

You don’t want the Analytics code to be loaded in development i.e.

This requires you to specify googleAnalytics = 'G-XXXXXXXX' in config.toml.

Let’s say you are using Google Analytics for your website. Let’s take an example to understand this better. Considering the structure above, when running hugo -environment staging, Hugo will use every setting from config/_default and merge staging’s on top of those.