Overview

Bolt.Diy is an open-source AI development environment for generating and editing full-stack web applications with your preferred model provider. DockerCP deploys the published production image, exposes the application on its standard port, prepares Docker-aware runtime settings, and adds host access for local model endpoints when needed.

Docker image ghcr.io/stackblitz-labs/bolt.diy:latest
Default port 5173
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
NODE_ENV production
COMPOSE_PROFILES production
PORT 5173
RUNNING_IN_DOCKER true
DEFAULT_NUM_CTX 32768
OLLAMA_API_BASE_URL http://host.docker.internal:11434

Persistent volumes

No persistent volume is required by the default template profile

Commands

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

docker pull ghcr.io/stackblitz-labs/bolt.diy:latest
docker ps --filter "name=bolt-diy"

docker logs --tail=100 bolt-diy

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

Bolt.Diy deployment form inside the DockerCP panel
Public URL served through DockerCP domain routing and SSL
Running service with domain and database state

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