- docker/server/traefik-passthrough: for a Traefik already on the server without a working certificate resolver; TLS passes through (TCP router), FrankenPHP gets its own certificate (HTTP challenge on the :80 entry point, JUMPHP_TRAEFIK_HTTP_ENTRYPOINT) - the generated Caddyfile drops "email" when JUMPHP_ACME_EMAIL is empty (Caddy refused the config and the container restarted in a loop) Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_018nX3d49j1YFpo3vu8qZuQd
975 B
975 B
Server deployment templates (bin/jumphp deploy)
bin/jumphp deploy copies one of these folders to the server with the browser builds in site/ and a .env
made from the project's .env (JUMPHP_SERVER_MODE, JUMPHP_DOMAIN, JUMPHP_ACME_EMAIL, JUMPHP_TRAEFIK_*),
then runs docker compose up -d there. bin/jumphp deploy:setup asks for the values.
frankenphp/: FrankenPHP alone, ports 80 / 443, HTTPS certificates from Let's Encrypt by Caddy itself.traefik/: Traefik (ports 80 / 443, Let's Encrypt, HTTP -> HTTPS) in front of FrankenPHP (plain HTTP inside).traefik-external/: FrankenPHP only, joined to the network of a Traefik already running on the server.traefik-passthrough/: the same, for a Traefik without a working certificate resolver: Traefik passes TLS through (TCP router onJUMPHP_TRAEFIK_ENTRYPOINT) and FrankenPHP gets its own certificate (HTTP challenge through the port 80 entry pointJUMPHP_TRAEFIK_HTTP_ENTRYPOINT).