From a4ec1eda782aaa3c81da1d45893a0e39ec372e5c Mon Sep 17 00:00:00 2001 From: Will Estes Date: Sat, 11 Jul 2026 05:13:59 -0400 Subject: [PATCH] Point the new-domain runbook at the campaigns-template repo Generate-from-template replaces copy-from-an-existing-repo now that campaigns-template exists, so onboarding always starts from a known- clean structure instead of whatever the last content repo happened to drift to. Co-Authored-By: Claude Sonnet 5 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2264c0f..5422f03 100644 --- a/README.md +++ b/README.md @@ -107,8 +107,8 @@ A starting template (listmonk's own stock `default.tpl`, with the required `{{ U Each domain/client gets its own content repo, isolated by ordinary Gitea repo permissions — a client with push access to their repo has no path to any other domain's listmonk credentials, because those credentials simply don't exist in their repo. -1. Create a new Gitea repo (e.g. `-campaigns`), private. -2. Add: an empty `campaigns/` directory, `email-templates/campaign.html` (copy the stock template from an existing content repo, or listmonk's own `static/email-templates/default.tpl`), and `.gitea/workflows/{sync,send,test,sync-template}.yml` copied from an existing content repo — each does `go install gitea.reground.org/will/eec-campaigns@` then runs the corresponding subcommand, with that repo's own secrets. +1. Generate a new repo from [`campaigns-template`](https://gitea.reground.org/will/campaigns-template) (Gitea's "Generate Repo," not a clone/fork — it starts the new repo with its own clean history), private. +2. Follow that generated repo's README checklist: rename the default-template name, restyle `email-templates/campaign.html` if needed, add secrets, confirm the tool version pin, run `Sync default campaign template` once, replace the README with a short domain-specific one. 3. Add repo secrets: `CAMPAIGNS_LISTMONK_BASE_URL`, `CAMPAIGNS_LISTMONK_API_USER`, `CAMPAIGNS_LISTMONK_API_TOKEN`, and optionally `CAMPAIGNS_PREVIEW_EMAIL` — scoped to that domain's own listmonk instance and API user. 4. Manually run the `Sync default campaign template` workflow once before the first real send.