Open Bruno-366 opened 3 years ago
I am currently using the github action asciidoctor-ghpages-action to build my blog from asciidoc files I really appreciate that it is hosted on github pages and updates my blog on every change (push).
However, since asciidoctor-ghpages-action uses docker-asciidoctor (which doesn't include asciibuild), I can't currently document the output/results of the code that is on my blog.
See: https://github.com/manoelcampos/asciidoctor-ghpages-action/issues/15#issue-877392595
Issue https://github.com/asciidoctor/docker-asciidoctor/issues/54#issuecomment-481398568 mentions that having 2 Docker images might be more appropriate:
asciidoctor/asciidoctor
andasciidoctor/box
with asciidoctor + tools includedRight now it seems like on docker hub asciidoctor/box and asciidoctor/docker-asciidoctor are equivalent?
Also issue #191 (which request adding asciidoctor-kroki) mentions that using layers would be a good idea.
I am pretty sure asciibuild can use layers ^1 ^2 ^3, it also has "out-of-the-box support for creating, manipulating, and executing code inside of Docker containers" ^4.
asciibuild allows you to use asciidoc for literate programming, ie: executing the code within an asciidoc file, which allows a documentation-first approach.
Including it in docker-asciidoctor could open up a really cool workflow. Code in source blocks get executed inside the docker container, and the output gets recorded in the very same asciidoc file.