Hwaro::Config::Options::BuildOptions
Inherits Struct / Value / Object
Constructors
Instance methods
When set (dev-server only), render only the homepage + the N most
recent pages on the initial pass; the remaining pages are stashed
on the Builder and rendered by a background fiber after the server
is already serving. Drops "ready" time on large sites from O(all)
to O(N). Always paired with fast_start_count.
When set (dev-server only), render only the homepage + the N most
recent pages on the initial pass; the remaining pages are stashed
on the Builder and rendered by a background fiber after the server
is already serving. Drops "ready" time on large sites from O(all)
to O(N). Always paired with fast_start_count.
Keep existing output files between rebuilds. Used by hwaro serve's
watch-triggered rebuilds so repeated full rebuilds don't wipe the
already-processed resized images (see ImageHooks#process_images
mtime-skip logic, which only works when destinations survive).
Keep existing output files between rebuilds. Used by hwaro serve's
watch-triggered rebuilds so repeated full rebuilds don't wipe the
already-processed resized images (see ImageHooks#process_images
mtime-skip logic, which only works when destinations survive).
True when this build is being run as part of hwaro serve (dev server).
Hooks can use this to change behavior (e.g. lazy OG generation).
True when this build is being run as part of hwaro serve (dev server).
Hooks can use this to change behavior (e.g. lazy OG generation).
Number of concurrent render workers (fibers) for the parallel render
phase. 0 = auto (CPU-based, the default). Lowering it (e.g. --jobs 2)
reduces effective render parallelism, which on template/Crinja-heavy
sites is often FASTER: those pages allocate many small objects, and
past ~2 workers Boehm's global allocation lock contends harder than
the extra cores help. Markdown-heavy sites keep scaling, so the
default stays auto. Never changes output — only render concurrency.
Number of concurrent render workers (fibers) for the parallel render
phase. 0 = auto (CPU-based, the default). Lowering it (e.g. --jobs 2)
reduces effective render parallelism, which on template/Crinja-heavy
sites is often FASTER: those pages allocate many small objects, and
past ~2 workers Boehm's global allocation lock contends harder than
the extra cores help. Markdown-heavy sites keep scaling, so the
default stays auto. Never changes output — only render concurrency.