Skip to main content

License: MIT Python Framework: Django Package Manager: Rye PyPI Version Latest on Django Packages Tests: pytest CI Code Style: PEP 8 PyPI Provenance

django_octo is the modular core orchestrator for the Django-Octo framework ecosystem. It unifies decoupled runtime modules under a single installation entrypoint, providing automated environment discovery, live Dual-Channel observability, and event-driven cumulative versioning.

Designed to remain completely agnostic to domain logic, this core hub dynamically detects active satellite modules installed in the runtime environment (importlib.util.find_spec + importlib.metadata) and mounts their administrative and public surfaces without manual wiring or tight coupling.


Key Architectural Features

  • Zero-Config Environment Auto-Discovery: Exposes get_installed_octo_apps() and dynamic URL mounting (include("django_octo.urls")), automatically registering only the satellite modules present in the active virtual environment.
  • Automated Control Hub (/octo/): Built-in zero-dependency observability dashboard that introspects installed modules, displays live semantic versions, and bridges direct access between public channels and the Django Admin panel.
  • Event-Driven Cumulative Versioning: Driven by repository_dispatch webhooks from satellite CI/CD pipelines. Every release published in a satellite module automatically increments the core version queue, updates CHANGELOG.md, validates cross-module coupling tests, and publishes a verified release to PyPI via OIDC Trusted Publishing.
  • Rye Environment Integration: Fully integrated with the Rust-based Python package manager for deterministic dependency locking across the entire ecosystem.

Ecosystem Architecture & Dual-Channel Topology

flowchart TB
    subgraph Satellites["🛰️ Decoupled Satellite Modules"]
        SEO["django-octo-seo<br/>(Semantic & JSON-LD Engine)"]
        SEC["django-octo-security<br/>(CVE & HTTP Posture Engine)"]
        EXT["Future Octo Modules<br/>(Extensible Plugin Slot)"]
    end

    subgraph Core["🍁 django-octo Core Orchestrator"]
        REG["Runtime Introspection<br/>(registry.py)"]
        HUB["Control Hub UI<br/>(/octo/)"]
        SYNC["Cumulative Version Engine<br/>(scripts/sync_version.py)"]
    end

    SEO -.->|repository_dispatch| SYNC
    SEC -.->|repository_dispatch| SYNC
    EXT -.->|repository_dispatch| SYNC

    SEO --> REG
    SEC --> REG
    EXT --> REG

    REG --> HUB
    HUB -->|Public Surface| PUB["🌐 Unified Public Routes"]
    HUB -->|Control Surface| ADM["🔐 Unified Django Admin"]

Orchestrated Ecosystem

Module Package Architectural Role Public Surface Control Surface
django-octo Core Orchestrator & Runtime Hub /octo/ Unified INSTALLED_APPS & urls.py
django-octo-seo 8-Layer Semantic & JSON-LD Engine /seo-demo/ /admin/ (SEO Models)
django-octo-security) Zero-Dependency CVE & HTTP Posture /security-audit/ /admin/ (CVE Checker)

Installation & Quick Start (PyPI)

Install the entire unified ecosystem into any modern Django (>=6.1.2) and Python (>=3.12) project using pip or Rye:

1. Install Core Package

pip install django-octo

Or using the Rust-backed Rye package manager:

rye add django-octo

2. Auto-Register Apps & Migrate

Use get_installed_octo_apps() in your settings.py to automatically load the orchestrator alongside every detected satellite module:

from django_octo import get_installed_octo_apps

INSTALLED_APPS = [
    "django.contrib.admin",
    "django.contrib.auth",
    "django.contrib.contenttypes",
    "django.contrib.sessions",
    "django.contrib.messages",
    "django.contrib.staticfiles",
    *get_installed_octo_apps(),
]

Apply all unified database migrations in a single pass:

python3 manage.py migrate

3. Mount the Unified Router

Include django_octo.urls in your root urls.py to expose the Control Hub and all active module endpoints simultaneously:

from django.contrib import admin
from django.urls import include, path

urlpatterns = [
    path("admin/", admin.site.urls),
    path("", include("django_octo.urls")),
]

Start the server (python3 manage.py runserver) and navigate to http://127.0.0.1:8000/ to inspect the live Control Hub.


Local Sandbox & Development Setup (Using Rye)

git clone https://github.com/jeanpmodev/django_octo/
cd django_octo
rye sync
rye test

License & Ecosystem Blueprint

Distributed under the permissive terms of the MIT License.

Metadata

Release files for django-octo 0.1.9

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

Source distribution (sdist)

Source distribution for django-octo 0.1.9
File Size Uploaded Provenance Actions
django_octo-0.1.9.tar.gz 9.0 kB With provenance Details for django_octo-0.1.9.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for django-octo 0.1.9
File Interpreter ABI Platform Actions
django_octo-0.1.9-py3-none-any.whl Python 3 none any Details for django_octo-0.1.9-py3-none-any.whl

Total release size: 17.1 kB

Release files / django_octo-0.1.9.tar.gz

Download URL django_octo-0.1.9.tar.gz
Size 9.0 kB
Tags Source
SHA-256 checksum
How to use checksums
15748f7b06b25568ac58a409b56b13d33ab6f19d4047422931a4bd0f7654625e
BLAKE2b-256 checksum
How to use checksums
617ba5f0e2348b032966b6e5568934f816d56bf608668a2911816a22142dfccd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 15, 2026.

Transparency log

Release files / django_octo-0.1.9-py3-none-any.whl

Download URL django_octo-0.1.9-py3-none-any.whl
Size 8.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
02bcbb467f9c2d4773b7746c91192eed04bf8a0452004c206aa6063af86ce339
BLAKE2b-256 checksum
How to use checksums
b02e30ff80e2bf4bc03b228398415c863f64c513c222da4e122bfaeb71103c64
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 15, 2026.

Transparency log

Security for django-octo 0.1.9

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for django_octo-0.1.9.tar.gz

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 Nov 15, 2026.

Transparency log

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.

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