cliver-playbook-app-basic
Foundations package of the cliver-playbook library — everything a service needs before business code: layered settings, the process runtime, and one runnable API slice.
What is inside
| Area | Path (under src/cliver_playbook/app/basic/) |
Notes |
|---|---|---|
| Settings | settings.py |
Layered: env > .env > runtime overrides > app.yaml (Jinja2) > defaults. Subclass Settings to extend (ADR-0016). |
| Runtime | runtime.py |
configure(settings) binds settings + async engine once per process; nothing is built at import time. |
| Runtime settings | runtime_settings.py |
Package-owned settings sections: field description, validation, live apply, app_settings persistence and the lifespan overlay (ADR-0021). |
| Routers | api/routes.py |
ROUTERS: list[APIRouter] — a composed app includes them (ADR-0015). |
| Demo slice | api/items.py, services/, schemas/, models/entities.py |
Full CRUD example: the items table and /api/v1/items. Optional — delete together with its migration and tests. |
| Migrations | alembic/ |
Own chain, version table alembic_version_basic; creates items and app_settings. |
| Application | app.py, __main__.py |
create_app() and python -m cliver_playbook.app.basic. |
Install
python -m pip install -e . # from this directory
# consuming project, same virtualenv (dependency first, then this):
python -m pip install -e ../cliver-playbook-app-basic
Editable installs of sibling packages coexist in one virtualenv: the
cliver_playbook and cliver_playbook.app namespace directories are
PEP 420 — deliberately no __init__.py — so every package's portion merges.
Run standalone
docker compose up -d db # or point CLIVER_DATABASE_URL at PostgreSQL
python -m cliver_playbook.app.basic --reload
# GET /api/v1/health, /api/v1/version, /api/v1/items
Configuration resolves relative to the current working directory: the nearest
ancestor containing app.yaml or .env is the application root (CLIVER_CONFIG_FILE
overrides). See settings.py and config_yaml.py.
Migrate
python -c "from cliver_playbook.app.basic.alembic import run_migrations_online; run_migrations_online()"
# interactive, from this directory:
alembic upgrade head
Test
python -m pytest # needs PostgreSQL; creates and drops a temp database
Metadata
Release files for cliver-playbook-app-basic 0.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 | |
|---|---|---|---|---|
| cliver_playbook_app_basic-0.1.0.tar.gz | 33.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cliver_playbook_app_basic-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 71.6 kB
Release files / cliver_playbook_app_basic-0.1.0.tar.gz
| Download URL | cliver_playbook_app_basic-0.1.0.tar.gz |
|---|---|
| Size | 33.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
57d6d4a73d40c010ae903b2701939c076c60bc32f3135841fed8d5419c83fa8b
|
|
BLAKE2b-256 checksum How to use checksums |
e403cf6bcd448df9678d920ecd4a37440d85d481025eedbd41ac6d429b0d3cf1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.9 {"installer":{"name":"uv","version":"0.12.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / cliver_playbook_app_basic-0.1.0-py3-none-any.whl
| Download URL | cliver_playbook_app_basic-0.1.0-py3-none-any.whl |
|---|---|
| Size | 37.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2967bcd9998abdb876767e558d4bd94d8cbeeac8099a987b62870231243641d5
|
|
BLAKE2b-256 checksum How to use checksums |
db907e6a1a14e51a85a4e2de5ad9af232865fa61658921737fbe1ac47418551a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.9 {"installer":{"name":"uv","version":"0.12.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for cliver-playbook-app-basic 0.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.