Files
twosquirrelspress-eec-courses/README.md
T
will 90961ee7e4
Sync courses / sync (push) Failing after 5s
Fill in client-specific values from eec-courses-template
Swaps __CLIENT__/__DOMAIN__ placeholders for twosquirrelspress/
eec-twosquirrelspress/twosquirrelspress.com.
2026-07-24 07:41:45 -04:00

31 lines
1.1 KiB
Markdown

# twosquirrelspress-eec-courses
Course content for [eec](https://gitea.reground.org/will/eec), the self-paced
email course engine — this instance served at eec.twosquirrelspress.com.
Push to `master` and CI syncs `courses/` straight to production — there's no
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
[`eec-courses`](https://gitea.reground.org/will/eec-courses) README — the
format is identical, only the target instance differs.
## Layout
```
courses/
<slug>/
course.yml
day-0.md
day-1.md
...
```
## Deploying
Push to `master``.gitea/workflows/sync.yml` tars up `courses/` and
`POST`s it to this domain's `eec-twosquirrelspress` container over the internal
Docker network, authenticated with `TWOSQUIRRELSPRESS_EEC_SYNC_TOKEN` (a Gitea Actions secret
shared with the `eec-twosquirrelspress` Ansible role's copy). No separate deploy step, no
staging — a push here goes live immediately.