servala/servala-portal
3
0
Fork 0
Code Issues 23 Pull requests 1 Projects 1 Releases Packages 2 Activity Actions

document deployment to staging

Browse source
This commit is contained in:
Tobias Brunner 2025-03-21 14:05:33 +01:00
parent 07812efe82
commit f2580675a0
No known key found for this signature in database
1 changed files with 10 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -35,9 +35,10 @@ uv run src/manage.py runserver
This will start the development server on http://localhost:8000. This will start the development server on http://localhost:8000.
### Configuration ## Configuration
TODO Configuration happens using environment variables.
See the available parameters in `.env.example`.
## Code style and linting ## Code style and linting
@ -69,13 +70,18 @@ Running:
```bash ```bash
docker run --rm -ti -p 8080:8080 --name=servala-portal --rm --env-file .env local/servala-portal docker run --rm -ti -p 8080:8080 --name=servala-portal --rm --env-file .env local/servala-portal
docker exec -it servala-portal uv run src/manage.py createsuperuser
``` ```
TODO: Persistence Then access it with http://localhost:8080/ and the Django admin with http://localhost:8080/admin
## Deployment ## Deployment
TODO The code is automatically built and deployed on a push to the main branch.
See `.forgejo/workflows/build-deploy-staging.yaml` for the actual workflow.
Deployment files are in the `deployment/kustomize` folder and makes use of [Kustomize](https://kustomize.io/) to account for differences between the deployment stages.
Stages are configured with overlays in `deployment/kustomize/overlays/$environment`.
## Testing ## Testing