deploy · mediatracker · Tangled

mediatracker deploy

13 files

Erican · Plugin system, first step: contract, manifest, loader, core plugin, admin page · 1w ago

Pages as a capability of a source (pages), steered by the policy and the administration, instead of a flag and a configuration list

Split the deployment into a package script and a server-side install script

anime-seasons.compose.yml

Anime Seasons feed service, publish tool, deployment files

Plugin system, first step: contract, manifest, loader, core plugin, admin page

jikan.compose.yml

MyAnimeList through Jikan-Edge: a second flavor of the Jikan API, and the default

Feed Studio deployment: images, standalone compose file, flat STUDIO_* variables (mapper with tests; the DID is derived from the API address), package script

Merge main into worktree-popfeed-tap

package-studio.sh

Frontend layout: apps/mediatracker, apps/studio and packages/ui under one workspace root, each app with its own TypeScript project, config and Dockerfile; plural text forms of the shared texts moved with their keys

Frontend layout: apps/mediatracker, apps/studio and packages/ui under one workspace root, each app with its own TypeScript project, config and Dockerfile; plural text forms of the shared texts moved with their keys

Version API and frontend together from the git tags

studio.compose.yml

Feed Studio under /api as well: ForwardedPrefixMiddleware shared (Administration.AspNetCore), Studio auth redirect keeps the path base, proxy also forwards /.well-known/did.json, STUDIO_API_UPSTREAM default in studio.compose.yml, Vite proxy and relative apiBaseUrl for the Studio frontend

studio.env.example

Feed Studio under /api as well: ForwardedPrefixMiddleware shared (Administration.AspNetCore), Studio auth redirect keeps the path base, proxy also forwards /.well-known/did.json, STUDIO_API_UPSTREAM default in studio.compose.yml, Vite proxy and relative apiBaseUrl for the Studio frontend

Version API and frontend together from the git tags