Note in index.html how a change here reaches the web and the apps
Build apps / build (push) Failing after 35s
Deploy web to NAS / deploy (push) Successful in 1m21s

This directory feeds both targets by different routes, and the difference is the
thing people get wrong: the website serves it directly, while the apps carry a
copy frozen at build time. Someone editing here reasonably assumes a deploy is
enough, and for the website it is.

Written at the top of the file rather than in a README because this is where the
assumption gets made.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Waters Church
2026-09-24 15:50:35 -04:00
co-authored by Claude Opus 5
parent 7d75fa9e83
commit b03fb252d8
+8
View File
@@ -1,4 +1,12 @@
<!DOCTYPE html> <!DOCTYPE html>
<!-- This directory is the source of truth for both the website and the apps. The website
serves it directly; mobile/scripts/sync-web.js copies it into the iOS and Android
bundles at build time, so the apps carry a FROZEN copy taken when they were last built.
A change here therefore reaches the two in different ways: pushing to main redeploys
the website within a minute, and separately rebuilds both apps on the ingest Mac and
emails that they are behind — but nothing reaches a phone until someone runs
./release.sh --ios --android and the stores approve it. -->
<html lang="en"> <html lang="en">
<head> <head>
<meta charset="UTF-8"> <meta charset="UTF-8">