All Domains
1587 entities found
ConsolidationCard.svelte
Responsive UI component presenting consolidation details with adaptive layouts.
ConsolidationRecommendation
DiscoveryService produces ConsolidationRecommendation to suggest table consolidations for questions. DiscoveryService generates ConsolidationRecommendation for intelligent table consolidation based on questions.
ConsolidationReview.svelte
UI component for reviewing proposed data consolidations with visual cues.
container-per-project
Container-per-project Isolation
Content filtering
Context Window
Limited to about 8,000 tokens; Arctic-Text2SQL-R1-7B encounters truncation with large schemas (490 tables). Reducing max_tables to 3 is planned to mitigate this performance constraint.
Contextual summaries with project context
Requirement to produce file summaries that relate content to project goals; improvements made for relevance.
control questions
System includes QA measures like data provenance tracking, validation, and iterative refinement, supporting quality control.
Conversation memory integration
DataLens Skill integrates conversation memory to maintain context in dialogs.
Coolify
DataLens uses Coolify on the theo server for deploying web frontends, APIs, and supporting infrastructure including PostgreSQL, Redis, Ollama, and Qdrant. It facilitates automated container builds, environment management, and environment variables like ANTHROPIC_API_KEY, ensuring smooth, continuous deployment and updates of the DataLens platform. IronClaw Agent Feature deployment integrates with Coolify for container build and deployment management. The Coolify backend is configured to use IronClawClient in remote mode with appropriate environment variables. ANTHROPIC_API_KEY is required to be set in Coolify environment for OpenClaw to operate successfully without timeout. Backend container depends on Coolify environment variables to have the ANTHROPIC_API_KEY set to function correctly with OpenClaw and Claude. Coolify environment variables provide necessary settings including Anthropic API key to the backend container during deployment. The DataLens platform backend integrates the coolify skill for deployment.
Coolify Application
Docker Deployment integrates with the Coolify Application deployment system. Coolify Application incorporates PostgreSQL for metadata storage and authentication. Coolify Application depends on the Backend for API functionality. Coolify Application depends on the Frontend for user interface.
Coolify auto-deploy
Automated deployment process for DataLens platform updates via Coolify CI/CD system. Auto-deploy via Coolify integrates with the Commit identification and deployment process to automate deployment after pushing the master branch code. Coolify auto-deploy integrates with the Discovery API router deployment process to automate updates.
Coolify container
Coolify daemon
The Coolify daemon integrates with the GitHub API to fetch repository source code during deployment builds.
Coolify deployment
The Coolify deployment uses the Docker-compose configuration for service orchestration. Commit 52eab9a requires deployment via Coolify to enable updated debug logging in process_message function. Container e8f4cd9 runs old code and will be replaced once the commit 52eab9a is successfully deployed via Coolify. Commit 52eab9a requires deployment via Coolify to enable updated debug logging in process_message function. Container e8f4cd9 runs old code and will be replaced once the commit 52eab9a is successfully deployed via Coolify. Coolify deploy manages backend container lifecycle for deployment and code reloads for new features. The async generator exception causing query execution to stop is potentially mitigated or affected by the Coolify deployment status, which may be stuck or slow.
Coolify frontend container
Deployment container for frontend; setup ongoing.
Coolify guide
Coolify Integration
Coolify Integration includes deployment for datalens.exerun.com domain. Coolify Integration includes deployment for api.datalens.exerun.com domain. The production deployment on theo uses the Coolify platform for container orchestration and deployment. The production deployment on theo uses PostgreSQL 16 for metadata storage. The production deployment on theo uses Redis 7 as job queue infrastructure. The Production Deployment on theo includes running the Backend container. The Production Deployment on theo includes running the PostgreSQL container. The deployment on theo lacks local GPU features, which constrains the availability of AI features like DS-STAR and Ollama inference. DataLens Project integrates with Coolify for deployment management and environment configuration.
Coolify server
DataLens Platform deployment depends on Coolify server for production hosting. Coolify server integrates with Ollama running on elin server at port 11434. Coolify server integrates with Qdrant running on elin server at port 6333. Coolify server uses DS-STAR agents located at /home/ops/datalens/agents/ on elin server. Coolify server deployment method references Git repository for code or uploads files directly.
Coolify-ready configuration
The Docker deployment configuration is designed to be ready for deployment with Coolify. The Docker deployment includes a Coolify-ready configuration DEPLOYMENT.md documents the Coolify-ready configuration
COOLIFY_DEPLOY.md
Docker Deployment includes the COOLIFY_DEPLOY.md acceptance document with deployment instructions.
Core functionality test suite
CORS
CORS configuration details are not explicitly mentioned in the provided messages.
Cost per inspection analysis
QuestionRouter realizes the capability to answer cost per inspection analysis queries using structured data.
Cost Reduction Achievement Use Case
Business process for analyzing savings and reductions across related tables.
Cost-per-inspection trends
User asked about the trends in cost-per-inspection, which was addressed with a summary indicating an increase from 2,340 DKK (2021) to 2,400 DKK (2022).
CRASH_PATTERN_ANALYSIS.md
Analyzes crash patterns related to backend startup, focusing on Qdrant connection handling, and suggests lazy-loading to avoid timeouts.