procmux VS scripts

projects, especially monorepos (like the one we work with at our company), often have a large list of undocumented scripts that can be executed with/against the codebase. Some scripts are long running daemon-like processes that stay running during the entire development process. Some script are executed adhoc but a relatively quick running, then they exit.

So, there are two problems:

- scripts get added silently and generally documentation about what they do or how/when they should be used is missing

- invocation of each script is messy, it often requires multiple terminals and switching between them is cumbersome

Procmux is a yaml config-driven TUI (terminal user interface) for managing project-level and system-level scripts/terminal sessions

https://github.com/napisani/procmux

Procmux is written in python, using prompt_toolkit + ptterm for the TUI functionality

this app was heavily influenced by the the mproc TUI

at a high-level, this is the current feature set:

- use keyboard bindings / mouse clicks to select scripts from the project

- view help / documentation for each script

- filter available scripts by name, category or meta tags

- zoom into open terminal sessions

- full screen doc/man page mode

- enter scroll mode - to see previous command output

- start / stop any script selected within the process list using the defined keybindings

- start scripts that require templated/interpolated input

- quit all running scripts all at once

Feel free to check it out, make suggestions, contribute or all of the above!

I made this at one point to counter that anti-Linux FUD; I still maintain it but not as religiously -- it's become too polarised and no one on that sub is logical once they've made up their minds (which perhaps applies to me also, but shrug !)

try https://github.com/xkcd386at/scripts/blob/master/restic-find-fzf if this interests you. Like a lot of my tools, this one also uses the amazing fzf program to help you select files or directories to extract

for people who want this kind of combination but still have muscle memory for head and tail arguments, try this: https://github.com/xkcd386at/scripts/blob/master/ht

if someone wants a pure bash+fzf+ripgrep solution with slightly different behaviour, take a look at https://github.com/xkcd386at/scripts/blob/master/vgc

So... https://github.com/xkcd386at/scripts/blob/master/fclone (and yes the program name is probably even less imaginative than rfync -- suggestions welcome)

I have a script that identifies exact duplicate directories; see https://github.com/xkcd386at/scripts/blob/master/dirdups

https://github.com/xkcd386at/scripts/blob/master/usff for the win

as for session token stealing, on Linux at least I have long advocated using multiple userids to run browsers -- I log on to gmail in a user called x3-gm, to amazon in a user called x3-amz, and so on. All simultaneously and without having to logoff/logon. https://github.com/xkcd386at/scripts/blob/master/usff has the details, but that's not important; the main idea is to not use the default locations for any important logged in site. Sure there is some pain in manually moving files between userids (e.g., move statement from bank userid to gmail userid to send to my accountant), but it's not hard and some judicious use of /tmp or similar can help a lot