target
Add configuration the lorri socket address
Feature description
Lorri has a single hardcoded address it uses for its socket. It's conceivable that there are use cases where this would be insufficient, in which case it would be nice to be able to supply a different address.
Likely, this should be provided as an environment variable, since many lorri commands are likely to want to meet at one socket.
Target users
Lorri developers themselves, as it might be handy to segregate the lorri-in-development from the workaday one. There's a blue-sky potential for non-unix-socket communication between Lorri processes e.g. to share a cache or something in a team. This might also be useful with an eye to changing the Lorri communication protocol.
potential for non-unix-socket communication between Lorri processes e.g. to share a cache or something in a team.
Hm, I haven’t thought about this before. That would require some more work, since the daemon would not just create a symlink, but copy-closure the build results as well. But definitely feasible.
Bigger issue is that this would require some kind of key-value store from nix expression inputs (maybe even normalized?) to drv files. See also https://github.com/target/lorri/issues/38 (though a more primitive “hashing of all inputs” would already be a good first step).
If we want to think about this, the question is whether it should be implemented in lorri, or whether we shouldn’t rather use an existing build system for this. Or provide primitives to implement into existing build systems, like bazel (which have their own daemon).
