nholtware/service-template-express
Template
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

docs: avoid substituting the variable name in README
Some checks failed
/ checks (push) Successful in 36s
/ deploy (push) Failing after 2s

Browse source
This commit is contained in:
nholtware 2026-11-05 01:44:31 -06:00
parent 2828a630a6
commit b2fd2618fb
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -22,7 +22,7 @@ Logs: one JSON object per line on stdout (`level,time,msg,service,version`, plus
## Using this template ## Using this template
1. **Generate** a repo from this template in Forgejo (public). `${REPO_NAME}` is substituted into `package.json`, this README, `.env.example`, the CI workflow, and the first migration. 1. **Generate** a repo from this template in Forgejo (public). The repo name is substituted into `package.json`, this README, `.env.example`, the CI workflow, and the first migration.
2. **Set 3 Actions secrets** on the new repo: `REGISTRY_USER` (`nholtware`), `REGISTRY_TOKEN` (registry push token), `GITOPS_TOKEN` (ci-bot gitops token). 2. **Set 3 Actions secrets** on the new repo: `REGISTRY_USER` (`nholtware`), `REGISTRY_TOKEN` (registry push token), `GITOPS_TOKEN` (ci-bot gitops token).
3. **Add gitops entries**: render `templates/backend/` (see its README) into `manifests/<app>/` and add `apps/<app>.yaml` in `nholtware/gitops`. 3. **Add gitops entries**: render `templates/backend/` (see its README) into `manifests/<app>/` and add `apps/<app>.yaml` in `nholtware/gitops`.
4. **Push** to `main`. Generating a repo emits no push event, so CI only starts on your first push. 4. **Push** to `main`. Generating a repo emits no push event, so CI only starts on your first push.