Hi Dave,
"Thompson, David" <[email protected]> writes: > > Services. Imagine you are developing a web application. You'd probably want > 'guix session' to at least launch a database server. This would be > accomplished by starting a Shepherd daemon with a (perhaps containerized) > database service that keeps all of its state local to the project root > directory. The unfortunate thing here is that neither system nor home > services are the right fit. There would need to be a new service layer for > this tool. This is something I could rant about, but I will refrain. :) > I don't think this is necessary for the first version. I think the first version could use operating-system along with the system container. That way system services can be reused. I agree it's not 100%, but it's something. I already heard of people starting databases etc. like this in their workflow. Rutherther
