configure bumpver for versoning
All checks were successful
Tests / test (push) Successful in 22s

This commit is contained in:
Tobias Brunner 2025-04-14 13:19:55 +02:00
parent 55f6169562
commit 9e4b820757
No known key found for this signature in database
5 changed files with 144 additions and 2 deletions

View file

@ -4,6 +4,8 @@
The Servala Self-Service Portal
Latest release: 2025.04.14-0
## Documentation
Available at https://docs.servala.com/.
@ -86,11 +88,34 @@ Then access it with http://localhost:8080/ and the Django admin with http://loca
## Deployment
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`.
### Staging
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`.
### Production
Building and deployment for production happens when a Git tag is pushed.
### Versioning
We're using `CalVer` as the versioning scheme.
The tool [bumpver](https://github.com/mbarkhau/bumpver) helps us to automate the process.
To cut a new release run the following command to check what will happen:
```bash
uv run bumpver update -d
```
The run the following command to create a release:
```bash
uv run bumpver update
```
## Maintenance and management commands