Skip to content

Start using HTML templating#1

Merged
srid merged 3 commits intomasterfrom
html-template
May 9, 2021
Merged

Start using HTML templating#1
srid merged 3 commits intomasterfrom
html-template

Conversation

@srid
Copy link
Copy Markdown
Owner

@srid srid commented May 9, 2021

@srid srid force-pushed the html-template branch from 24debd3 to a8b9d84 Compare May 9, 2021 21:06
@srid srid merged commit c28d11a into master May 9, 2021
@srid srid deleted the html-template branch May 9, 2021 21:06
shivaraj-bh pushed a commit to shivaraj-bh/emanote that referenced this pull request Dec 18, 2023
* WIP use Text.Ginger

* add more template vars

* cleanups
srid added a commit that referenced this pull request Apr 25, 2026
…-only

Two related fixes for nix build .#docs:

1. Add more puppeteer args (--disable-dev-shm-usage, --disable-gpu,
   --disable-crash-reporter, --no-zygote, --single-process) on top of
   --no-sandbox / --disable-setuid-sandbox. The Nix build sandbox lacks
   /dev/shm and IPC capabilities Chromium expects, and the GitHub Actions
   runners we already had to placate. None of these touch sandboxing
   for mmdc's actual rendering — that runs against trusted local source.

2. Stop feeding mermaid render failures into the per-note error list.
   checkBadMarkdownFiles treats anything in there as fatal and calls
   exitFailure, so a single transient Chromium hiccup tanked the whole
   site build. Errors now go to the logger plus the visible inline
   "Mermaid rendering failed:" Para — readers and authors still see
   them at the right granularity, but the build keeps going.

Trade-off: regresses the Hickey-#1 unification of error channels from
the earlier review pass. Worth it: parse errors really should fail the
build, render errors really shouldn't.
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

Successfully merging this pull request may close these issues.

1 participant