So, to clarify, roll_local_time is “Whether to use local timestamps in rolled filenames.”
Is that what you’re looking for, or are you looking for the timestamps in the individual logs messages themselves to be localized?
If you want to change the time format, you can use the time_format on the encoder options. But right now there’s no way to set those to local time, they default to UTC. In general UTC is the best default because it’s immune to timezone issues like daylight savings time etc.
Are you sure your user as which you’re running Caddy has permissions to write to that location?
You can use the console encoder which is somewhat nicer. But yeah, Caddy’s logs are structured logs.
You can use the discard writer. Make sure to configure the default logger in global options (see the docs).
FYI this line will only match requests to exactly the path / and nothing else. Remove the / to make it apply to all requests.
You won’t really gain anything by turning off TLS 1.2. I strongly recommend just leaving the defaults here.
For now, you’ll need to use some external tooling to transform the timestamps. There’s currently no way to emit local time in logs.
You can set up more than one logger. Make the default one discard, then configure another to log to file.
But really, you should probably run Caddy in such a way that stdout/stderr are captured and written to file. You can do this by running Caddy as a windows service. See the docs for instructions for that: