| > I see this as capture of processes -- their invocation, context, and results -- in a relatively normalized form for analysis and re-use. That's a nice, neat, concise way of putting it. Thanks. > There are many possible applications based on analyzing these ... Those are some neat ideas. I'd certainly have to talk about them with some real users to understand the demand and use-case. I think the easy sharing I mentioned could go a long way to achieving that goal. You can also already pretty easily extract just the commands run, to (as you put it) hoist it into a larger script or workflow. E.g. in my current instance, `hucksh sql "select command from command_history where id > 2863 order by id"` dumps out the most recent 10 commands you ran. > No one likes to have this level of intrusion or monitoring, but everyone seems to accept running code in containers, so if this were built in to the container, it might be easily deployed and widely accepted. Hmm, perhaps. That does give me an idea for another use-case for hucksh in containers: mount the hucksh database file into a container, across invocations, to have a more seamless history of working in the container. > A more narrow goal based on the current implementation could be to build and maintain a library of bash functions or scripts, possibly shared by a team. Indeed. That's where I was going when I said "I hope in the future to make it easy to share history, which could help with new employee onboarding, [etc]." > My goal is always to migrate any bash that gets big [...] Yes, I agree. Thanks again for your comment. Some neat stuff here. |