Overview

Flogo is a lightweight, event-driven framework for building integration flows and edge functions. DockerCP deploys it as a Docker container with persistent storage, default port mapping, domain routing, and SSL-ready configuration. Once it is running, you can attach domains, issue SSL certificates, inspect logs, and monitor resource usage directly from the panel.

Docker image flogo/flogo-docker:latest
Default port 7777
Deployment type docker image
Recommended resources 1 CPU · 1 GB

How deployment works in DockerCP

This template gives DockerCP the deployment metadata needed to create a service, prepare runtime variables, map persistent storage, expose the internal port, and connect a public domain with SSL when required.

  1. Create or select a project where the service belongs.
  2. Review the Docker image, tag, default port, environment variables, and volume mappings.
  3. Deploy the service and check logs until the application is healthy.
  4. Attach a domain or subdomain when the application must be available publicly.
  5. Enable HTTPS and verify the final browser response.

Configuration

Environment variables

Variable Default / guidance
APP_ENV production
APP_PORT 7777

Persistent volumes

Volume Mount path
flogo_data /data

Commands

DockerCP handles deployment from the panel, but understanding the equivalent Docker commands helps users debug services with more confidence. 

docker pull flogo/flogo-docker:latest
docker ps --filter "name=flogo"

docker logs --tail=100 flogo

DNS and SSL checklist

Step Expected result
Add A or CNAME record The domain points to the DockerCP server or configured target.
Attach domain to service The service is reachable through the selected hostname.
Enable HTTPS The certificate becomes active and redirect to HTTPS can be enabled.

Screenshots

Panel previews for the Flogo template: how deployment, the running service, and its key details look inside DockerCP.

Flogo deployment form inside the DockerCP panel.
Automation workflows running on the deployed service.
Public webhook URL routed through the DockerCP proxy.

Troubleshoot

  • Confirm the Docker image and tag exist.
  • Confirm the selected internal port matches the application port.
  • Confirm required variables such as database URL, app URL, and credentials are set.
  • Check service logs after the first deployment.
  • Verify DNS before requesting or renewing SSL certificates.