Overview

Slim PHP Production Profile is a micro PHP framework for building small APIs and lightweight web services. This is a production-oriented profile of Slim PHP, with defaults geared toward stable, always-on operation rather than experimentation. Through DockerCP you can launch it on your own server with persistent volumes, a mapped domain, and automatic SSL.

Docker image php:8.2-apache
Default port 80
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 80

Persistent volumes

Volume Mount path
slim_php_production_profile_data /data

Commands

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

docker pull php:8.2-apache
docker ps --filter "name=slim-php-production-profile"

docker logs --tail=100 slim-php-production-profile

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

Slim PHP Production Profile deployment form inside the DockerCP panel.
Application runtime booting inside the container.
Runtime configuration injected by DockerCP.

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.