First off, thanks for the awesome tool!
Would it be possible to provide a statically-linked git-crypt release, maybe in addition to existing releases?
We're using git-crypt in our containerized CI/CD pipelines, and we prefer to use slimmer images (alpine, busybox or *-slim variants). They usually require some extra packages in order to make git-crypt work, and some of those packages aren't even available in the official repos - e.g. latest Ubuntu doesn't have libssl1.1 that provides libcrypto.so.1.1, so I had to get that package from Debian security update repos.
Another situation where the statically-linked version is very useful: our hosting provider doesn't let us install any packages, but we would like to use git-crypt to manage local deployment configuration synced to master repo on our VCS. Without git-crypt we either have to keep secrets in plaintext and manage them using file permissions (our current setup), or ask the hosting provider to redesign their deployment process (with very slim changes of that happening). I realize that our current situation is suboptimal, but having git-crypt that can simply be dropped on a box and executed without and extra fiddling would be perfect.
First off, thanks for the awesome tool!
Would it be possible to provide a statically-linked
git-cryptrelease, maybe in addition to existing releases?We're using
git-cryptin our containerized CI/CD pipelines, and we prefer to use slimmer images (alpine,busyboxor*-slimvariants). They usually require some extra packages in order to makegit-cryptwork, and some of those packages aren't even available in the official repos - e.g. latest Ubuntu doesn't have libssl1.1 that provideslibcrypto.so.1.1, so I had to get that package from Debian security update repos.Another situation where the statically-linked version is very useful: our hosting provider doesn't let us install any packages, but we would like to use
git-cryptto manage local deployment configuration synced to master repo on our VCS. Withoutgit-cryptwe either have to keep secrets in plaintext and manage them using file permissions (our current setup), or ask the hosting provider to redesign their deployment process (with very slim changes of that happening). I realize that our current situation is suboptimal, but havinggit-cryptthat can simply be dropped on a box and executed without and extra fiddling would be perfect.