Service

A Service is what actually runs your workload. Changes are staged until you Deploy or Redeploy. You need an Application first; follow Create an application under Applications in the sidebar.

For how Services sit inside Environments, read Services concept under Core Concepts in the sidebar and How services relate to environments under Services in the sidebar.

Prerequisites

• An Application with a Worker Node (or compute) available for its Environment.
• For Git deploys: a repository and (if private) access configured. See Integrations overview under Integrations in the sidebar.
• For private images: a registry integration when the UI requires it. See Docker registry integration under Integrations in the sidebar.

1. Create a Service

New Application canvas: if there are no Services yet, use Add new (or equivalent), pick types, configure sources and Volumes, then deploy. Services often deploy in sequence in canvas order.

Existing Application: use Create Service, pick the type, open the Service detail page, configure, save, then Deploy.

More detail: Create a service under Services in the sidebar, Services overview under Services in the sidebar.

2. Deploy from Git

Supported providers include GitHub, Azure DevOps, GitLab, Bitbucket, and Gitea. See Integrations overview under Integrations in the sidebar.

GitHub

• Manual setup: choose GitHub, Manual, add token for private repos, set repository URL and branch, save. Deploy when you trigger Redeploy (no automatic deploy on push unless the product shows otherwise).
• GitHub App: choose GitHub App, pick the installation, repo, and branch. Pushes to the configured branch can automatically trigger deploys when enabled.

Azure DevOps, GitLab, Bitbucket, Gitea

1. Select the provider.
2. Add a Git token when the repository is private.
3. Set URL and branch, save.
4. Deploy manually unless the UI shows automatic deploys for that provider.

Provider specifics change over time, so trust in-product labels over this summary.

3. Deploy a Docker image

1. Create a Docker-type Service.
2. Public image: image reference and ports, save, deploy.
3. Private image: image reference, ports, pick a configured registry account, save, deploy.

4. Deploy a database Service

Supported types commonly include MongoDB, MySQL, MariaDB, PostgreSQL, Redis, and others. See Databases overview under Databases in the sidebar.

1. Choose the database Service type.
2. Configure storage and credentials as prompted.
3. Deploy.

Shorter first-time guide: Create your first database. Reference other Services with dynamic env vars in Service settings under Services in the sidebar.

Expected outcome

A Deployment completes successfully, the Service shows the expected state in the UI, and you can open logs for the Deployment and runtime.

After deploy

• Build / deploy logs: Logs under Deployments and Operations in the sidebar.
• Runtime logs: Logs tab on the Service.
• Restart / redeploy: from the Service or Deployment UI.

If something fails

• Deployment issues under Troubleshooting in the sidebar
• Getting started issues under Troubleshooting in the sidebar
• Integration issues under Troubleshooting in the sidebar
• Environment variable issues under Troubleshooting in the sidebar

Related

• Deployments concept

• GitHub integration