The Servala Self-Service Portal
Find a file
Tobias Brunner c6c078c5c2
All checks were successful
Build and Deploy Staging / build (push) Successful in 45s
Build and Deploy Staging / deploy (push) Successful in 7s
gitignore local tmp folder
2025-03-21 15:00:45 +01:00
.forgejo use separate token for staging deployment 2025-03-21 14:34:17 +01:00
deployment/kustomize no kubernetes probes during development 2025-03-21 14:59:12 +01:00
docker configure uv cache to support openshift 2025-03-21 14:24:21 +01:00
docs move over documentation from old place 2025-03-11 15:37:13 +01:00
src configure csrf trusted origins 2025-03-21 14:59:37 +01:00
.dockerignore dont include local sqlite file in docker build 2025-03-21 14:24:21 +01:00
.env.example Add auth configuration to .env and settings.py 2025-03-16 10:33:34 +01:00
.gitignore gitignore local tmp folder 2025-03-21 15:00:45 +01:00
.pre-commit-config.yaml add a pre-commit configuration 2025-03-07 09:21:48 +01:00
.python-version uv + Django[postgres] installation 2025-03-05 10:44:16 +01:00
Dockerfile properly support staticfiles in docker 2025-03-21 14:24:21 +01:00
LICENSE Initial commit 2025-03-03 15:26:47 +00:00
Makefile initial Antora boilerplate 2025-03-10 09:23:18 +01:00
playbook.yml initial Antora boilerplate 2025-03-10 09:23:18 +01:00
pyproject.toml Add django-rules 2025-03-20 15:36:40 +01:00
README.md document deployment to staging 2025-03-21 14:24:37 +01:00
uv.lock Add django-rules 2025-03-20 15:36:40 +01:00

Servala Portal

Servala Logo

The Servala Self-Service Portal

Documentation

Available at https://docs.servala.com/.

The project documentation is written in AsciiDoc and built with Antora. It's automatically packaged and deployed by the CI/CD pipeline found in .forgejo/workflows/docs.yaml.

Paths:

  • docs/modules/ROOT/pages: Documentation pages
  • docs/modules/ROOT/assets/images: Images to be included in the documentation pages
  • docs/modules/ROOT/nav.adoc: Site navigation (new pages need to be added there)

Writing documentation is best done by running make docs-preview and connecting to the site at http://localhost:2020/. The browser add-on LiveReload - Web extension will help while editing with automated page reload in the browser.

Development setup

First, copy the .env.example file to .env and adjust the settings to your needs. Make sure to source the file before running any commands.

Then use uv to install the project and run its commands while youre developing:

uv sync --dev
uv run src/manage.py migrate
uv run src/manage.py runserver

This will start the development server on http://localhost:8000.

Configuration

Configuration happens using environment variables. See the available parameters in .env.example.

Code style and linting

Servala uses several linters / formatters to keep the project style consistent for you. Run them like this:

uv run black src/  # Code formatting; -c to just check
uv run isort src/  # Import ordering; -c to just check
uv run djlint src/ --reformat --format-js --format-css  # Format templates, JS and CSS, --check to just check
uv run flake8 src/  # Python linter

The repository features a pre-commit configuration which helps to properly format the source code before committing. It's recommended to install and use it.

Docker

The project provides a Dockerfile which builds a production-ready container image. It uses Caddy to serve static files and connect to Gunicorn, the Python WSGI application server.

Building:

docker build -t local/servala-portal .

Running:

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

Then access it with http://localhost:8080/ and the Django admin with http://localhost:8080/admin

Deployment

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 to account for differences between the deployment stages. Stages are configured with overlays in deployment/kustomize/overlays/$environment.

Testing

TODO