blob: fd0e3e5d6e9e3b1ada5bfb79bccccc1c3ba8f15d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
---
title: "Website Publishing Pipeline"
date: "2026-07-31"
---
HOW THIS SITE GETS BUILT AND DEPLOYED
--------------------------------------------------
## STACK
- Quarto renders every `.qmd` to both HTML and plain text
- nginx on the VPS does user-agent detection:
`curl` gets `.txt`, browsers get `.html`
- `deploy.sh` builds `public/` and rsyncs to the VPS
## SOURCE OF TRUTH
The repo is self-contained and public — browse the
source or clone it:
- Web: [git.jayrup.me](https://git.jayrup.me)
- Clone: `git clone https://git.jayrup.me/git/homepage.git`
`blog/` holds these posts as flat `.qmd` files;
`blog/index.qmd` is the listing page, newest first.
## PUBLISHING
1. Write `blog/<slug>.qmd` with title + date frontmatter
2. Add a numbered entry to `blog/index.qmd`
3. Commit + push to meru — the post-receive hook renders
the site in a Docker container and rsyncs it to the
VPS automatically
4. Verify: `curl https://jayrup.me/blog/<slug>`
## WHY THIS WORKS
`deploy.sh` finds every `.qmd` recursively, so new
posts are built with zero script changes. nginx's
`try_files` cascade resolves `/blog/<slug>` to the
`.txt` for curl and the `.html` for browsers.
--------------------------------------------------
BACK: [BLOG](https://jayrup.me/blog) | [HOME](https://jayrup.me)
|
