easydigital/frankenphp repository overview

⁠FrankenPHP — Enterprise PHP App Server

Published by easydigital⁠ · GitHub⁠

Enterprise-ready FrankenPHP images with a custom Caddy build, 51 PHP extensions, and production tooling. Same image as morsalin1342/frankenphp — published here for organizational use.

⁠✨ Why This Image?

The full list of extensions, Caddy modules and tools, with versions and known issues, is in EXTENSIONS.md⁠.

⁠Why Use the easydigital Registry?

• Namespace isolation — keep team pulls under the organization account
• Same image digest — bit-for-bit identical to morsalin1342/frankenphp
• CI/CD friendly — predictable tags for automated pipelines

⁠Deployment Example

# production.yml
services:
  app:
    image: easydigital/frankenphp:8.4-trixie
    restart: always
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - ./public:/app
      - ./Caddyfile:/etc/caddy/Caddyfile
      - app_data:/data
    environment:
      SERVER_NAME: example.com

volumes:
  app_data:

⁠Caddyfile with HTTPS

example.com {
    root * /app/public
    encode zstd gzip
    php_server
    file_server
    header Strict-Transport-Security "max-age=63072000"
}

⁠Available Tags

8.5, 8.5-trixie, 8.4, 8.4-trixie, 8.3, 8.3-trixie, 8.2, 8.2-trixie, latest → 8.5

Only trixie is built; -trixie tags are aliases of the unsuffixed ones. Old -bookworm tags are no longer updated.

⁠❓ FAQ

Q: Can I add extensions? A: Yes — RUN install-php-extensions <name> in a layer on top; the installer is already in the image.

Q: How do I run queue workers? A: Run them as separate containers from the same image with their own command; supervisor and cron are not included.

Q: Is there a bookworm image? A: No. Only trixie is built now. Older -bookworm tags stay on Docker Hub but are no longer updated.

⁠🔗 Related Images & Tools

⭐ If this image helps you, consider giving it a star on GitHub⁠!