Services overview

Service types in the dashboard, where they live under Applications and Environments, and links to create, configure, and operate them.

Written By Zoro

Last updated 3 days ago

Service

A Service is a runnable workload inside an Environment. Every Service belongs to exactly one Environment; that Environment’s compute (Worker Node or managed capacity) is where builds and containers actually run.

Read Services and How dFlow is structured under Core Concepts in the sidebar.

Service types

dFlow groups workloads into three types you choose when you create a Service:

TypeUse it for
AppHTTP applications built from Git (or similar sources).
DatabaseManaged database engines (Postgres, MySQL, MongoDB, and others).
DockerA container image you specify (public or private registry).
  • App services: sources, builds, domains, scaling patterns (page in this section).
  • Database services: how databases fit the same model; engine guides sit under Databases in the sidebar.
  • Docker services: images, ports, and when Docker fits better than App.

Where Services appear in the dashboard

Work from Applications: open an Application, then open an Environment (from the Environments tab or your default Environment). Services are listed and managed in that Environment’s context, typically the Services tab or canvas, depending on your flow.

Create paths are covered in Create a service (this section). How services relate to environments explains scope, compute, and isolation.

Configure and deploy

  • Settings and variables (App and Docker): Service settings for static values, references to other Services, secret(), and database reference variables.
  • Deployments: each Service has a Deployments history; see Deployments overview under Deployments and Operations and Deployments under Core Concepts.
  • Logs: Logs under Deployments and Operations for build and runtime output.

Configuration changes are staged in the UI until you Deploy or Redeploy (wording varies by Service type). If a rollout fails, use Troubleshooting in the sidebar (Deployment issues, Logs and debugging).

For maintainers mapping UI behaviour to code, see Service actions under API, CLI, and Admin Reference (advanced).

If something fails

Use Troubleshooting in the sidebar. Typical starting points: Deployment issues, Logs and debugging, Compute and worker node issues, Integration issues, and Database troubleshooting (under Databases).

Related