Actually I've been playing with this last week.

1. There is a way to specify a custom luvi, but for some reason it was never documented.
2. You don't even need to embed luvi, a single with #!/path/to/luvi --\n will work just fine in place of the luvi binary.

Using both these my solution is to compile custom luvi for alpine (just clone luvi source and build normally inside alpine). I put it at /usr/local/bin/luvi. Then create a file, I call it prefix that contains #!/usr/local/bin/luvi --\n. Then I build my luvi based app, but using /path/to/prefix in place of the custom luvi.

> lit make lit://luvit/luvit /usr/local/bin/luvit /path/to/prefix

And it will build the zip for luvit/luvit, and append it to the file at /path/to/prefix and store it in /usr/local/bin/luvit

The undocumented feature is the 3rd argument to lit make is the custom luvi path.

I would like to think of some tweaks to luvi that makes this custom luvi easier, maybe a config option?

Thanks for the prompt response!

A config option would be helpful to force a custom version of luvi instead of grabbing a prebuild binary

Agreed, I'll leave this issue open as a reminder to add such an option when I'm back at my desk next week.