example:
https://github.com/woodpecker-ci/woodpecker/blob/ed6d3f3cea2c9ceab5dbcd22bcc25b48e7523ab2/web/web.go#L10-L11

only we will have to do some restucture of code as you can not embed files that are not in the same directory or in child directory where golang code is where you are embedding it.

go:embed don't support ../ on path, the directory structure have to be changed.

Maybe symlink before build?

We can add a small go file in those locations to grab the assets.

Another thing to consider is that vfsgen provides the gzip versions of assets which we directly serve from the http server if the client indicates gzip support. I think it's crucial for performance to retain the option to serve pre-compiled gzip assets.

Edit:

See https://github.com/vearutop/statigz for one approach to solve it. I also maintain a JS module to generate .gz and .br files at https://github.com/silverwind/precompress.