trust

I was working on updating my personal dev blog which used to be on Jekyll and wanted to try out Gatsby for increased flexibility in making my own things. Along the way I realised that the format for Markdown posts in Jekyll blogs is slightly different from the one used in Gatsby (Jekyll relies on a specific filename format for slugs and dates, whereas Gatbsy reads this data from frontmatter blocks in the markdown header). I figured it would be a good occasion to write a small Rust project (I'm very new to Rust) so I made a tool to batch update my posts, with loads of options to choose exactly how to migrate the files. Pretty impressed with the speed of Rust as it processes about 30 blog posts instantly (despite having a regex that scans the entire file), I'm almost sure if I made a node.js tools it would have been slower. It's published o

Never thought I'd see someone link to one of my projects! As others have pointed out, it's not a perfect solution and has a limited scope of use. I originally made this as an experiment to make it easy to distribute updates for cli apps that I was working on. Yes, a package manager is the "right" way to do this, but since I was testing and building images in my CI flow (using https://github.com/japaric/trust) I wanted a way to take advantage of that pipeline in a seamless way. The library exposes a couple predefined "backends" that handle common patterns like GitHub releases and s3, but the underlying steps (downloading, extracting, replacing) are also made available so you can build your own update pattern and add things like verification.

FWIW, 'cargo install' is designed to be for distributing dev-tools, rather than for end-user tools. I believe https://github.com/japaric/trust is designed to make it very easy to publish Github Releases from CI systems.

Incidentally, this is _very easy_ to do with Rust: https://github.com/japaric/trust