lyrathorpeandEmma Thorpe
f1e1373fd3
Build and publish container / build (push) Successful in 6m4s
## What - `pyproject.toml` — setuptools metadata with a `legacy-email-proxy` console script. Runtime dependencies are read dynamically from `requirements.txt`, so the Docker build and the package cannot drift apart. - `proxy_server.run()` — a synchronous entry point for that console script; `main` is a coroutine and cannot be referenced by one. The `__main__` path behaves as before. - `flake.nix` / `package.nix` — the package, `overlays.default`, a dev shell, and `checks`. The pytest suite runs as part of the build. - `module.nix` — a NixOS module: `services.legacy-email-proxy` with freeform `settings` (environment variables) and a separate `environmentFile` for credentials, so secrets stay out of the Nix store. Runs under `DynamicUser`, takes `CAP_NET_BIND_SERVICE` only while a listener is on a privileged port, and opens no firewall ports. - README: pip install, Nix usage, and a NixOS service example. ## Why The proxy could only be consumed as a container. Anyone deploying it on NixOS had to vendor a package definition into their own configuration — which is exactly what happened downstream, and is now deleted there in favour of this. ## Not in scope - The `Dockerfile` and its CI workflow are untouched. - No Nix job in CI; the runner has no Nix. The build is reproducible locally with `nix flake check`. - `version` is static and tracks the latest tag (`0.3.0`); bump it with the tag. ## Verification - `nix flake check` — package builds, 14 tests pass inside the build. - Consumed from a downstream NixOS host with `--override-input`: the unit's `ExecStart` resolves to the module's own build, and that flake's checks pass too. --------- Co-authored-by: Emma Thorpe <emma.thorpe@citrix.com> Reviewed-on: #16
26 lines
703 B
TOML
26 lines
703 B
TOML
[build-system]
|
|
requires = ["setuptools>=77"]
|
|
build-backend = "setuptools.build_meta"
|
|
|
|
[project]
|
|
name = "legacy-email-proxy"
|
|
version = "0.3.0"
|
|
description = "Unauthenticated POP3/SMTP front end proxied to authenticated IMAPS/SMTPS backends"
|
|
readme = "README.md"
|
|
requires-python = ">=3.12"
|
|
dynamic = ["dependencies"]
|
|
|
|
[project.scripts]
|
|
legacy-email-proxy = "proxy_server:run"
|
|
|
|
[project.urls]
|
|
Homepage = "https://code.emmathe.dev/lyrathorpe/legacy-email-proxy"
|
|
|
|
# requirements.txt stays the single source of runtime dependencies, so the
|
|
# Dockerfile and this file cannot drift apart.
|
|
[tool.setuptools.dynamic]
|
|
dependencies = { file = ["requirements.txt"] }
|
|
|
|
[tool.setuptools]
|
|
py-modules = ["proxy_server"]
|