Files
insights/.run/Plugin Server.run.xml
zeekay 2e29e0db21 rename: it is Hanzo Datastore everywhere, not ClickHouse
The fork half-carried the upstream vendor's name: env vars had been moved to
DATASTORE_*, but every module path, identifier and doc string underneath still
said ClickHouse. A fork that reads like someone else's product in every import
is a vendored copy that never got renamed.

  insights/clickhouse/            -> insights/datastore/
  insights/insightsql/functions/  -> .../functions/datastore/
  products/live_debugger/backend/ -> .../backend/datastore/
  docker/, docs/handbook/         -> datastore/
  CLICKHOUSE_* identifiers        -> DATASTORE_* (164 files)
  manage.py migrate_clickhouse    -> migrate_datastore
  prose, comments, docstrings     -> Datastore (1000+ files)

The ORM moved with it: hanzoai/infi.clickhouse_orm now ships `datastore_orm`,
so consumers write `from datastore_orm import ...` rather than threading the
original vendor's `infi` org namespace through their imports. Repinned here to
that revision.

MIGRATION HISTORY. A package rename orphans the history table, because it keys
on package_name: the runner then sees zero applied migrations, replays from
0001 and dies on 0026. That already happened once here, silently blocking every
datastore migration until the rows were re-keyed by hand. So the rename carries
its own fixup — migrate_datastore now adopts history from prior package names
before migrating, idempotent and a no-op on a fresh database, with the list of
former names as the single place a future rename has to touch. The history
TABLE name is unchanged: it is persisted state, and renaming it is a data
migration rather than a rename.

Left with the vendor's name, because they are the vendor's: clickhouse-driver,
clickhouse-pool and clickhouse-connect are third-party PyPI packages we do not
fork, CLICKHOUSE_SKIP_USER_SETUP and CLICKHOUSE_SERVER_IMAGE configure the
upstream server image, and clickhouse.com doc links point at the real engine's
documentation.

Verified: 4257 Python files parse with 0 syntax errors, no `insights.clickhouse`
or `infi.clickhouse` references survive, and clickhouse_pool/_driver imports are
untouched.
2026-07-26 08:44:50 -07:00

17 lines
662 B
XML

<component name="ProjectRunConfigurationManager">
<configuration default="false" name="Plugin Server" type="js.build_tools.npm">
<package-json value="$PROJECT_DIR$/nodejs/package.json" />
<command value="run" />
<scripts>
<script value="start:dev" />
</scripts>
<node-interpreter value="project" />
<envs>
<env name="DATASTORE_SECURE" value="False" />
<env name="DATABASE_URL" value="postgres://insights:insights@localhost:5432/insights" />
<env name="KAFKA_HOSTS" value="localhost:9092" />
<env name="OBJECT_STORAGE_ENABLED" value="True" />
</envs>
<method v="2" />
</configuration>
</component>