summaryrefslogtreecommitdiff
path: root/f3s/docs
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2026-04-08 15:24:30 +0300
committerPaul Buetow <paul@buetow.org>2026-04-08 15:24:30 +0300
commit8918a61f5e2c37e1ccc89f47787e8f2cede0c1d0 (patch)
tree60636c4442337f2045c68e0c7e5b0ae45bb78c8b /f3s/docs
parent4a5cf5327adc603e8b09d8941974549990425558 (diff)
d0: document PI phase 1.2 static content sync
Diffstat (limited to 'f3s/docs')
-rw-r--r--f3s/docs/pi-phase-1-2.md24
1 files changed, 24 insertions, 0 deletions
diff --git a/f3s/docs/pi-phase-1-2.md b/f3s/docs/pi-phase-1-2.md
new file mode 100644
index 0000000..febb422
--- /dev/null
+++ b/f3s/docs/pi-phase-1-2.md
@@ -0,0 +1,24 @@
+# PI Phase 1.2 Static Content Sync on pi0/pi1
+
+Task 1.2 for the Raspberry Pi cluster was completed on:
+
+- `pi0.lan.buetow.org` as the source content node
+- `pi1.lan.buetow.org` as the synchronized target
+
+Completed actions:
+
+- Created `/var/www/html/index.html` on `pi0` with the static farm landing page content
+- Synchronized the `pi0` content tree to `pi1` with `rsync`
+- Preserved the source content as the reference copy on `pi0`
+- Did not install a cron job, because the plan marked it optional and this task did not require it
+
+Verification:
+
+- `curl -fsS http://localhost` on `pi0` and `pi1` returned the same page content hash
+- `sha256sum /var/www/html/index.html` on `pi0` and `pi1` returned the same hash
+- Both hosts produced `97667da1e299f54b9831532171f1980f214018001770cecbe5de1bc127aa1552`
+
+Notes:
+
+- The source node initially had no `index.html`, so the landing page was created on `pi0` before syncing.
+- `pi0` could not resolve `pi1.lan.buetow.org` for an outbound peer-to-peer rsync, so the final sync used the workstation as a relay while still treating `pi0` as the source of truth.