stapel-booking
Composite preset for bookable resources (coworking, equipment rental, scheduled services): wires stapel-calendar (availability/slots) and stapel-listings (the resource) into one INSTALLED_APPS/urls/config bundle. Mounts no urls and writes no business logic of its own — the app slot is reserved for future cross-module glue (MODULE.md, preset.py).
Part of the Stapel framework — composable Django apps that deploy as a monolith or as microservices without changing module code.
Install
pip install stapel-booking
At a glance
| Fact | Value |
|---|---|
| Version | 0.1.5 |
| Python | >=3.11 (3.11, 3.12, 3.13, 3.14) |
| Fleet dependencies | stapel-calendar · stapel-listings |
Documentation
capabilities.json · llms.txt (for agents)
Assemble (one line)
pip install stapel-tools
stapel-assemble mybooking --libs booking
cd mybooking && make test
That expands booking through the STAPEL_LIBS requires
closure and wires every member module into INSTALLED_APPS,
requirements.txt, urls.py and CONFIG.MD, then runs the verify gates.
Manual wiring (no scaffold)
# settings.py
from stapel_booking import preset
INSTALLED_APPS = [
# ... django/stapel-core baseline (incl. stapel_core.django.projections)
"stapel_calendar",
"stapel_listings",
"stapel_booking",
]
for _k, _v in preset.SETTINGS_DEFAULTS.items():
globals().setdefault(_k, _v)
# urls.py
from django.urls import include, path
urlpatterns = [
path("calendar/", include("stapel_calendar.urls")),
path("listings/", include("stapel_listings.urls")),
]
Config checklist (fill these, in the generated project's CONFIG.MD too)
| Key | Note |
|---|---|
STAPEL_CALENDAR[...] |
presets/slots — see stapel-calendar CONFIG.MD |
STAPEL_LISTINGS["BASE_CURRENCY"] |
default USD — set your currency |
STAPEL_LISTINGS["DEFAULT_LISTING_TTL_DAYS"] |
default 30 (a bookable resource usually wants None) |
License
MIT — see LICENSE.
This page is assembled by stapel-readme from docs/readme.md plus the contract artifacts in docs/. Edit the prose in docs/readme.md; the badges, facts and links above and below it are generated — do not hand-edit README.md.
Metadata
Release files for stapel-booking 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| stapel_booking-0.1.5.tar.gz | 11.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| stapel_booking-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.4 kB
Release files / stapel_booking-0.1.5.tar.gz
| Download URL | stapel_booking-0.1.5.tar.gz |
|---|---|
| Size | 11.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9d1d6b93b7b3a4942a082a7bb85c1e830fe62c2e1fafc7311bf78fc974fbcb6
|
|
BLAKE2b-256 checksum How to use checksums |
4552c61b68b94cfd0be47f38272557a26234682bab5b80230c4d4c7249971a4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logRelease files / stapel_booking-0.1.5-py3-none-any.whl
| Download URL | stapel_booking-0.1.5-py3-none-any.whl |
|---|---|
| Size | 13.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
675abe15f4990a58d97e27d458a5b7643abc05b399e1bda51f80123055993776
|
|
BLAKE2b-256 checksum How to use checksums |
2129f2609074746e502de1e8ee5127d2479d2232923e4f4edefa27bd069e1733
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency log