Overview
Jekyll Worker Service is the Ruby static site generator that powers many GitHub Pages sites from Markdown and Liquid templates. This profile runs Jekyll as a background worker process rather than a web-facing service, which suits processing queues, scheduled tasks, and other asynchronous jobs. DockerCP deploys it as a Docker container with persistent storage, default port mapping, domain routing, and SSL-ready configuration.
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.
- Create or select a project where the service belongs.
- Review the Docker image, tag, default port, environment variables, and volume mappings.
- Deploy the service and check logs until the application is healthy.
- Attach a domain or subdomain when the application must be available publicly.
- Enable HTTPS and verify the final browser response.
Configuration
Environment variables
| Variable | Default / guidance |
|---|---|
APP_ENV |
production |
APP_PORT |
4000 |
Persistent volumes
| Volume | Mount path |
|---|---|
| jekyll_worker_service_data | /data |
Commands
DockerCP handles deployment from the panel, but understanding the equivalent Docker commands helps users debug services with more confidence.
docker pull jekyll/jekyll:latest
docker ps --filter "name=jekyll-worker-service"
docker logs --tail=100 jekyll-worker-service
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 Jekyll Worker Service template: how deployment, the running service, and its key details look inside DockerCP.
Offload queues and scheduled jobs to a dedicated Jekyll worker, the Ruby static site generator that powers many GitHub Pages sites from Markdown and Liquid templates.
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.