Goaccess with caddy v2

[timelordx]

You definitely can use the regular Caddy image.

@copolycube

not sure what in your configuration required the custom image

As I mentioned in my previous post:

I’m using my own timelordx/caddy-dns-acmedns Docker image just for ACME-DNS support - this is only relevant to how I obtain TLS certificates

I simply copy-pasted my running setup as an example. In that setup, I’m using a wildcard certificate obtained via the ACME-DNS module, which is the only reason for the custom image.

That said, I’ve since simplified the configuration and removed the separate WebSockets site. Everything is now served under a single domain:

GoAccess Log File Analysis for Caddy

This setup lets you analyze Caddy access logs with GoAccess and view real-time web stats via webstats.example.com, served directly by your Caddy server. It also supports WebSockets through the same domain. Components (Docker Images) Used: Caddy web server GoAccess MaxMind GeoIP (optional) Caddy Docker Compose: services: caddy: image: caddy:latest container_name: caddy volumes: - /volume/docker/caddy/etc/caddy:/etc/caddy:ro - /volume/docker/caddy/config:/config …