1. My Caddy version (caddy version
):
C2RC1
2. How I run Caddy:
Not sure, but it works.
a. System environment:
Ubuntu 18.04. Caddy2 installed as a service. Docker pulls mysql + directus with docker-compose.
b. Command:
thou shalt confuse easily
c. Service/unit/compose file:
docker-compose.yml
(sourced here)
d. My complete Caddyfile or JSON config:
example.com {
reverse_proxy to localhost:8080
}
3. The problem I’m having:
I don’t know if I should be asking here or with Directus folks, but here goes…
The reverse_proxy seems to work alright, it takes a few refreshes sometimes which I don’t understand but lets me look at my broken Directus. One time it even let me login only to see the graphic below.
I can also go to the server-ip:8080 and get a fully functional Directus, but is Caddy involved in that?
There will be follow-up questions:
I’d love to get this on a subdomain, but first attempts at using directus.example.com in the Caddyfile ( + caddy reload
) returned nothing.
And if Directus requires PHP and I haven’t touched PHP, how is Directus working?
How does php_fastcgi work here?
4. Error messages and/or full log output:
5. What I already tried:
Dousing
6. Links to relevant resources:
- Caddy is working
- Directus on Docker
- Caddy on Directus (I’d love to help update this)
- docker-compose.yml
Thank you very much!