chore: adapt Dockerfile/compose for standalone server repo
- Dockerfile no longer bakes in a Flutter web build (this repo has no client/ dir); the web bundle is mounted at runtime instead. - docker-compose.yml: web bundle mount path configurable via WEB_CLIENT_BUILD_PATH, defaults to a sibling KC-APP checkout. - README: point to the KC-APP client repo for clients. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
# KC-App Backend
|
||||
|
||||
NestJS API for the KC-App platform (see repo root README + plan for
|
||||
architecture context).
|
||||
NestJS API for the KC-App platform. Split out of the main KC-APP monorepo
|
||||
(https://git.konfi-castle.com/linus/KC-APP); the Flutter clients live there.
|
||||
|
||||
## Setup
|
||||
|
||||
|
||||
Reference in New Issue
Block a user