Overview

Botpress v12 is the legacy self-hosted edition of the Botpress conversational automation platform. DockerCP deploys the official v12 container with persistent application data, environment configuration, domain routing, and HTTPS-ready service settings. The upstream self-hosted edition is now sunset, so this template is intended for users who specifically need the maintained v12 container rather than Botpress Cloud.

Docker image botpress/server:v12_31_10
Default port 3000
Deployment type docker image
Recommended resources 2 CPU · 4 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
BP_HOST 0.0.0.0
NODE_ENV production
PORT 3000

Persistent volumes

Volume Mount path
botpress_data /botpress/data

Commands

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

docker pull botpress/server:v12_31_10
docker ps --filter "name=botpress"

docker logs --tail=100 botpress

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 Botpress template: how deployment, the running service, and its key details look inside DockerCP.

Botpress 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