morphy VS json-tail

This is so true but my biggest struggle. Everything I have just shipped before I thought it was ready did really well, yet I still struggle to do it. I built my own static site generator, which I use for my own blog: https://github.com/kiramclean/morphy

I need to at least add documentation, and obviously there's a million other things I think I need before I tell anyone else about it.

I recently set up code coverage reporting with Codecov for a Clojure project of mine that uses tools.deps and builds on CircleCI. It turned out to be pretty easy but the documentation for the various parts was a bit ambiguous, so I wrote down the steps here in case you're looking to do the same. You can see all the changes it took together in context in this commit where I set it up for my project.

For one, you have a better control on the GUI. Don't get me wrong, I actually ship the tools I build also as little servers (example: https://github.com/egeozcan/json-tail) but there are also disadvantages to this.

I've made a half-baked newline separated JSON tailer for my small use case: https://github.com/egeozcan/json-tail

it's super bare-bones, and the golang side of things could have been much better, but it kind of works.