From what I gather, the main difference would be tweaking WebCoRE piston side of things where it stores the JSON value and updating the image URL to point to the ‘latest’ version of the jsonbin that you create. I poked around with jsonbin.io and it looks like you’ll need to create an account, create a bin, and then use that in your pistons…
Out of curiosity, what kind of things are you using WebCoRE variables for? I’m curious if there’s some way to accomplish something similar with the native SharpTools.io variables that have been introduced since this post was originally created.
Here’s some high level steps:
- Create an account on jsonbin.io
- Create a new public ‘bin’ in jsonbin
- I just stubbed in some dummy data, tapped the ‘Private Bin’ button to toggle it to Public, and clicked Create
- From a search of the WebCoRE forums, there’s allegedly a way to pass in authorization headers to use with a private bin, but I didn’t see that in my version of WebCoRE (maybe it just needs an update though?
)
- Grab the URL from the bottom of your newly created bin:
- Go back to WebCoRE and update the Piston like the following:
- When you create the Media Tile, you can use the URL from jsonbin to read the value, but make sure to use tack on
/latestso it grabs the latest version of the bin. In my example, it’s something like:https://img.shields.io/badge/dynamic/json.svg?label=%20&colorA=333&colorB=666&query=$.myValue&style=flat-square&uri=https://api.jsonbin.io/b/5f6dff5f7243cd7e824372b2/latest
