fix: derive app-name at runtime; template expansion breaks ${{ }} expressions
Some checks failed
/ checks (push) Successful in 36s
/ deploy (push) Failing after 30s
Some checks failed
/ checks (push) Successful in 36s
/ deploy (push) Failing after 30s
This commit is contained in:
parent
b2fd2618fb
commit
d2e4b76610
3 changed files with 3 additions and 4 deletions
|
|
@ -1,6 +1,5 @@
|
||||||
package.json
|
package.json
|
||||||
README.md
|
README.md
|
||||||
.env.example
|
.env.example
|
||||||
.forgejo/workflows/ci.yaml
|
|
||||||
migrations/0001_init.sql
|
migrations/0001_init.sql
|
||||||
package-lock.json
|
package-lock.json
|
||||||
|
|
|
||||||
|
|
@ -20,10 +20,10 @@ jobs:
|
||||||
- uses: actions/checkout@v4
|
- uses: actions/checkout@v4
|
||||||
- uses: http://192.168.1.230:3000/nholtware/workflows/build-push@main
|
- uses: http://192.168.1.230:3000/nholtware/workflows/build-push@main
|
||||||
with:
|
with:
|
||||||
app-name: ${REPO_NAME}
|
app-name: ${{ github.event.repository.name }}
|
||||||
registry-user: ${{ secrets.REGISTRY_USER }}
|
registry-user: ${{ secrets.REGISTRY_USER }}
|
||||||
registry-token: ${{ secrets.REGISTRY_TOKEN }}
|
registry-token: ${{ secrets.REGISTRY_TOKEN }}
|
||||||
- uses: http://192.168.1.230:3000/nholtware/workflows/gitops-bump@main
|
- uses: http://192.168.1.230:3000/nholtware/workflows/gitops-bump@main
|
||||||
with:
|
with:
|
||||||
app-name: ${REPO_NAME}
|
app-name: ${{ github.event.repository.name }}
|
||||||
gitops-token: ${{ secrets.GITOPS_TOKEN }}
|
gitops-token: ${{ secrets.GITOPS_TOKEN }}
|
||||||
|
|
|
||||||
|
|
@ -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). The 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`, and the first migration (CI derives the app name from the repo name itself).
|
||||||
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.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue