mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
17 lines
835 B
Python
17 lines
835 B
Python
"""Django app configuration for warehouse_sources."""
|
|
|
|
from django.apps import AppConfig
|
|
|
|
|
|
class WarehouseSourcesConfig(AppConfig):
|
|
name = "products.warehouse_sources.backend"
|
|
label = "warehouse_sources"
|
|
|
|
def ready(self) -> None:
|
|
# Connect the external-data-source / -schema activity-log receivers at app-population. They
|
|
# used to wire in as an import side effect of the viewset modules; the lazy API router no
|
|
# longer pulls that, so a process that never builds the router (notably the Temporal data
|
|
# import workflows, which mutate these models heavily) would drop audit logs. They live in a
|
|
# light activity_logging module because both viewsets pull in dlt via the data-import chain.
|
|
from products.warehouse_sources.backend import activity_logging # noqa: F401, PLC0415
|