build: migrate backend dependency management to uv

Author: krab1k

.github/workflows/backend.yml

@@ -21,23 +21,18 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v5
 
-      - name: Setup Python
-        uses: actions/setup-python@v5
+      - name: Setup uv
+        uses: astral-sh/setup-uv@v7
         with:
-          python-version: "3.13"
+          version: "0.12.19"
+
+      - name: Install system dependencies
+        run: apt-get update && apt-get install -y --no-install-recommends ca-certificates python3-dev libpq-dev gcc
 
       - name: Install dependencies
-        run: |
-          apt-get update && apt-get install -y curl python3.13-dev libpq-dev gcc
-          python -m pip install --upgrade pip
-          curl -sSL https://install.python-poetry.org | python3 -
-          export PATH="/github/home/.local/bin:$PATH"
-          echo "$HOME/.local/bin" >> $GITHUB_PATH # allow poetry to be used in next step
-          poetry env use python3.13
-          poetry install --no-interaction --no-root
+        run: uv sync --locked --no-python-downloads --python /usr/bin/python3
         working-directory: ./src/backend
 
       - name: Run tests
-        run: |
-          poetry run pytest ./tests
+        run: uv run --no-sync pytest ./tests
         working-directory: ./src/backend

.gitignore

@@ -2,6 +2,7 @@ __pycache__
 .idea
 /.mypy_cache/
 **/venv
+**/.venv
 .vscode
 .devcontainer
-build/
+build/

docs/backend/db/README.md

@@ -15,13 +15,13 @@ Migrations are handled by `alembic`, with related code being located [here](../.
 ### Creating a new migration
 ```bash
 $ cd src/backend/app
-$ poetry run alembic revision --autogenerate -m "<migration name>"
+$ uv run --no-sync alembic revision --autogenerate -m "<migration name>"
 ```
 
 ### Running migrations
 ```bash
 $ cd src/backend/app
-$ poetry run alembic upgrade head
+$ uv run --no-sync alembic upgrade head
 ```
 
 ## Updating the database schema

src/backend/.python-version

@@ -2,27 +2,23 @@ FROM chargefw2-base:acc
 
 USER root
 
-ENV POETRY_HOME=/opt/poetry
-ENV POETRY_VIRTUALENVS_CREATE=false
-ENV PATH="/opt/poetry/bin:$PATH"
+COPY --from=ghcr.io/astral-sh/uv:0.12.19 /uv /usr/local/bin/uv
+
+ENV UV_PYTHON_DOWNLOADS=never
+ENV UV_PROJECT_ENVIRONMENT=/opt/venv
+ENV PATH="/opt/venv/bin:$PATH"
 
 RUN apt-get update && \
     apt-get install -y --no-install-recommends \
     ca-certificates \
-    curl \
     gcc \
     python3-dev \
     libpq-dev && \
     apt-get clean && rm -rf /var/lib/apt/lists/*
 
-# Install Poetry
-RUN curl -sSL https://install.python-poetry.org | python3 - && \
-    poetry config virtualenvs.create false
-
-
 WORKDIR /acc
-COPY poetry.lock pyproject.toml ./
-RUN poetry install --no-interaction --no-ansi --no-root
+COPY uv.lock pyproject.toml ./
+RUN uv sync --locked --no-cache --python /usr/bin/python3
 
 COPY ./app /acc/app
 COPY ./entrypoint.sh /acc/

src/backend/Dockerfile

@@ -26,18 +26,18 @@ $ cmake .. -DCMAKE_INSTALL_PREFIX=<WHERE-TO-INSTALL> -DPYTHON_MODULE=ON
 All required environment variables are located in the [.env file](./app/.env) except `OIDC_CLIENT_ID` and `OIDC_CLIENT_SECRET` (required for Life Science auth, can be ignored for local setup). All used environment variables are described in [docs](../../docs/backend/README.md). How to obtain the abovementioned environment variables is also mentioned [here](../../docs/backend/life-science/README.md). 
 
 ### Installing dependencies
-ACC III uses [Poetry](https://python-poetry.org/) for depencency management.
+ACC III uses [uv](https://docs.astral.sh/uv/) for dependency management. Docker and CI use uv 0.12.19.
 
-#### Install Poetry
+#### Install uv
 ```bash
-$ curl -sSL https://install.python-poetry.org | python3 -
+$ curl -LsSf https://astral.sh/uv/0.12.19/install.sh | sh
 ```
 
 #### Install project dependencies
-*Note:* Poetry will automatically create a virtual environment inside the project before the installation. Configured [here](./poetry.toml).
+uv creates a `.venv` in the backend directory and installs the versions recorded in `uv.lock`. Use Python 3.13 or newer, matching the Python version used to build your ChargeFW2 bindings. Docker uses Ubuntu's Python and does not download another interpreter.
 
 ```bash
-$ poetry install
+$ uv sync --locked --no-python-downloads --python python3
 ```
 
 ### Startup
@@ -53,13 +53,13 @@ $ cd app
 
 After the database is ready, we need to run migrations:
 ```bash
-$ poetry run alembic upgrade head
+$ uv run --no-sync alembic upgrade head
 ```
 
 API can now be started just by running the main file:
 
 ```bash
-$ poetry run gunicorn --workers 4 --worker-class uvicorn.workers.UvicornWorker main:web_app
+$ uv run --no-sync gunicorn --workers 4 --worker-class uvicorn.workers.UvicornWorker main:web_app
 ```
 
 API runs by default on `--bind 127.0.0.1:8000`. Documentation (Swagger) is available on `/docs`. Alternatively you can use Redoc available on `/redoc`.