generated from bisco/codex-bootstrap
feat: bootstrap HoopScout scouting app
This commit is contained in:
+34
-9
@@ -1,13 +1,38 @@
|
||||
# Operations
|
||||
|
||||
Describe operational procedures.
|
||||
## Startup
|
||||
|
||||
Include:
|
||||
```bash
|
||||
docker compose up --build
|
||||
```
|
||||
|
||||
- startup and shutdown;
|
||||
- health checks;
|
||||
- logs;
|
||||
- monitoring;
|
||||
- backup and restore;
|
||||
- routine maintenance;
|
||||
- known operational risks.
|
||||
## Shutdown
|
||||
|
||||
```bash
|
||||
docker compose down
|
||||
```
|
||||
|
||||
## Health Checks
|
||||
|
||||
The PostgreSQL container has a `pg_isready` healthcheck. Backend and frontend smoke checks are manual in the MVP:
|
||||
|
||||
- backend: open `http://localhost:8000/admin/`;
|
||||
- frontend: open `http://localhost:4200/`.
|
||||
|
||||
## Logs
|
||||
|
||||
```bash
|
||||
docker compose logs backend
|
||||
docker compose logs frontend
|
||||
docker compose logs db
|
||||
```
|
||||
|
||||
## Backup and Restore
|
||||
|
||||
No automated backup is configured for the MVP. Use `pg_dump` from the database container before preserving real scouting data.
|
||||
|
||||
## Known Operational Risks
|
||||
|
||||
- The frontend uses the Angular development server and is not production hardened.
|
||||
- Role-specific permissions are modeled but not yet enforced per action.
|
||||
- External data ingestion is intentionally not automated yet.
|
||||
|
||||
Reference in New Issue
Block a user