Service tasks

[lucasew]

I'd define services as things that should be running until interrupted

How I am thinking about the UX:

• Tasks by default are transient, nothing happens if they die
• A task becomes a service if it gets a service = true attribute
• If a task depends on a service it starts the service and keeps it running with the lifetime of the task, the task ends? the service stops.
• If the user do mise run task and the task is a service it would work like it is today, run until Ctrl+C
• A task service can depend on other task services and it would follow the same rules
• If a task service fails everything else fails too

Usecases

• Run service containers while doing development, like databases. Docker compose does that but you are limited with containers
• Run service containers so tests can use them in CI

[jdx]

it's nascent but I have a separate project around services: https://pitchfork.jdx.dev/

[ideasasylum]

fwiw, today Claude completely imagined a mise services feature and I was unreasonably excited about it: