Configuration

#Project runtime

The root .env.example provides addresses for running services directly on one host. Compose connects through container service names, and configuration classes may also default to container-network addresses. Set URLs for the actual launch mode; localhost examples are not container-to-container addresses. Browser access, internal services, and model providers use separate configuration.

The Vite development server listens on 21108 and proxies /api to http://127.0.0.1:21109. The Compose frontend uses its own reverse proxy. A VITE_API_BASE containing a container hostname unreachable from the browser causes request failures; keep the default empty value when using a same-origin proxy.

Model services manages provider connections and the model catalog through /api/model-providers, /api/models, and /api/models/custom. URL and API Key fields open empty. Saving blank fields preserves the existing connection; new values replace it when saved, and removing a saved key requires the explicit clear action. Base URL is the provider endpoint, not the iGraph workspace URL. Embedding models still require provider support. Credentials belong in application configuration, never in the documentation site.

#Construction and computation

Graph Engine runs construction with separate model, budget, and experience configuration. Budget values below come from .env.example as deployment starting points; use the construction page and API of the same deployment for request options and limits. Relational construction can explicitly use a rules baseline, while text entity extraction requires a usable LLM service.

A persistent deployment also needs durable PostgreSQL, Graph Engine data, skills, and session workspaces. Large-graph computation, NebulaGraph, upload quotas, and text extraction have their own settings. Check .env.example, graph-computation documentation, and the actual error instead of trying to resolve every capacity issue by increasing construction timeout.

Partitioned large graphs use durable jobs and workers, separately from the ordinary graph-algorithm process pool. LARGE_GRAPH_EMBEDDED_WORKER defaults to true for direct startup; Compose disables the embedded worker and starts a separate graph-engine-worker. Preparation converts supported text edge lists or triples into partitioned snapshots; not every binary graph format supports this preparation path.

The construction panel lets you select a model or enter a custom model ID and save a separate URL and API key for TXT extraction and AI-assisted table construction. GET /api/construction-models returns the list; GET / POST /api/construction-model-settings reads or saves the connection. Blank fields retain saved or server settings; an explicit clear action removes a saved key. In Compose, settings are stored by default in /data/configuration/construction-model.json, not in dataset options or construction reports.

Settings such as PER_USER and USER_UPLOAD_QUOTA still count by storage owner. In single-user mode these limits apply to the default workspace, without creating accounts or assigning login permissions.

#Documentation-site settings

The independent documentation site does not use model API keys, database connections, IGRAPH_CONTROL_SERVICE_KEY, or VITE_API_BASE. docs-site/wrangler.jsonc configures the site name, compatibility date, and dist asset directory. Optional SITE_URL generates absolute canonicals and a sitemap at build time and must be the actual documentation HTTPS origin without a path, query, or fragment. Cloudflare publishing credentials upload static files; they are not iGraph application credentials.