-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
In addition, I think bash's `operate-and-get-next` can be very helpful. When you go back through your shell history, you can hit Ctrl+o instead of enter and it will execute the command then put the next one in your history on the command line, and keep track of where you are in your history. This way, you can rerun a bunch of commands by going to the first one and Ctrl+o till you are done. And you can edit those commands and hit Ctrl+o and still go to the next previously run command.
Note: fzf's history search feature breaks this. https://github.com/junegunn/fzf/issues/2399
I started using just [0] on my projects and have been very happy so far. It is very similar to make but focused on commands rather than build outputs.
Define your recipes and then you can compose them as needed.
[0] https://github.com/casey/just
I made something called shell workspaces[0] for this.
I like to tinker with bash and this has helped me keep all of the commands relevant to a particular project discoverable, accessible, and documented.
It uses a function "," for command execution. So, for instance, if the workspace file defines a function "build", when you're in the workspace, the command `$ , build` will run it.
It's not the most comprehensive solution to this, but it's probably the bit of shell programming that I use almost every day and has saved me tons of time.
[0] https://github.com/nepthar/ws.sh
I've heard good things about atuin
https://github.com/atuinsh/atuin
I created a tool I called parseArger to create/maintain bash scripts arguments/options/flags parsing code https://github.com/DimitriGilbert/parseArger
It's heavily inspired by ArgBash (https://argbash.dev/) and uses parts of bashly (https://github.com/DannyBen/bashly/) which are very similar tools :)
Navi[1] is perfect for this! It's both a fuzzy finder of a personal collection of commands, but it's template syntax is flexible enough to be able to have "command builders"
I have a blog on doing exactly this for a subset of strace[2].
1: https://github.com/denisidoro/navi
2: https://kbknapp.dev/strace-navi/
Related posts
-
How do you guys keep a list of the commands you gotta run across different projects?
-
How do i get history suggestion like this in my bash is there any plugin for oh my zsh. Not autocomplete but history suggestion.
-
Explore and install terminal plugins with 1-click using the Fig Plugin Store
-
Z – Jump Around
-
Show HN: Inshellisense – IDE style shell autocomplete