simplecd VS null

I'm pretty sure that to this day, I am its only user, but it's fascinating how a relatively simple bash-based continuous delivery script can power the build & deploy pipelines of some quite complex and large-ish projects of mine: https://github.com/manuelkiessling/simplecd/

I needed a no-fuzz, lightweight Continuous Delivery setup, and wrote https://github.com/manuelkiessling/simplecd.

It’s a single bash script.

To this day, I use to deploy all my projects, including my work projects, no matter what tech stack I use, with great success.

I find most Continuous Delivery tools/services overkill most of the time, so I wrote (and heavily use, even in enterprise setups) my own tool „SimpleCD“, which is just a single Bash script, but is extremely powerful and flexible: https://github.com/manuelkiessling/simplecd

I build a logging library for Go, because I couldn't find one that logs to stdout AND stderr. If you used a logging lib on GCP for example, all log output went into the same pile of junk and it was hard to find "real" errors: https://github.com/emvi/logbuch

Then there is "null", also because I couldn't find one that got both, marshalling to JSON and be able to store null values in db: https://github.com/emvi/null

And finally, our "flagship" open-source project Pirsch, an embedded library for web analytics: https://github.com/pirsch-analytics/pirsch