-
Notifications
You must be signed in to change notification settings - Fork 155
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
Comments
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). |
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
Book publishing
Presentation
|
@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. |
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.
The text was updated successfully, but these errors were encountered: