helm-secrets
transcrypt
helm-secrets | transcrypt | |
---|---|---|
1 | 7 | |
1,142 | 1,409 | |
- | - | |
0.9 | 4.8 | |
over 3 years ago | 5 months ago | |
Shell | Shell | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
helm-secrets
-
HELM SECRETS
helm plugin install https://github.com/futuresimple/helm-secrets
transcrypt
-
Is Mozilla SOPS dead?
I was looking into secret storage in git recently and rather liked Transcrypt: https://github.com/elasticdog/transcrypt
- GitHub can now auto-block commits containing API keys, auth tokens
-
git-crypt VS transcrypt - a user suggested alternative
2 projects | 5 Jan 2022
-
Do you alternate with Emacs?
On the actual system itself (you likely know this as you'd mentioned reading other posts, but) I have Neovim compiled on my phone (directly through Termux), notes pushed up to Github using transcrypt for backups and live-synced between several devices using syncthing (which is how I get notifications on my phone, using a Raspberry Pi and systemd services to implement against orgmode.nvim's notification API).
-
Note taking
I use nvim-orgmode on my computer through Neovim, and keep that pushed up to Github (encrypted using transcrypt) but also have a Syncthing server setup on a Raspberry Pi.
-
Encryption for VimWiki
Also if you want the notes to be encrypted and you push them to Github, try transcrypt. They won't be encrypted on disk, but will be when you push them.
-
How do I become "smarter"
Start writing all of your work down. I personally put almost every line of code I ever write into github. I have a "misc" project for random one-off things, but I always commit it to a repo. I started doing this in 2013/2014 and its been incredibly valuable to go back and refer to old work (its also fun to see how far you've come). This gets interesting when you start needing to write down information that shouldn't be public (e.g. api keys). You're into crypto, so you can probably see the fun in this. I've use a program called transcrypt to store encrypted files in my git repos. Be careful with transcrypt though, if you make a mistake you can accidentally publish secrets in plain text, and it does open you up to brute force attacks.
What are some alternatives?
k8s-wait-for - A simple script that allows to wait for a k8s service, job or pods to enter a desired state
git-crypt - Transparent file encryption in git
data-center-helm-charts - Helm charts for Atlassian's Data Center products
vim-gnupg - This script implements transparent editing of gpg encrypted files.
helm-teller - Allows you to manage configuration and secrets from multiple provider while masking the secrets at the deployment
helm-secrets - DEPRECATED A helm plugin that help manage secrets with Git workflow and store them anywhere
helm-git - Helm Plugin - Install Helm Charts strait from Git repositories
encpass.sh - Lightweight solution for using encrypted passwords in shell scripts
sops - Simple and flexible tool for managing secrets
neorg-haskell-parser
kubernetes-lts - Kubernetes LTS(long term support)
obsidian-vimrc-support - A plugin for the Obsidian.md note-taking software