-
Notifications
You must be signed in to change notification settings - Fork 196
Support extended Hugo version #182
Comments
the issue on binrc is the one to watch for a resolution. In the meantime, 1 potential workaround which is not ideal: follow bep's advice: |
i tried manually including binary in the repo - as a quick-fix - doesn't work:
|
We'll track that separate issue here, @jensamunch : #183 |
To those looking for a workaround until this is fixed: Run |
It would be really great to have a bit more of an explanation from the Netlify team on timeline and plan. |
@jensamunch Unfortunately, the solution involves upgrading the version of Ubuntu we use in the base image. That is a larger user impact than we initial hoped for. In order to ensure a smooth transition for all users, we need to do some work around communicating the changes ahead of time. Once we have a firm timeline, we will communicate that publicly. |
Fast workaround #183 (comment) |
Currently netlify doesn't support Hugo's asset pipeline (netlify/build-image#182)
If you don't want to check in
|
Looks like the last dev update was in August. How are things going on this issue? |
@rdebeasi you don't need the "extended version" to do image processing. I was told by Netlify several times that this issue is hanging on a upgrade of their build environments from Ubuntu 14.04 (which has an EOL date in April next year). I have been given the impression that this is something "actively worked on" and that solution was "around the corner". I would probably been looking for an alternative fix from the Hugo side (building 14.04 compatible binaries) if I had known that this was going to take so long. Is it possible to get a time estimate on this issue? |
For what it's worth the solution posted by @igk1972 is working great for me |
Hey all, I'm taking over for Bryce on this issue. Sounds like this is blocked by #222 The Ubuntu upgrade is in progress (see the mentioned PR), and I am currently working on improving our build pipeline to accommodate different build images, and free up constraints to help make more frequent releases. I can't give dates yet, but it's high priority and we are actively working on it. |
the error gone by adding |
is this now solved? |
Not right now, but the goal with the current work is to enable more rapid updates in the future. |
@jensamunch No, but @biilmann (Netlify CEO) has silently kind of at least not denied that a fix for this could be a nice Christmas present :-) |
Hi All! Any volunteers interested in beta testing a new buildbot image? What it entails:
Im particularly interested in sites that may be running not in extended mode but on a version of hugo greater than 0.43, or if you are interested in testing out extended mode things that previously were not working for you. |
@bcomnes 'tecidev' |
workaround for netlify/build-image#182
@bcomnes please add kind-bartik-cd167d too please, thanks! |
@bcomnes please add "negative-reviews", cheers! |
@bcomnes |
Hey folks, sorry for the delay. I was out for holidays and a handoff wasn't possible. I deployed #197 yesterday, but determined it wasn't a reliable enough fix. I partially reverted it here: #248 I kept the required libraries though, which means if you provide your own hugo extended binary in the build, or download it on build, you can use it by doing something like: LD_LIBRARY_PATH=$HOME/stdc++6/usr/lib/x86_64-linux-gnu ./hugo The good news is, I've started a deployment of the Disclaimer: the preview dev image isn't 100%, things will change potentially until we come up with a stability contract on the new xenial image. Stay posted on this issue for updates, and thank you for your patients on this issue. It is my primary priority as of now. |
@bcomnes seems broken for me:
If you could please revert it, I need to set something live. Cheers P.S.: sorry to waste your time, I thought it was a beta testing thing, where it was probably going to work out of the box ;) |
@StefanoChiodino If you are providing your own hugo extended version and are running into that error try setting the LD_LIBRARY_PATH when running hugo in the current image:
I'm currently working on an out-of-the-box fix we can hopefully provide preview access to asap. |
@bcomnes if you're still taking signups, please enable for 'grumpycorp'. Thank you! |
A workaround for netlify deploys is just upload resources one or a bash script (untested) netlify/build-image#182
Sorry for the delay. Almost ready to start adding sites to the dev image this week. Please update your comments if you do NOT want your site added to a potentially-unstable-at-times |
@bcomnes please add 'yonson', thanks! |
Ok, confirmed its working, I'm going to start adding sites onto it. |
Ok, I set up an issue track dev image beta stuff over at #254 Lets keep this issue specific to hugo extended from here on out. |
Since this is working in the xenial image, I'm going to close this. We should get that out to everyone soonish. Thanks for your patients and all the input on this one, and my personal apologies for it taking so long. We have some great improvements to the buildbot pipeline coming this year you will all love. |
removing `resources` folder from being tracked as should be generated
Building sites … ERROR 2019/05/28 20:15:29 error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version, see https://goo.gl/YMrWcn for more information Total in 187 ms Error: Error building site: logged 1 error(s) The command "hugo -d public" exited with 255. Refs: netlify/build-image#182
If other people like me come here wondering how to actually apply the fix to their existing projects, here is the article how to switch to the new Ubuntu version: https://www.netlify.com/blog/2019/03/14/a-more-flexible-build-architecture-with-updated-linux/ |
…orks: Related issue: netlify/build-image#182 Once netlify upgrades their ubuntu version the resources/ folder can be .gitignore'd again and everything should work.
Solution in #183 (comment) allowed me to deploy hugo with sass/scss on netlify. |
Duplicate of: netlify/binrc#16
Opening an issue here as @futuregerald kindly suggested.
- What is the current behavior?
From version 0.43 Hugo comes in two flavours, extended version allows native Sass compilation.
Netlify currently does not support extended version:
Edit: For now, the recommended workflow is to commit your
/resources
folder after building locally withhugo
.- What is the expected behavior?
Either download the extended binary by default from now on or allow to specify something like 0.43/extended in netlify.toml.
_extended is added to the release path before the version number:
https://github.com/gohugoio/hugo/releases/download/v0.43/hugo_0.43_Linux-64bit.tar.gz
https://github.com/gohugoio/hugo/releases/download/v0.43/hugo_extended_0.43_Linux-64bit.tar.gz
The text was updated successfully, but these errors were encountered: