cms/tibi-svelte-starter
Template
5
0
Fork 2
Code Issues Pull Requests Actions Projects Releases Wiki Activity

chore: STAGING_PATH entfernt, ci-starter-defaults für Template-Staging

Browse Source 
- STAGING_PATH aus .env und Makefile (media-sync-local-to-staging) entfernt, Doku bereinigt
- scripts/ci-starter-defaults.sh löst __PLACEHOLDER__ im CI-Workspace auf, dev/master bleiben identisch
This commit is contained in:
Sebastian Frank
2026-10-05 16:40:16 +00:00
parent 0004bc98a1
commit 4ba3cab451
7 changed files with 70 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/skills/tibi-project-setup/SKILL.md
+1 -1
View File
@@ -119,7 +119,7 @@ Important:
- if `GET /api/v1/project` with `X-Admin-Token: $ADMIN_TOKEN` returns `permission denied: admin token lacks permission project.read`, that token is not valid for project registration
- create new projects by logging in with `admin` / `admin` in the default starter dev setup and using the returned JWT via `X-Auth-Token`
- `ADMIN_ASSET_VERSION` is required so Nova picks up the current admin bundle
- `PROJECT_NAME`, `TIBI_NAMESPACE`, `PRODUCTION_PATH`, and `STAGING_PATH` should be project-specific before the first deploy
- `PROJECT_NAME`, `TIBI_NAMESPACE`, and `PRODUCTION_PATH` should be project-specific before the first deploy
- `package.json` should no longer advertise the starter repository or default package name once the project is bootstrapped
## Step 4 — Install and start the Docker stack