Closed abtris closed 1 year ago
Name | Link |
---|---|
Latest commit | 6e9b8014e493143bf6b2720431cf65112e57edb4 |
Latest deploy log | https://app.netlify.com/sites/house-keeper-proficiencies-68654/deploys/6487257ad8b0d7000808e04f |
Deploy Preview | https://deploy-preview-109--house-keeper-proficiencies-68654.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
[hugo-updater] Update Hugo to version 0.113.0 More details in https://github.com/gohugoio/hugo/releases/tag/v0.113.0
This release adds TLS/HTTPS support to
hugo server
(see cf38c73f and #11064 for details) entirely backed by mkcert. We still default tohttp
which is recommended and good enough for 99% of the Hugo use, but there are some situations where you really need it.We have added a new sub command and some new flags to
hugo server
to enable this:Note that we just delegate to mkcert using its default settings, so all of their documentation is relevant.
Also note that this is currently only supported for Linux, MacOS and Windows. And if you install on Linux using Snap, you will currently get an access denied error when running
hugo server trust
. A workaround for that, or if you need to use some of mkcert's advanced options, is to use mkcert directly to install the local CA:You can then start the server with
hugo server --tlsAuto
.If you have obtained the TLS certificate and key file by other means, you can use the
--tlsCertFile
and--tlsKeyFile
flags. When--tlsAuto
or--tlsCertFile
and--tlsKeyFile
is set and no--baseURL
is provided as a flag, the server is started with TLS andhttps
as the protocol.