V2 - Start php-fpm process when caddy starts up

1. My Caddy version (caddy version):

2.0.0 (caddy_2.0.0_linux_amd64)

2. How I run Caddy:

By running /usr/bin/caddy run --config /etc/Caddyfile in a Docker container

a. System environment:

Docker (php:7.4-fpm-alpine)

b. Command:

/usr/bin/caddy run --config /etc/Caddyfile

c. Service/unit/compose file:

d. My complete Caddyfile or JSON config:

# We are behind a reverse proxy so using http here.

# Define our root path
root * /var/www

# Point all PHP requests to an upstream socket, served by php-fpm

# Enable access logging

# Serve static files

# Enable gzip compression (and zstd)
encode zstd gzip

3. The problem I’m having:

In the Caddy v1, I could do this:

# Point all PHP requests to an upstream socket, served by php-fpm
# Start php-fpm before the server starts listening
fastcgi / php
on startup php-fpm

However, I cannot find anything back in the Caddy v2 docs about the “on startup”.
Is there a way to startup the php-fpm process in Caddyv2? Am I overlooking something in the docs? Or should I make a Docker entrypoint script that starts up php-fpm first, and then runs caddy run?

4. Error messages and/or full log output:

5. What I already tried:

6. Links to relevant resources:

running caddy behind reverse_proxy is extremely interesting.

@tweeniev2, Yeah well… I use Dokku (Dokku - The smallest PaaS implementation you've ever seen) to easily deploy some containers of my sideprojects. It’s like Heroku. But it installs an Nginx reverse proxy in front of the Docker containers… Nginx handles the Letsencrypt certificate automatically. But I like Caddy for the simplicity in combination with my php app :slight_smile: Someday I’ll entirely use Caddy probably. The documentation mentions Caddy so I guess it’s possible in the future: Dokku - Docs - Networking - Proxy Management

1 Like

I would just recommend using docker-compose to start up your stack, with the restart: unless-stopped option.

Run two containers, one for caddy and one for php-fpm, and then use php_fastcgi php-fpm:9000. Make sure that Caddy has a volume with the files for your site as well so it can see which files the app has to serve and so it can serve static files.

That could be an option! But I’m used to Dokku which is similar to Heroku deployments (buildpacks).

My question really is: is the on startup php-fpm option removed in V2, which means I have to write a docker-entrypoint.sh script instead? The migration docs did not mention this. It’s this feature: https://caddyserver.com/v1/docs/on

Currently we do not have an equivalent to on in v2.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.