Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/backtest-kit/backtest-ollama-crontab/llms.txt

Use this file to discover all available pages before exploring further.

Every runtime value that changes between deployments — database addresses, API credentials, trading symbols — is read from process.env at startup. During local development the dotenv-cli package injects values from a .env file before each npm run command, so no code change is ever needed to switch environments. In production the same variables are supplied directly by the host environment (Docker, a cloud scheduler, or a shell export).

​
Getting Started

Copy .env.example to .env in the project root and fill in the values that differ from the defaults: 
cp .env.example .env
The shipped example already overrides the two most common settings for a Docker-based local setup:
.env.example
CC_REDIS_HOST=host.docker.internal
CC_MONGO_CONNECTION_STRING=mongodb://host.docker.internal:27017/backtest-kit?wtimeoutMS=15000
Variables that are not present in .env fall back to their hard-coded defaults: most are defined in packages/core/src/config/params.ts, while CC_SYMBOL_LIST is defined in packages/main/src/config/params.ts. The sections below document each variable in full.

​
Variable Reference

​
Database

​
Caching

​
Telegram

The default values for CC_TELEGRAM_API_ID and CC_TELEGRAM_API_HASH are demo credentials bundled for development convenience only. They are subject to strict rate limits and may be blocked for certain channels. Before connecting to any real Telegram channel, register your own application at my.telegram.org and replace these values with your own api_id and api_hash.

​
Ollama

​
Trading

Build docs developers (and LLMs) love

Get started for freeTalk to us