Go to file
Csaba 6f019020ea
All checks were successful
Amarillo/amarillo-gitea/amarillo-core/pipeline/head This commit looks good
Added error logging to file in logging.conf
2024-03-06 09:50:49 +01:00
amarillo Added error logging to file in logging.conf 2024-03-06 09:50:49 +01:00
.gitignore [#4] Passwords in AgencyConf model 2024-02-28 09:34:13 +01:00
Dockerfile Added secret_key variable to Dockerfile 2024-03-06 09:20:28 +01:00
Jenkinsfile Only deploy from main branch 2024-02-16 14:58:39 +01:00
MANIFEST.in rename /app to /amarillo 2024-02-13 10:47:03 +01:00
pyproject.toml Basic OAuth2 authentication 2024-02-26 10:59:09 +01:00
README.md rename /app to /amarillo 2024-02-13 10:47:03 +01:00
requirements.txt Basic OAuth2 authentication 2024-02-26 10:59:09 +01:00

Amarillo

CRUD for carpool offers

An Amarillo is a yellow-dressed person helping others to find a car pool in Cuba.

Setup

  • Python 3.9.2 with pip
  • python3-venv

Create a virtual environment python3 -m venv venv.

Activate the environment and install the dependencies pip install -r requirements.txt.

Run uvicorn amarillo.main:app.

In development, you can use --reload.

Environment Variables

  • env
  • ADMIN_TOKEN

Security

All endpoints are protected by an API-Key in the HTTP header. There is a special admin user. For this user, the API-Key must be passed in as an environment variable when Amarillo is started.

The admin can create additional API-Keys in the /agencyconf endpoint. This endpoint is always available but not always shown in /docs, especially not when running in production. The Swagger docs for /agencyconf can be seen on the MFDZ demo server.

Permissions work this way

  • the admin is allowed to call all operations on all resources. Only the admin can create new API-Keys by POSTing an AgencyConf JSON object to /agencyconf.
  • API-Keys for agencies are allowed to POST/PUT/GET/DELETE their own resources and GET some public resources.

Development

GTFS-RT python bindings

In case you modify or update the proto-files in amarillo/proto, you'll need to regenerate the python bindings. First, create the python files:

$ cd amarillo/proto
$ protoc --version
libprotoc 3.21.6
$ protoc --proto_path=. --python_out=../services/gtfsrt gtfs-realtime.proto realtime_extension.proto
$ sed 's/import gtfs_realtime_pb2/import amarillo.services.gtfsrt.gtfs_realtime_pb2/g' ../services/gtfsrt/realtime_extension_pb2.py | sponge ../services/gtfsrt/realtime_extension_pb2.py

Testing

In the top directory, run pytest amarillo/tests.

Docker

Based on tiangolo/uvicorn-gunicorn:python3.9-slim

  • build docker build -t amarillo --build-arg="PLUGINS=amarillo-metrics" .
  • run docker run --rm --name amarillo -p 8000:80 -e MAX_WORKERS="1" -e ADMIN_TOKEN=$ADMIN_TOKEN -e RIDE2GO_TOKEN=$RIDE2GO_TOKEN -e TZ=Europe/Berlin -v $(pwd)/data:/app/data amarillo