Daemonized Lorri

[grahamc]

Shea Profpatsch and I met a couple weeks ago and came up with some designs on how to setup a daemon.

Essentially what we came up was fairly simple:

• Lorri's daemon will listen at a "well defined location" -- as defined by the XDG rules for XDG_RUNTIME_DIR
• Entering direnv will look at this location for the socket, and if it isn't present or listening, spawn a new socket
• Each time lorri's direnv hook is activated, it will send a ping to the daemon
• The daemon will "time out" after a period and then exit
• A single lorri daemon will cover many projects

We'll want to take care that one evaluation does not block another evaluation.

[infinisil]

What's the advantage of using one daemon for many projects instead of one for each?

[grahamc]

That is certainly a question. That would eliminate the need for a well known socket location, and would simplify blocking evaluations.

Having a single daemon means fewer watches when paths overlap, but not sure that is a significant benefit.

@shlevy, @Profpatsch?

[shlevy]

The main advantage is that many more service mangaement setups will support a single service than those that support multiple parameterized services, and you can start it once at login instead of having to start it once per project.

[colonelpanic8]

This is done now, right?

[Profpatsch]

This is done now, right?

Everything except the timeout part, which is why I haven’t closed this issue yet.

[Profpatsch]

Closing in favor of #163. This is a nicely small-scoped issue, if anyone wants to give it a try.