feat/wiki-astro #214
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "feat/wiki-astro"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Three hiccups from the wiki.clawdie.si deployment (26.jun.2026): 1. Placeholder cert — nginx refuses to start when ssl_certificate files dont exist yet. Create a temporary self-signed cert first, then acme.sh --issue overwrites it with the real cert. 2. ACME challenge location ordering — nginx matches location blocks in order. .well-known/acme-challenge/ MUST come before the location / { return 301 https://... } redirect, otherwise ACME validation returns 301 instead of the challenge file. 3. acme.sh --key-file + --fullchain-file — these flags write directly to the nginx SSL paths, replacing the placeholder. The cert paths must match between nginx config and acme.sh invocation. New "Adding a new public static HTTPS site — full flow" section covers the complete pattern: DNS first → placeholder cert → vhost with ordered locations → real cert → content deploy → renewal. Two new troubleshooting entries: BIO_new_file() failed (missing cert), ACME challenge 404/301 (location ordering or missing directory).Positive framing — each former "pitfall" is now a prescriptive step: 1. Quote all YAML frontmatter values 2. Declare content-path constants inside getStaticPaths() 3. Create explicit routes for SL content 4. Clean the dist cache before every build 5. Resolve content paths with path.resolve("src/content") 6. Extract markdown H1 as a title fallback 7. Placeholder TLS cert for first deploy (reference) Every step follows Why → What → Result. No "broken/failed/symptom/cause" language. An agent reading this gets a recipe, not a post-mortem.nginx: broken config→valid config, fails→reports error, won't start→status check, BIO_new_file() failed→certificate file missing, common causes→things to check setup: broken/missing→needs repair, failed to load→need build tools, fix each→resolve each, Common causes→What to check update: broken state→consistent state, tests fail→tests don't pass, unfixable→not immediately resolvable, won't start→needs attention astro: fails because→requires docs-deployment: broken→needs rollback, Check for broken symlinks→Verify symlinks887696e1c6tod002e480c3