Fill in client-specific values from eec-courses-template

Swaps __CLIENT__/__DOMAIN__ placeholders for twosquirrelspress/
eec-twosquirrelspress/twosquirrelspress.com.

.gitea/workflows/sync.yml

@@ -13,8 +13,8 @@ jobs:
         run: |
           tar czf /tmp/courses.tar.gz courses
           status=$(curl -s -o /tmp/sync-response.json -w '%{http_code}' \
-            -X POST "http://eec-__CLIENT__:8080/admin/sync" \
+            -X POST "http://eec-twosquirrelspress:8080/admin/sync" \
-            -H "Authorization: Bearer ${__CLIENT___EEC_SYNC_TOKEN}" \
+            -H "Authorization: Bearer ${TWOSQUIRRELSPRESS_EEC_SYNC_TOKEN}" \
             --data-binary @/tmp/courses.tar.gz)
           cat /tmp/sync-response.json
           echo
@@ -23,4 +23,4 @@ jobs:
             exit 1
           fi
         env:
-          __CLIENT___EEC_SYNC_TOKEN: ${{ secrets.__CLIENT___EEC_SYNC_TOKEN }}
+          TWOSQUIRRELSPRESS_EEC_SYNC_TOKEN: ${{ secrets.TWOSQUIRRELSPRESS_EEC_SYNC_TOKEN }}

README.md

@@ -1,9 +1,9 @@
-# __CLIENT__-eec-courses
+# twosquirrelspress-eec-courses
 
 Course content for [eec](https://gitea.reground.org/will/eec), the self-paced
-email course engine — this instance served at eec.__DOMAIN__. Push to
+email course engine — this instance served at eec.twosquirrelspress.com.
-`master` and CI syncs `courses/` straight to production — there's no staging
+Push to `master` and CI syncs `courses/` straight to production — there's no
-step, so treat a push here the same as a push to `eec` itself.
+staging step, so treat a push here the same as a push to `eec` itself.
 
 Full reference for course/step file format, `course.yml` fields, the
 readiness step, drip-triggered courses, and sync guardrails lives in the
@@ -24,16 +24,7 @@ courses/
 ## Deploying
 
 Push to `master` → `.gitea/workflows/sync.yml` tars up `courses/` and
-`POST`s it to this domain's `eec-__CLIENT__` container over the internal
+`POST`s it to this domain's `eec-twosquirrelspress` container over the internal
-Docker network, authenticated with `__CLIENT___EEC_SYNC_TOKEN` (a Gitea
+Docker network, authenticated with `TWOSQUIRRELSPRESS_EEC_SYNC_TOKEN` (a Gitea Actions secret
-Actions secret shared with the `eec-__CLIENT__` Ansible role's copy). No
+shared with the `eec-twosquirrelspress` Ansible role's copy). No separate deploy step, no
-separate deploy step, no staging — a push here goes live immediately.
+staging — a push here goes live immediately.
-
----
-
-**Generating a new client repo from this template:**
-
-1. Gitea → "Generate Repo" from this template repo's page, named `<client>-eec-courses`.
-2. Find/replace `__CLIENT__` → the client's slug (must match the `eec-<client>` container name) and `__DOMAIN__` → the client's domain, in this README and in `.gitea/workflows/sync.yml`.
-3. Add the `<CLIENT>_EEC_SYNC_TOKEN` Actions secret to the new repo (Gitea does not carry secrets over from a template) — value must match the `eec-<client>` Ansible role's copy.
-4. Delete this "Generating a new client repo" section from the new repo's README once done.