From b7d4410cf0c2adcd4495408e28fd7e56400d6dc6 Mon Sep 17 00:00:00 2001 From: yeasy Date: Thu, 23 Jul 2026 17:14:19 -0700 Subject: [PATCH] fix(build): drop the _site_site workaround that mdPress 0.8.1 made obsolete MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The build script anticipated an older mdPress behaviour where a shared --output made the site land in a sibling directory, then moved it back: mdpress build --format site --output _site && rm -rf _site && mv _site_site _site mdPress 0.8.1 writes straight into --output, so the sibling never appears and the mv aborts the step: ✓ Generated site → .../docker_practice/_site/index.html mv: cannot stat '_site_site': No such file or directory Caught by a smoke test after 0.8.1 shipped, before any content push fanned it out — this repo is the only one with a live copy of the workaround (the three matches in other repos are inside gitignored _book/ build artifacts). The site itself built fine; only the post-processing dance failed. --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 012c9a0..9c1db51 100644 --- a/package.json +++ b/package.json @@ -9,7 +9,7 @@ "scripts": { "test": "node scripts/check_metadata.js && python3 -m unittest tools.test_prepare_pdf_sources && python3 -m unittest discover -s tests -p 'test_*.py' && python3 tools/test_examples.py", "mdpress:help": "mdpress --help", - "build": "rm -rf _site _site_site && mdpress build --format site --output _site && rm -rf _site && mv _site_site _site", + "build": "rm -rf _site && mdpress build --format site --output _site", "serve": "mdpress serve", "start": "mdpress serve", "pdf": "rm -rf /tmp/docker_practice-pdf-src && python3 tools/prepare_pdf_sources.py --book-dir . --out /tmp/docker_practice-pdf-src && cd /tmp/docker_practice-pdf-src && mdpress build --format pdf --output \"${INIT_CWD:-$PWD}/docker_practice.pdf\""