build(deployment): use sibling repos as docker build context
This commit is contained in:
33
README.md
Normal file
33
README.md
Normal file
@@ -0,0 +1,33 @@
|
||||
# Qlockify Deployment
|
||||
|
||||
This repository is the deployment layer only.
|
||||
|
||||
It does not contain application source copies. Docker builds read directly from the sibling repositories:
|
||||
|
||||
- `../qlockify-backend`
|
||||
- `../qlockify-frontend`
|
||||
|
||||
## Local structure
|
||||
|
||||
The expected directory layout is:
|
||||
|
||||
```text
|
||||
Qlockify/
|
||||
qlockify-backend/
|
||||
qlockify-frontend/
|
||||
qlockify-deployment/
|
||||
```
|
||||
|
||||
## Deployment flow
|
||||
|
||||
1. Configure deployment env files:
|
||||
- `./.env`
|
||||
- `./backend/.env`
|
||||
- `./frontend/.env`
|
||||
2. From `qlockify-deployment`, build and start the stack:
|
||||
|
||||
```powershell
|
||||
docker compose up --build
|
||||
```
|
||||
|
||||
The backend container runs database migrations and `collectstatic` on startup, then serves Django with Gunicorn using `config.wsgi:application`.
|
||||
Reference in New Issue
Block a user