avermeer commented on PR #45: URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691769956
> Another idea would be to use the ASF Jenkins CI to build from a different branch and automatically push the content changes to `asf-site`. So we only need to deal with the `.md` files and the test is a CI job. Maybe, but I have no idea how to do this. In the meantime, i'm trying to move on Linux my storm-site workspace. Fighting hard to have proper Ruby version & dependencies to get `gem install jekyll bundler` to work - I'm on a Redhat 8.6 machine and by default it gets Ruby 2.6.0. After a while, I got Ruby 3.0.0 installed and that seems to make `gem install jekyll bundler` working, but then `bundle install` failed until I ran it using `sudo bundle install` (in spite of the warning messages telling it's not a good idea to run it as root). I must confess all this stuff for making minor changes to storm-site seems to me like a _gas factory_. I have the feeling that using LaTeX for Storm documentation would have been even simpler (don't take me seriously for this one). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
