4 commits

Author	SHA1	Message	Date
Bjørn Erik Pedersen	89bd025ebf	Build without the deploy feature by default ... Build tags setup changed to: * !nodeploy => withdeploy * nodeploy => !withdeploy Also move the deploy feature out into its own release archives. See #12994 for the primary motivation for this change. But this also greatly reduces the number of dependencies in Hugo when you don't need this feature and cuts the binary size greatly. Fixes #12994	2024-10-30 11:46:40 +01:00
Rohan Hasabe	6b5e117a12	commands: Use consistent style when describing subcommands ... Closes #12897 Change-Id: Ib27a4a7b540d45243e6252db769d4b9fb7447718 Signed-off-by: Rohan Hasabe <rohanhasabe8@gmail.com>	2024-10-15 08:51:53 +02:00
Bjørn Erik Pedersen	12dc9a6e4a	deploy: Fix deploy defaults for non-zero flag values (e.g. maxDeletes, invalidateCDN) ... This was broken in the config rewrite in Hugo 0.112.0. The workaround is to be explicit about setting these flag values (even if just using the defaults), e.g.: ``` hugo deploy --invalidateCDN --maxDeletes 256 ``` Fixes #11127	2023-06-18 19:38:34 +02:00
Bjørn Erik Pedersen	241b21b0fd	Create a struct with all of Hugo's config options ... Primary motivation is documentation, but it will also hopefully simplify the code. Also, * Lower case the default output format names; this is in line with the custom ones (map keys) and how it's treated all the places. This avoids doing `stringds.EqualFold` everywhere. Closes #10896 Closes #10620	2023-05-16 18:01:29 +02:00