This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-12-23
Channels
- # adventofcode (4)
- # beginners (25)
- # biff (11)
- # clojure (2)
- # clojure-bay-area (1)
- # clojure-europe (5)
- # clojure-norway (2)
- # clojuredesign-podcast (4)
- # datalevin (2)
- # dev-tooling (34)
- # hyperfiddle (2)
- # missionary (5)
- # off-topic (3)
- # polylith (4)
- # rewrite-clj (13)
- # shadow-cljs (11)
- # tools-deps (1)
- # vim (1)
- # xtdb (5)
Hi, guys! I've heard you mention keeping dev secrets in a dev.edn
file a few times. That works well, and I still do that sometimes. But are you aware of https://github.com/magnars/confair by @magnars? It lets you check in encrypted secrets and configs into your Git repo. Very useful and “standard” in the (small) Norwegian subcommunity! I thought you might like it. Cheers and Merry Christmas!
@U01PE7630AC @U0JEFEZH6 Thanks for the suggestions! I’ll have to check those out. As for crypting within a got repo, I’ve used a separate repo for that. Something totally separate than my source repo. I also like the idea of having a command line interface to a secrets manager. Thanks again!
committing secrets always felt risky. if you get the crypto wrong or someone finds a flaw in the crypto you're using then all your secrets are forever available in the git history, forcing a rotation. storing the secrets in a separate service that maintains proper encryption and security for you always felt safer