init studio admin backend
This commit is contained in:
@@ -0,0 +1,38 @@
|
||||
# Autonomy Studio Admin Backend
|
||||
|
||||
NestJS + Prisma backend for Studio Admin.
|
||||
|
||||
## Stack
|
||||
|
||||
- NestJS
|
||||
- Prisma
|
||||
- PostgreSQL
|
||||
- local k3s integration through `kubectl`
|
||||
|
||||
## Local setup
|
||||
|
||||
```bash
|
||||
npm install
|
||||
cp .env.example .env
|
||||
docker compose up -d
|
||||
npm run prisma:generate
|
||||
npm run start:dev
|
||||
```
|
||||
|
||||
## k3s connection
|
||||
|
||||
For local k3s, keep `KUBECONFIG` empty if `kubectl` already points to the target cluster.
|
||||
Otherwise set it explicitly:
|
||||
|
||||
```bash
|
||||
KUBECONFIG=/etc/rancher/k3s/k3s.yaml
|
||||
```
|
||||
|
||||
Runtime APIs use `kubectl` for the first implementation:
|
||||
|
||||
- `GET /api/runtime/namespaces`
|
||||
- `GET /api/runtime/workloads`
|
||||
- `POST /api/runtime/workloads/:namespace/:kind/:name/restart`
|
||||
- `POST /api/runtime/workloads/:namespace/:kind/:name/scale`
|
||||
- `GET /api/runtime/workloads/:namespace/:kind/:name/logs`
|
||||
- `GET /api/runtime/events`
|
||||
Reference in New Issue
Block a user