> For the complete documentation index, see [llms.txt](https://jembi.gitbook.io/openhim-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jembi.gitbook.io/openhim-platform/packages/analytics-datastore-clickhouse/local-development.md). # Local Development ### Launching Launching this package executes the following two steps: * Running Clickhouse service * Running config importer to run the initial SQL script ### Initializing ClickHouse The config importer will be launched to run a NodeJS script after ClickHouse has started. It will run SQL queries to initialize the tables and the schema, and can also include initial seed data if required. The config importer looks for two files `clickhouseTables.js` and `clickhouseConfig.js` found in `/analytics-datastore-clickhouse/importer/config.` For specific implementation, this folder can be overridden. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://jembi.gitbook.io/openhim-platform/packages/analytics-datastore-clickhouse/local-development.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.