as I’m working on a site, at various points I’ll capture the template metrics output from a clean start of hugo.
Some things that I think would be generally helpful to include, and is already available:
- the date/time that this blob of template metrics were generated and posted to console.
- the version of hugo being run
- a dump of the config as hugo observed it when generating this particular run.
- this would likely benefit from the inclusion of any/all command-line flags passed to hugo when it was started, as these aren’t likely to be represented in the config files
similar to the generation of hugo_stats.json (WHICH is a lifesaver. Thank you!)
I would think that having the ability to ask hugo to emit the version string it emits when starting to build the sites just before or after emitting the template metrics; alongside the current date/time wouldn’t be terribly hard, and would help by making it easier to assess build-to-build changes…
Hugo currently emits some things it deems relevant after the template metrics[1]
would it be unreasonable to emit the current date/time, and hugo version alongside this info?
or the commandline flags passed to hugo that aren’t captured in files in config…
I ask, as it seems to me that this information is equally relevant… and I’m not sure why it wouldn’t already be there… so there’s likely a good reason I don’t understand yet
Currently it emits: # of pages, # of files, # of images, # of aliases, some useful memory metrics, the hugo environment, how hugo is serving files, the serving URI, bound address ↩︎