Update migration instructions in README
All checks were successful
PostgreSQL Compatibility Matrix / PG14 smoke (push) Successful in 7s
PostgreSQL Compatibility Matrix / PG15 smoke (push) Successful in 7s
PostgreSQL Compatibility Matrix / PG16 smoke (push) Successful in 7s
PostgreSQL Compatibility Matrix / PG17 smoke (push) Successful in 7s
PostgreSQL Compatibility Matrix / PG18 smoke (push) Successful in 7s

Removed redundant migration step and clarified that migrations run automatically on backend container startup. Updated related sections for better clarity and consistency.
This commit is contained in:
2026-02-12 16:42:23 +01:00
parent 8e5a549c2c
commit 4bc178b720

View File

@@ -96,13 +96,7 @@ python -c "from cryptography.fernet import Fernet; print(Fernet.generate_key().d
make up make up
``` ```
4. Run migrations: 4. Open the application:
```bash
make migrate
```
5. Open the application:
- Frontend: `http://<SERVER_IP>:<FRONTEND_PORT>` - Frontend: `http://<SERVER_IP>:<FRONTEND_PORT>`
- API base: `http://<SERVER_IP>:<BACKEND_PORT>/api/v1` - API base: `http://<SERVER_IP>:<BACKEND_PORT>/api/v1`
@@ -119,9 +113,11 @@ Initial admin bootstrap user (created from `.env` if missing):
make up # build and start all services make up # build and start all services
make down # stop all services make down # stop all services
make logs # follow compose logs make logs # follow compose logs
make migrate # run alembic upgrade head in backend container make migrate # optional/manual: run alembic upgrade head in backend container
``` ```
Note: Migrations run automatically when the backend container starts (`entrypoint.sh`).
## Configuration Reference (`.env`) ## Configuration Reference (`.env`)
### Application ### Application