Skip to content

Move the deploy feature out into its own release archives #12994

@bep

Description

@bep

I have received a question/report about some questionable network activity from Hugo on Windows. This is from a more complex setup that is not practical for me to set up, but I have inspected the code and my prime suspect is the hugo deploy command (the Microsoft Azure integration), which does static initialisation, even if you don't use the feature. We really need to make this feature some kind of plugin (e.g. Wasm), but until then I suggest we pull it out into separate release archives.

We already have a nodeploy build tag for this, so that should not be too hard.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions