At the moment, asciibinder builds all topic maps that exist in the _topic_maps folder (depending on the distros chosen)
Alternatively, you can use the --page option to build a single page, which hugely reduces build resources
However, if you edit many modules in a PR, then the --page option is harder to use and requires working backwards up the tree to figure out what pages have changed and requires creating multiple page builds.
It would be good to be able to build a specific book (top-level topic group), so that you don't have to end up building lots of individual pages, while at the same time avoiding the >>2GB full preview build.
Most books are <25MB, so just building a single book could require 1/100th of the resources versus a full preview.
I have replicated the issue with my local asciibinder build. Using @gabriel-rh's container image with his updated version of asciibinder, I verified the fixes worked as expected.
At the moment, asciibinder builds all topic maps that exist in the _topic_maps folder (depending on the distros chosen)
Alternatively, you can use the --page option to build a single page, which hugely reduces build resources
However, if you edit many modules in a PR, then the --page option is harder to use and requires working backwards up the tree to figure out what pages have changed and requires creating multiple page builds.
It would be good to be able to build a specific book (top-level topic group), so that you don't have to end up building lots of individual pages, while at the same time avoiding the >>2GB full preview build.
Most books are <25MB, so just building a single book could require 1/100th of the resources versus a full preview.
Book sizes: