Skip to content
Distr
Book Demo Start free trial Login

Customer Portal Deployments

As an end customer, you can deploy and manage applications with Distr agents directly from the Customer Portal.

This guide walks you through the deployment agent quickstart from the customer portal.

Deployment Agent quickstart from the customer portal

Section titled “Deployment Agent quickstart from the customer portal”

Navigate to Deployments in the sidebar and click on the + New Deployment button.

Choose the application you want to deploy.

Select Application step

Give your deployment a descriptive name. This name will help you identify and manage the deployment later.

For Helm applications, you’ll also need to specify the Kubernetes namespace where it should be deployed. Make sure the namespace exists in your cluster before proceeding.

Deployment Configuration step

Configure the environment variables for your Docker Compose application. These variables will be passed to the docker compose process via the --env-file argument.

The entered environment variables will be passed unmodified to the docker compose process via the --env-file argument. For more information on how to use them, please refer to our guide on working with environment variables.

You can also enable Docker Swarm mode for deployments that should run in swarm mode. See Docker Swarm for more details. Additionally, you can enable container log collection to view application logs directly in the portal. Learn more about Container Logs.

Application Configuration step

Review your configuration and click Create Deployment to proceed to the deployment page.

Deployment success page

View real-time updates as your deployment initializes.

Deployment status view

Click on the status button to view application logs directly from the portal.

Environment logs view

Modify configuration values and update running deployments as needed.

Update deployment view
  • A single agent can manage multiple deployments in the same target environment
  • To remove a deployment, first undeploy it before deletion