New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade default version of hugo #93

Open
fool opened this Issue Oct 19, 2017 · 8 comments

Comments

Projects
None yet
5 participants
@fool
Member

fool commented Oct 19, 2017

Our current default version of hugo is quite old - almost halfway back in the version history (v0.17 vs current v0.30.2).

Could we do the thing we've done with node wherein we pin the old version for old sites and install a newer version to use by default when someone uses a build command hugo on a new site?

It would be a better user experience as very few new customers showing up today use old hugo.

This would need an associated migration in the database for existing repo settings, and some logic in the build image to respect it, but this seems like the sanest place to track all the work.

Request by @bep and his posse of thousands of hugo users :)

@davidpelayo

This comment has been minimized.

davidpelayo commented Nov 30, 2017

I agree this must be updated asap. I was about to use netlify in my personal site to automate the process and simplify it, but since the version is tool old, I'll hold this for now.

@rybit

This comment has been minimized.

Member

rybit commented Nov 30, 2017

We will be updating this, but hugo will probably move faster than our update cycle. Because we don't want to be moving the cheese on a lot of people that aren't being specific about the version that they're using, we have to be careful about updating versions.

I'd recommend setting the HUGO_VERSION as was recommended in your other PR. :)

@inwardmovement

This comment has been minimized.

inwardmovement commented Feb 11, 2018

I'm not sure to understand: it's possible to force Netlify to use the latest Hugo version even if it's not an available version in the Netlify’s Docker file, simply by writing the version we want in netlify.toml ?

@bep

This comment has been minimized.

@inwardmovement

This comment has been minimized.

inwardmovement commented Feb 11, 2018

Yes that is what raised my question, because in Hugo docs it's said:

Setting the build command to hugo will build your site according to the current default Hugo version used by Netlify. You can see the full list of available Hugo versions in Netlify’s Docker file.

which made me think we are bound to Netlify's Hugo version. This was preventing me from using Netlify as I would like to benefit the latest Hugo versions, but it's awesome that we can use whatever version we want, thanks :)

Maybe the Hugo docs should be clarified in regard to this, I can try a PR if you want @gohugoio

@bep

This comment has been minimized.

bep commented Feb 11, 2018

Maybe the Hugo docs should be clarified in regard to this, I can try a PR if you want @gohugoio

That would be most welcome.

@fool

This comment has been minimized.

Member

fool commented Feb 11, 2018

@inwardmovement I'd suggest referring to this blog post that describes in depth what hugo versions are available on netlify and the two ways you can configure one:

https://www.netlify.com/blog/2017/04/11/netlify-plus-hugo-0.20-and-beyond/

@inwardmovement

This comment has been minimized.

inwardmovement commented Feb 11, 2018

Thanks @fool I added the reference in my PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment