> On Jun 30, 2024, at 5:18 PM, Rob Landers <rob@bottled.codes> wrote: > I think composer and friends are a moot point. If we go a bespoke way for > everything, we end up with a mess. What about creating "hooks" that things > like composer can "register" an installer at? For example, we could define a > "WELL_KNOWN/installers/composer/hooks.json" (I'm gonna steal a bunch of ideas > from kubernetes from here on), where WELL_KNOWN is some engine-specific > directory (like where the php.ini file is). Basically, any installer can > register an installer by creating a directory in WELL_KNOWN/installers of > which an installer might look like the following for composer:
There is such a thing as a /.well-known/ URI thanks to RFC 8615: https://datatracker.ietf.org/doc/html/rfc8615 https://en.wikipedia.org/wiki/Well-known_URI Not sure if you are envisioning a web-accessible `hooks.json` or not. #justfyi -Mike
