morphy VS dupver

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.

I work with a lot of uncompressed structured binary files so I finally broke down and wrote my own system based on the Restic chunker: https://github.com/akbarnes/dupver

I wound up writing dupver https://github.com/akbarnes/dupver after getting frustrated with the lack of versioning tools for binary files. One neat thing about .docx files and their ilk is that they are "just" zip files so it isn't hard to add special handling to pull out their contents and run deduplication over that.

DupVer https://github.com/akbarnes/dupver is a deduplicating version control system for large binary files. It's designed to keep state in a repository on the local machine separate from the working directory so it plays nice with cloud synchronization software.

I started it after constant headaches involving Git LFS and the corporate proxy. It's based around the Restic chunker library, with inspiration from both the Duplicacy backup software and Boar, another binary version control system for large binary files.

https://github.com/akbarnes/dupver