Skip to content

Mini docker image? #507

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
TeaDrinkingProgrammer opened this issue Mar 19, 2025 · 3 comments
Open

Mini docker image? #507

TeaDrinkingProgrammer opened this issue Mar 19, 2025 · 3 comments

Comments

@TeaDrinkingProgrammer
Copy link

TeaDrinkingProgrammer commented Mar 19, 2025

I have just started using Asciidoc, and something that jumped out at me, is that there is only one variant of the image. As this Docker image includes many packages, maybe it would make sense to create one or two more variants that include less? Maybe the variants specified in this repo could be a starting point? I could help putting them together, but like I said, I don't have much experience with Asciidoc, so I would need someone to give me some pointers.

@dduportal
Copy link
Contributor

Hi @TeaDrinkingProgrammer , what is the problem you're having or trying to solve with the current image?

Shrinking image makes sense in some cases but it has to be identified, because most of the time shrinking causes more issues than it solves (unless, again, on specific tied use cases).

The repository you are pointing to is an example of some of these use cases: it has to be really documented (and not to be the default).

@TeaDrinkingProgrammer
Copy link
Author

Fair question. My use case is that I only need to export to PDF and I only use AsciiDoc diagram, Asciidoctor PDF and CodeRay. An image that only has only this, or at least less than the main image, would allow me to use an image that might be significantly smaller (needs to be verified though). To make actually useful variants, you would need to identify the main usecases, as well as if the difference in size to the main image is significant. Here is a start:

Documentation

  • Usecase: people using AsciiDoc for generating technical documentation.
  • Assumption: probably use diagrams and code highlighting extensively (and maybe math packages?), but not BibTex.
  • Packages: All except reveal.js, BibTex, EPUB3 and FB2
  • Expected savings: no need for BibTex -> no need for LaTex, no need for reveal.js, Epub3, FB

Book publishing

  • Usecase: people using AsciiDoc for book publishing
  • Assumption: probably use most features except Confluence publishing
  • Image: current one, only Confluence does not change size significantly (?)

Presentation

  • Usecase: people using AsciiDoc for presentations
  • Assumption: probably use most features except publishing for things other than presentation. Also do not use BibTex (?). Might want to publish presentation as PDF later.
  • Packages: All except, EPUB3, FB2, Confluence and BibTex.
  • Expected savings: no need for BibTex -> no need for LaTex, no need for Epub3, FB, Confluence

@TeaDrinkingProgrammer
Copy link
Author

TeaDrinkingProgrammer commented Apr 2, 2025

@dduportal What do you think of the proposed use cases? Again, I would gladly put together the Docker images, but I would like to have some feedback on the use-cases I identified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants