Skip to main content

stapel-social

CI coverage pypi downloads python license llms.txt

Composite preset for a social surface around any entity: wires stapel-chat (messaging), stapel-profiles (user profiles) and stapel-reviews into one INSTALLED_APPS/urls/config bundle. Mounts no urls and writes no business logic of its own (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-social

At a glance

Fact Value
Version 0.1.6
Python >=3.11 (3.11, 3.12, 3.13, 3.14)
Fleet dependencies stapel-chat · stapel-profiles · stapel-reviews

Documentation

capabilities.json · llms.txt (for agents)

Likes/favourites are NOT included yet: stapel-engagement does not exist. They arrive as a MINOR bump of this composite once it does.

Assemble (one line)

pip install stapel-tools
stapel-assemble mysocial --libs social
cd mysocial && make test

That expands social 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_social import preset

INSTALLED_APPS = [
    # ... django/stapel-core baseline (incl. stapel_core.django.projections)
    "stapel_chat",
    "stapel_profiles",
    "stapel_reviews",
    "stapel_social",
]
for _k, _v in preset.SETTINGS_DEFAULTS.items():
    globals().setdefault(_k, _v)

# urls.py
from django.urls import include, path

urlpatterns = [
    path("chat/", include("stapel_chat.urls")),
    path("profiles/api/", include("stapel_profiles.urls")),
    path("reviews/", include("stapel_reviews.urls")),
]

Config checklist (fill these, in the generated project's CONFIG.MD too)

Key Note
STAPEL_REVIEWS["TARGET_TYPES"] prefilled by stapel_social.preset.SETTINGS_DEFAULTS (targets profile)
STAPEL_CHAT[...] see stapel-chat CONFIG.MD
STAPEL_PROFILES[...] see stapel-profiles CONFIG.MD

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-social 0.1.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for stapel-social 0.1.6
File Size Uploaded
stapel_social-0.1.6.tar.gz 12.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for stapel-social 0.1.6
File Interpreter ABI Platform
stapel_social-0.1.6-py3-none-any.whl Python 3 none any Details

Total release size: 26.1 kB

Release files / stapel_social-0.1.6.tar.gz

Download URL stapel_social-0.1.6.tar.gz
Size 12.2 kB
Tags Source
SHA-256 checksum
How to use checksums
759be07fd2dc128dc3d147eaed6d4e86e961df66d8cd42564589c39ad093b46f
BLAKE2b-256 checksum
How to use checksums
01ed478e75ce984084d6bc08fd01980b37d59ce7db390c087327c9cfa57d5942
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

Release files / stapel_social-0.1.6-py3-none-any.whl

Download URL stapel_social-0.1.6-py3-none-any.whl
Size 13.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
629e489e0049517f9f36f1c177306e4ae7f6dc7db21c53f481afa9075e5fdf8e
BLAKE2b-256 checksum
How to use checksums
e4560387359df3cd07819228c6dfff3b52d034f62aeabd85b4707479ccd02be0
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

Release history Release notifications | RSS feed

This release

0.1.6 This release

2 release files

0.1.5

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page