json.bash (textproc/json.bash) Updated: 9 months, 4 weeks ago Add to my watchlist 0

json.bash's one thing is to get shell-native data (environment variables, files, program output) to somewhere else, using JSON encapsulate it robustly. Creating JSON from the command line or a shell script can be useful when: - you need some ad-hoc JSON to interact with a JSON-consuming application, - you need to bundle up some data to share or move elsewhere. JSON can a good alternative to base64-encoding or a file archive. It does no transformation or filtering itself, instead it pulls data from things you already know how to use, like files, command-line arguments, environment variables, shell pipelines and shell scri…

json.bash's one thing is to get shell-native data (environment variables, files, program output) to somewhere else, using JSON encapsulate it robustly. Creating JSON from the command line or a shell script can be useful when: - you need some ad-hoc JSON to interact with a JSON-consuming application, - you need to bundle up some data to share or move elsewhere. JSON can a good alternative to base64-encoding or a file archive. It does no transformation or filtering itself, instead it pulls data from things you already know how to use, like files, command-line arguments, environment variables, shell pipelines and shell scripts. It glues together data from these sources, giving it enough structure to make the data easy to consume reliably in downstream programs. It's something like a reverse tee — it pulls together data sources, using JSON to represent the aggregation. It's not an alternative to to data-processing tools like jq, rather it helps assemble JSON to send into JSON-consuming tools like jq.

+ Show more

GitHub

Trac Tickets

×

Close

• Details
• Builds
• Installation Stats
• Trac Tickets
• Report an Issue with this port
• API
• Stats FAQ

Statistics for selected duration

2025-Jun-28 to 2025-Jul-28