Admin
cf8ac706b6
Removes every wrapper script under deploy/ (up.ps1, up.sh, scripts/*,
zitadel/provision.*) and folds their logic into three one-shot services
in compose.yml, following the pattern already used by seaweedfs-init:
keys-init generates the RS256 stream-ticket key pair
migrate applies the EF Core migrations (backend/Musify.Migrator.Dockerfile)
zitadel-init creates the Musify project + OIDC apps, writes the client
ids back into the active env file
Deploying is now two plain `docker compose` commands, no scripts to run
or chmod:
docker compose -f deploy/compose.yml -f deploy/compose.dev.yml up -d
docker compose -f deploy/compose.yml -f deploy/compose.dev.yml --profile apps up -d --build
(swap compose.dev.yml for compose.prod.yml + --env-file deploy/.env.prod
for production). The first command brings up infra and lets the bootstrap
jobs run to completion; the second builds and starts the apps, which by
then read real OIDC values instead of empty ones — compose interpolates
${VAR} once per invocation, so this can't collapse into a single command
without the apps reading their own config file at container start instead
of via compose env (out of scope here).
Also:
- DatabaseDesignTimeFactory now also reads Database__ConnectionString
from the environment, and DesignSettings.json is optional, so the new
migrate container works without user-secrets or a config file excluded
from the Docker build context by .dockerignore.
- nginx's depends_on no longer lists the apps-profile services: it does
not need them at its own startup (every vhost resolves its upstream at
request time via the embedded Docker resolver), and requiring them made
`compose.prod.yml up -d` (without --profile apps) an invalid project.
- env_get/env_set in zitadel-init strip \r: the mounted env file can have
CRLF line endings on Windows, which otherwise makes an empty-looking
value non-empty to `[ -z ... ]`. .env.example/.env.prod.example are
pinned to LF via .gitattributes for the same reason. Also fixed:
rewriting the bind-mounted env file in place instead of renaming a temp
file over it (rename onto a bind-mounted inode fails with "Resource
busy").
- Removed compose.share.yml and zitadel/.output-share/ — a "temporary"
personal overlay that had leaked a real Zitadel service-account PAT
into git history (committed in 70968b3). That token should be rotated.
- Removed deploy/.tmp/ from .gitignore: nothing mounts or creates it
anymore (it never actually did, either — no compose service referenced
it, only the now-removed up.ps1 did).
Verified end-to-end with Docker: a clean `down -v` + fresh `up -d` +
`--profile apps up -d --build` on the dev stack brings up all four one-shot
jobs successfully and all four apps healthy (api/gateway return 200,
worker starts its consumers with no errors, web-player responds). Also
verified compose.prod.yml starts nginx cleanly with dummy certs and no
apps running, confirming the depends_on fix.
36 lines
1.2 KiB
Markdown
36 lines
1.2 KiB
Markdown
# web-player
|
|
|
|
Musify's web client: SvelteKit 2 (`adapter-node`), Svelte 5 runes, Tailwind 4,
|
|
TypeScript. Authentication is server-side OIDC against Zitadel (`openid-client`
|
|
and `jose`) with an encrypted session cookie; the backend is called from `load`
|
|
functions and form actions through a typed `openapi-fetch` client.
|
|
|
|
## Development
|
|
|
|
```sh
|
|
npm install
|
|
npm run dev # :5173
|
|
```
|
|
|
|
Configuration lives in `.env` (template in `.env.example`). Bring the
|
|
infrastructure stack up first (see [../deploy/README.md](../deploy/README.md))
|
|
and copy the `WEB_CLIENT_ID` / `WEB_CLIENT_SECRET` it writes to `deploy/.env`
|
|
into this `.env` once, then run the dev server.
|
|
|
|
```sh
|
|
npm run check # svelte-check — must be clean before closing a change
|
|
npm run lint # prettier --check . && eslint .
|
|
npm run format # prettier --write .
|
|
npm run build # production build into build/
|
|
npm run gen:api # regenerate src/lib/api/schema.d.ts from the running API
|
|
```
|
|
|
|
## Production
|
|
|
|
Built and run as a container by the production stack — see
|
|
[../deploy/README.md](../deploy/README.md). There the same variables come from
|
|
`deploy/.env.prod` through compose instead of from `.env`.
|
|
|
|
Conventions and the design system are documented in [CLAUDE.md](CLAUDE.md) and
|
|
in the `musify-web` skill.
|