This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-26
Channels
- # announcements (2)
- # asami (2)
- # aws (34)
- # babashka (6)
- # beginners (9)
- # calva (76)
- # chlorine-clover (10)
- # circleci (5)
- # clj-kondo (2)
- # clojure (40)
- # clojure-australia (3)
- # clojure-europe (15)
- # clojurescript (39)
- # conjure (1)
- # core-async (4)
- # cursive (4)
- # datahike (1)
- # datomic (69)
- # figwheel-main (1)
- # graalvm (16)
- # honeysql (9)
- # hyperfiddle (2)
- # jobs-discuss (2)
- # lsp (36)
- # luminus (1)
- # malli (11)
- # off-topic (13)
- # pathom (1)
- # portal (1)
- # portkey (3)
- # reitit (25)
- # reveal (1)
- # rewrite-clj (5)
- # spacemacs (2)
- # sql (4)
- # vrac (90)
I remember having to set this up before too, especially the GPG stuff was challenging. Our solutions are pretty similar too 🙂 https://github.com/nedap/speced.def/blob/4d2982a546fb671952f4b3833b854eb3751a6f67/.circleci/config.yml#L61-L68
Interesting! My problem was always in exporting/importing keys. I follow this guide https://joemiller.me/2019/07/signing-releases-with-a-gpg-project-key/ but always stumble on creating a “thing” which doesn’t require a password. My incompetence in this area is vast
To be fair I think the key I use in our public repo's doesn't have a password; The password would have to be in the env-vars too either way so it wouldn't make a big difference
If anyone's wondering how to do this with tools.deps based projects, I used a similar pattern in edn-avro https://github.com/cddr/edn-avro