caddy-embed

Currently, this approach has some UX problems. It requires cloning this repo and copying the files to embed to inside of the repo. This is awkward for various reasons, such as fighting with with the directory, having to clone at all meaning you have some extra directory sitting around, having to copy your files yourself (i.e. needing to write a script/Makefile to automate it), needing to modify if you want to rename the embed, etc. My suggestion is that we could move this to the https://github.com/caddyserver/xcaddy project, where it would be a build flag, i.e. . Then would create the file itself into a temp dir, optionally change the line to use a different base path (maybe with another flag like ), copy the given path (files to embed) to inside of the temp dir, then invoke the build as normal. I think this would be _significantly_ better UX, because there would be no need for messing around with , no copying files by hand, no need to write your own build script to make it work as a repeated command. It would just become an argument to the command they (probably) already use.

On my machine the build take about 9 hour and still running, so I terminate it. Do you know why this is happen? !image I'm using Ubuntu 22.04.2 LTS, go version 1.20.6, xcaddy v0.3.4 Step to reproduce 1. Install xcaddy: 2. Clone the repo: 3. Build Caddy with plugin: I tried reinstall xcaddy with and the output still the same. Do you think is xcaddy bug?