I proposed the Vinli Cli as a way to make it easier to play around with our APIs. We had just developed this really cool Virtual Vinli service to allow developers to get test data into their Vinli apps without having to plug in a device and drive around the block with every build. We had the API ready and the idea of building another web portal didn’t bring me joy.
I wanted to steal the best parts of every command line tool I’ve ever used and make one cool tool for developers and internal testers. I remember fondly using the Nodejitsu CLI and being impressed with the ability to sign up for Nodejitsu right in the command line. Also nowadays every tool has a .rc
or .yml
or some sort of config file in the project. A typical project I work on has .eslintrc
, .npmrc
, circle.yml
, docker-compose.yml
, .editorconfig
and perhaps even a .bowerrc
for good measure. I had to get in on that action with .vinlirc
Anyways I wrote a blog post about it over at the Vinli dev blog.