Yes, I understanding working with JSON. I do it nearly daily (read, modify, update, write, between client and server)
FWIW,
If I was going to use the same API to modify and update JSON as you are doing, I would write a quick app with either PHP (if I did not need any UI), or I would develop with with Vue.js if I needed a web UI.
PHP processes JSON much better than bash and can easily update as well with very simple tools to pull and push files from the net built in, obviously.
Vue.js with extensions like Axios and Vuex is so rich in features for processing JSON across the net that comparing it to bash would be like comparing the Starship Enterprise to a flat bottom wooden boat (at worse) or at best (and being generous) an antique car.
Anyway, I realize a lot of people like to use these old tech tools from decades past and build an infrastructure around it to make it work; but honestly when working with JSON across the net as you are doing, there are much better tools than command line
jq, curl, wget and bash, I promise
Anyway, I think I understand the reason you are using
bash, curl and jq.... you are comfortable with those tools and that's cool too
. I used to use those tools (excessively) between 15 and 5 years ago, so I understand and might use them again if I was forced to. However, I have noticed a
seismic shift in JSON processing, including the use of
Firebase and JSON-based NOSQL repos.
PS:
At least use Postman to analyze your API calls. Postman is one of the single most productivity enhancing tools out where when working with JSON APIs.
03-11-2019
