fairagro-middleware-api-local-offline
Local offline Middleware API stand-in for harvester and sql-to-arc tests: enough /v3 harvest HTTP for
ApiClient.harvest_arcs, writes each accepted ARC under a configurable directory (no CouchDB, RabbitMQ, or DataHUB).
Install
uv add fairagro-middleware-api-local-offline
# or: pip install fairagro-middleware-api-local-offline
Pair with fairagro-middleware-api-client in consumer test suites.
Run (CLI)
# local_offline.yaml — do not reuse a production API config
log_level: INFO
output_root: /data/arcs
middleware-api-local-offline --config local_offline.yaml --port 8000
# Optional: --host 0.0.0.0 when the process must accept connections from other containers
Point ApiClient at http://127.0.0.1:8000 and assert on files under output_root.
In-process (pytest / ASGI)
from pathlib import Path
from middleware.api_local_offline import LocalOfflineConfig, create_local_offline_app
app = create_local_offline_app(LocalOfflineConfig(output_root=Path("/tmp/arcs")))
Config
Only stand-in fields are accepted (extra=forbid). Keys such as couchdb, celery, and arc_store are rejected so a
production Middleware YAML cannot be loaded by mistake.
Metadata
Release files for fairagro-middleware-api-local-offline 14.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fairagro_middleware_api_local_offline-14.1.0.tar.gz | 8.8 kB | Without provenance | Details for fairagro_middleware_api_local_offline-14.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fairagro_middleware_api_local_offline-14.1.0-py3-none-any.whl | Python 3 | none | any | Details for fairagro_middleware_api_local_offline-14.1.0-py3-none-any.whl |
Total release size: 17.5 kB
Release files / fairagro_middleware_api_local_offline-14.1.0.tar.gz
| Download URL | fairagro_middleware_api_local_offline-14.1.0.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08ea6c3a419225087622392b52fb3c1c30f353f7beb2b56104390204878d110a
|
|
BLAKE2b-256 checksum How to use checksums |
d846ac9a4f75a1fc3ce496a50e06c477a30cf6ea369eac333a33ff1518e333da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / fairagro_middleware_api_local_offline-14.1.0-py3-none-any.whl
| Download URL | fairagro_middleware_api_local_offline-14.1.0-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
65392ad1f851fd441a304418cd95bd27a2e3d2630f1631689276df1b34e204b4
|
|
BLAKE2b-256 checksum How to use checksums |
3f966185db5895d8d580abe932d8a9d4dfe5d2b2931293e0264248f89246ee4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for fairagro-middleware-api-local-offline 14.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.