Overview

Beanstalkd is a simple, fast work queue for distributing background jobs to workers. It is packaged here as a ready-to-deploy DockerCP template. On DockerCP it runs as a managed Docker container with persistent volumes, environment variables, domain routing, and one-click SSL. Sensible defaults for ports, volumes, and environment variables take you from template to running service in a few clicks.

Docker image schickling/beanstalkd:latest
Default port 11300
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 11300

Persistent volumes

Volume Mount path
beanstalkd_data /data

Commands

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

docker pull schickling/beanstalkd:latest
docker ps --filter "name=beanstalkd"

docker logs --tail=100 beanstalkd

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

Beanstalkd deployment form inside the DockerCP panel.
In-memory service with internal endpoint and protected access.
Runtime metrics reported by the service.

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.