Bundler instruction does not work any more #38
Comments
|
Cc @rlepigre who wrote the original instructions I think |
|
We also have tons of dependabot alerts, seems like in general the build system here has been bitrotting quite badly over the years. Does anyone feel in charge of maintaining that? I don't know nearly enough about bundler to do that, so we need someone else to be in charge of the ruby stuff. :) |
|
I spent about an hour yesterday trying to figure out how to fix this on my Mac, so I'm "glad" to hear it's not only a Mac problem. I tried running it through Docker as well, as the README suggests, and that didn't work either. I found this page here which offers some suggestions, but I tried what the poster suggests and it didn't fix the problem for me. (I got some other error at the end.) https://medium.com/@ritviknag/ruby-versioning-trouble-with-jekyll-github-pages-fd2748bf4e1d @amintimany said yesterday that he was willing to take over maintenance of this and possibly change the whole infrastructure, while leaving the general approach of separating the data from appearance (with the .json file) intact. Are you still up for that, @amintimany ? |
|
Yes, I can do that. |
@RalfJung I thing I did, but I just wrote down what I managed to get working without understanding much of what I was doing. 😅 |
|
Locally, I managed to build after #39. Basically, what I did is:
|
|
@rlepigre @RalfJung @robbertkrebbers we should make a decision here. Do we want to change away from Jekyll. I am happy to migrate the webpage to Hugo and maintain it. Unless @rlepigre is happy to continue maintaining this Jekyll setup. |
|
@amintimany I don't know Hugo, is it supposed to be more stable than the current setup? Also, will it support the same kind of stuff we're doing here, with the javascript data and the templates? On the other hand, if the current setup works, is there any point in changing it? I can help maintaining it (although I don't really have a clue what I'm doing, I probably just followed a tutorial when creating the first version), but it'd be better if I was not the only maintainer. |
|
I don't have a strong opinion either way. I am more familiar with Jekyll, but I guess Hugo's template language won't be so difficult to learn either. Amin seems to know Hugo better than Rodolphe knows the Jekyll/Ruby setup, but the bus factor would still be 1. @amintimany can you say a bit more how the Hugo-based setup would look like? Is it required to install Hugo to do any change or can I just push something and CI takes care of everything? |
Also, the current setup unfortunately doesn't work... |
|
It seems like the correct filename is Looks like maybe bundler/gem are broken in Debian. :( |
|
The only advantage of Hugo is that it is easier to manage locally as it does not rely on ruby. We could set up CI so it essentially work as it is now. |
|
Okay I got it to work by manually editing All this doesn't exactly make me more confident in the Ruby-based approach (though to be fair this is Debian's fault to a large extent). |
|
It works for me now on Mac (and I didn't have to go through the hoops that Ralf did). |
|
Yeah Debian's Ruby is just extremely outdated, and has some bad patches. Not really Ruby's fault (unless they are doing something that makes packaging hard). OTOH, the version of Hugo in Debian is from March. So just from that perspective hugo would probably work better on my system. ;) That's not a very strong argument though. |
Turns out that was a bad idea, it breaks using the jekyll that is shipped with Debian. :( |
Even the "fallback" command fails now:
says
bundle installfailsCan someone who knows bundler figure out instructions that actually work please? :)
The text was updated successfully, but these errors were encountered: