When the disableFastRender
option is added in the configuration file (disableFastRender = true
), it is not taken for the compilation. It was in previous versions of Hugo (I use 0.131).
Since this option is not documented, does this mean that it can no longer be used?
Alternatively, can all CLI parameters be used in the hugo.toml file?
For example, templateMetrics = true
works just fine.
1 Like
Quick test of flags available to the root hugo command, seen by running hugo --help
…
Honored if set in config file:
baseURL
buildDrafts
buildExpired
buildFuture
cacheDir
cleanDestinationDir
contentDir
disableKinds
enableGitInfo
environment
ignoreCache
ignoreVendorPaths
layoutDir
minify
noBuildLock
noChmod
noTimes
panicOnWarning
printI18nWarnings
printPathWarnings
printUnusedTemplates
renderSegments
templateMetrics
templateMetricsHints
theme
themesDir
Ignored if set in config file:
clock
configDir
configDir
debug
destination
disableFastRender
forceSyncStatic
gc
help
logLevel
poll
printMemoryUsage
quiet
renderToMemory
source
tracefile
verbose
watch
The disableFastRender
flag is specific to hugo server
so I would not expect this to be honored if defined in the config file.
Perhaps we should make sure that all of the “honored” items above appear here:
https://gohugo.io/getting-started/configuration/#all-configuration-settings
PR welcome.
2 Likes
bep
August 9, 2024, 3:16pm
3
The templateMetrics
is part of the Hugo build configuration (you see it when running hugo config
)
disableFastRender
is part of the CLI configuration.
There’s certainly some overlaps/edge cases here, but disableFastRender
does not belong in hugo.toml
.
1 Like
system
Closed
August 11, 2024, 3:17pm
4
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.