Feature requests - what do you already love, what could be better?

Features
227

I think the time has come for Netlify to add docfx support to the build image. GitHub - dotnet/docfx: Static site generator for .NET API documentation.

For a while now it’s moved to a cross-platform CLI tool that can be installed as a .NET global tool or an available directly from the GitHub releases. It’s a little chonky for the build image, sure, but it gets enough usage that I think the ability to deploy to Netlify make sense. I know it would definitely be great for us at the NUnit project.

228

You can try adding a Brewfile.netlify with the following code:

brew unzip

and then changing your build command to:

curl -LJO https://github.com/dotnet/docfx/releases/download/v${DOCFX_VERSION}/docfx-linux-x64-v${DOCFX_VERSION}.zip && unzip docfx-linux-x64-v${DOCFX_VERSION}.zip -d docfx && rm docfx-linux-x64-v${DOCFX_VERSION}.zip && export PATH=/opt/build/repo/docfx:$PATH && <your actual build command>

Note that, you’d also have to add an environment variable named DOCFX_VERSION with the value of the version, for example, 2.74.1.

229

Can the policy.xml for ImageMagick be set to max out the resources of the build-bot? The default in Ubuntu installations is very restrictive: ImageMagick command line convert -limit values - Ask Ubuntu

Maybe set it to open? https://legacy.imagemagick.org/source/policy-open.xml

I assume resource limits are set at the bot instance level anyway.

230

I don’t think we can configure that for anyone. You should be able to do it yourself if I recall.

231

I’d love to be able to stop automatic deployment when new commit to production (main) branch has occured while keeping automatic deploy previews builds in pull requests.
At the moment, the only thing to do it by appending [skip ci] or [skip netlify] to commit message. However, this is not ideal solution because simple one can forget it.

232

There should be some basic automated monitoring. On one of my deployed sites, the automatic certificate renewal had failed with the error “Try again later”. The certificate expired in April and Netlify apparently never tried again. Now that I noticed, I had to click “Renew certificate” to get the site back up.