After spending way too many hours on this, I finally managed to get most things upgraded and working - https://libcloud.staged.apache.org. This includes:
* Upgrading Jekyll to latest stable versions (4.2) * Upgrading Ruby to latest stable version (3.1) * Upgrading Bootstrap theme to v3.3.7 and jQuery to v3.3.1. Sadly upgrading to Bootstrap 5 would be too much work (pretty much a complete rewrite). Same goes for upgrading to jQuery v3.6.0 - the asset compressor we use is old and crashes when trying to compress / minify latest version of jQuery. I know there are some known security issues with older jQuery versions, but since jQuery is used in a very limited fashion (no user input is ever passed to jQuery code) and out website is purely static content (no dynamic server side component), I think those shouldn't affect us. * Docker image which handles installing all the dependencies and the environment which should make contributing and building the website locally very easy. As a "bonus" also added a new dark mode / theme. Theme still needs some love, but it should be a start. Long term we can also figure out automatic website build + deploy on push to main branch (I don't think we can utilize ASF build infrastructure since we depend on custom Ruby plugins with C extensions). Staging website: https://libcloud.staged.apache.org/ Source code: https://github.com/apache/libcloud-site/tree/asf-staging I hope to have it all finished and deployed this weekend (and hopefully after that it will serve us well again for many years - unless of course someone wants to contribute a new and fresh design / theme). ------- Original Message ------- On Monday, March 28th, 2022 at 7:49 PM, Tomaz Muraus to...@tomaz.me wrote: > It turns out that creating a working Dockerfile is a massive pain, because > the Ruby and Jekyll version used are very old and unsupported and this brings > up all kind of issues. > > I did manage to get it working in the end with some hacks and changes in the > Jekyll configuration > (https://github.com/apache/libcloud-site/blob/asf-staging/Dockerfile), but at > this point it may actually make the most sense to try to redo the whole > website from scratch using a new version of Jekyll and Ruby. > > I did try an incremental upgrade, but that didn't work out since there are > tons of breaking changes and we also rely on custom plugins. > > ------- Original Message ------- > > On Sunday, March 27th, 2022 at 9:15 PM, Tomaz Muraus to...@tomaz.me wrote: > >> I just wanted to give everyone a heads up - I'm working on moving the >> website source code from svn to git (finally!). >> >> New website repo location will be - https://github.com/apache/libcloud-site/ >> (https://gitbox.apache.org/repos/asf/libcloud-site.git). >> >> ASF website publishing infra does support building the website automatically >> on push using jekyll, but that doesn't seem to work with our repo. >> >> I didn't dig in too much, but I assume it's likely related to old jekyll >> version + extensions we depend on. That means that for the time being, we >> still need to build the website locally before pushing it to the repo. >> >> I will let everyone know when it's fully set up and working. >> >> I still need to do the following: >> >> - [ ] Update readme with how to contribute website changes (info on how to >> utilize staging branch, how to generate the website, etc.) >> >> - [ ] Add Dockerfile used for generating the website (since sadly we still >> rely on ancient version of jekyll and Ruby which is a pain to install >> without rvm, etc.) >> >> - [ ] Update actual website and add information about the new website >> repository >> >> Some reference links: >> >> - >> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Staticwebsitecontentgeneration >> >> - https://infra.apache.org/project-site.html
