Waters-Church/visit.waterschurch.org
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: point README at the Gitea repository

Browse Source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Waters Church
2026-09-22 16:58:35 -04:00
co-authored by Claude Fable 5.1
parent 78cd0cc550
commit d0506aa473
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6 -5
View File
@@ -91,12 +91,13 @@ so the build targets the lowest common denominator that every cPanel account sup
If Waters Church later confirms Node hosting, the frontend needs no change; the PHP layer could be If Waters Church later confirms Node hosting, the frontend needs no change; the PHP layer could be
swapped for route handlers, but there is no functional reason to. swapped for route handlers, but there is no functional reason to.
## Working in this Google Drive folder ## Source of truth: Gitea
This repo lives in a Google Drive shared drive. `node_modules/` is large and churns Drive sync; The repository lives at `Waters-Church/visit.waterschurch.org` on the church's Gitea
`.next/` and `out/` are symlinked to `~/.local/share/visit-waterschurch/` for that reason (`ssh://git@chronicles-ab.waterschurch.org:3022/Waters-Church/visit.waterschurch.org.git`).
(`npm install` insists on a real `node_modules`). If you clone elsewhere, delete the two symlinks Clone it to a normal local folder (for example `~/Sites/visit.waterschurch.org`); do not develop
first: `rm .next out`. inside Google Drive, which fights with `node_modules` and build output. The original copy in the
"Websites" shared drive is kept only as a snapshot and is no longer updated.
## Facts and placeholders ## Facts and placeholders