Caddy-L4 support

[vnxme]

Hi,

I like your plugin and always use it when contributing to Caddy and caddy-l4. Thank you for maintaining it!

It would be very nice if you could extend caddyfile support to cover the layer4 app. To navigate through various modules and syntax options, you may refer to the docs PR, integration tests and comments to UnmarshalCaddyfile functions in the code.

[xepozz]

Hi @vnxme
Sorry for the late answer.

For if I support Json Schema for Caddyfile instead?
Basically, I can switch between original / l4 schemas in the plugin itself, or you can change it anytime you want.

Is there json schema for l4?

[vnxme]

No, I don't think there is a JSON schema valid for configuring caddy-l4 via Caddyfile. In general, both Caddy and caddy-l4 can be configured via Caddyfile, a preferred proprietary format, and JSON. But JSON syntax slightly differs from Caddyfile. So even if there is any tool that generates JSON schemas based on Go source files, it won't help with Caddyfile.

What JSON schema did you use to implement generic Caddyfile support?

[xepozz]

I mean, we could imagine Caddyfile syntax as a JSON:

host {
  directive value1 value2
  ...
}

to

{
  "host": {
    "directive": ["value1", "value2"],
    ...
  },
}

Or similar to this.

Caddy / Caddy-L4 maintainers or community may create and support JSON schema for the JSON variant of the config.
But in plugin I can add json-like layer which will use JSON schema for Caddyfile syntax.

So next time you write

host {
  dir<HERE>
  ...
}

you'll get all JSON schema intentions from and around it, like autocompletion, documentation, validation.

I think it's much easier and maintainable to re-use JSON-Like adapters than introduce our own.

[vnxme]

I think I don’t fully get it. Did you use any JSON schema to build the plugin? Is it something publicly available on GitHub or caddyserver.com, or did you compose it yourself?

I haven’t found any JSON schemas in this repo, so I’m a bit confused about how it works and what it’s needed to support Caddy-L4.