better story for prod use

[amonks]

Keeping all the logs in memory is great for interactive use, but it's also inherently a memory leak, which could be uncomfortable for non-interactive use cases.

I use run "in prod" to orchestrate processes, and in that context, writing to a bunch of files (or even shipping the logs?) would be preferable.

Thinking about it, log files on disk might even be a good alternate way to implement the interactive viewer?

I wonder whether you'd want a single file or you'd want each stream to get its own file 🤔

One API for this might be a new value for the -ui flag.

[jellevandenhooff]

some other fuel to add to the thinking fire: I think I'd like the ability to throw away all logs upon task restart for eg. running tests where I don't care about the last iteration. or at least I think I don't; maybe it'd be extra nice to have the ability to hide the previous logs most of the time but then show them in case I want to debug something.

[amonks]

ooooh that's a nice idea.

I suppose a UI could parse logs to find restarts, but that seems kind of brittle. Maybe a more-explicit api for tailing runner events would be nice.