rzo1 commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691822753
I think you are good to go.
--
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 commen
rzo1 commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691776984
> 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
rzo1 commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691718993
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
rzo1 commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1691635335
I think you could manually create a "hardlink" in Windows (don't using
Windows for a few years now).
+1 for adding some warning.
--
This is an automated message from the Apache Git S
rzo1 commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1690993248
Looks like the symlink to current is missing :-)
--
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 t
rzo1 commented on PR #45:
URL: https://github.com/apache/storm-site/pull/45#issuecomment-1687644204
@avermeer I think you need to run `bundle exec jekyll build -d content` to
update the `content` directory.
--
This is an automated message from the Apache Git Service.
To respond to the mes
