Skip to main content

Environments

App page

Environments are named deployment contexts (DEV, QA, Prod, Docker). Each environment is paired with a runtime (shared free-plan, or dedicated hosted runtime for paid plans). Use the Environments page to create environments, request hosted runtimes, and open per-environment detail pages.

Workspace activation

  • ?intent=create opens Add Environment automatically.
  • ?projectId=... opens the page in project-runtime-setup context with a return-to-project action.
  • ?focusEnvId=... highlights the requested environment row.
  • In project context, Set as Project Environment updates the project's default runtime environment.

Overview table

  • Environment name is a hyperlink to the Environment Detail page.
  • The runtime column is summary-only here; runtime assignment lives on the detail page.
  • Hosted-runtime request panels show current account-scoped provisioning state.

Environment Detail page

Open an environment name from the overview to access the detail page. Tabs:

  • Overview -- environment metadata, current runtime summary, counts for linked projects / variables / caches / related agents.
  • Projects -- only projects linked to the selected environment.
  • Variables -- only variables linked to the selected environment.
  • Caches -- only caches linked to the selected environment.
  • Runtime Agents -- current runtime assignment, related runtime agents, and host/status details for the selected agent.

Hosted runtime requests

  • Cloud Runtime Agents surfaces DataLug-managed hosted runtime requests for the signed-in account.
  • Creating a hosted runtime request can optionally target a specific environment. The backend uses that environment as the target for runtime mapping after successful provisioning.
  • Request status, failure reasons, and retry/approval actions appear here based on your role.
  • Free plan shared-runtime backing is NOT presented as a paid dedicated runtime request -- free accounts always share the platform runtime.

Agents (runtime details)

In the Agents section, the table lists running agents and runtimes. Click an agent to open a right-hand detail pane showing:

  • Host name and internal host id.
  • Host IP address.
  • Operating system.
  • Maximum memory and available memory.
  • Storage capacity and available storage.
  • Last updated timestamp.

Paid hosted-runtime containers register back as account-scoped runtime agents. One paid account can have multiple runtime agents linked to different environments even when those agents share one hosted tenant VM.

Plan and environment expectations

  • Free (30-day trial) uses the shared DataLug runtime path; one default environment.
  • Professional ships 2 initial environments (Runtime 01 and Runtime 02).
  • Teams / Business ship 3+ environments with paid dedicated runtimes.