This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-03
Channels
- # announcements (11)
- # atom-editor (8)
- # aws (16)
- # babashka (34)
- # beginners (59)
- # calva (32)
- # cider (8)
- # clj-kondo (43)
- # cljs-dev (52)
- # clojure (26)
- # clojure-europe (11)
- # clojure-italy (2)
- # clojure-nl (5)
- # clojure-spec (16)
- # clojure-uk (44)
- # clojurescript (5)
- # core-async (21)
- # cursive (14)
- # datomic (53)
- # figwheel-main (4)
- # fulcro (5)
- # graphql (6)
- # java (3)
- # kaocha (5)
- # leiningen (6)
- # local-first-clojure (1)
- # malli (25)
- # off-topic (40)
- # other-languages (1)
- # pathom (5)
- # pedestal (3)
- # re-frame (4)
- # reitit (2)
- # reveal (8)
- # rum (21)
- # sci (16)
- # shadow-cljs (90)
- # spacemacs (8)
- # tools-deps (10)
- # vrac (6)
- # xtdb (12)
I mean this: https://github.com/slipset/deps-deploy/blob/master/src/deps_deploy/deps_deploy.clj
what's missing is an easy way to build pom.xml, currently a lot of build tooling complexity is either about updating or reading the pom
I tailored deps-deploy to my needs (e.g. use args instead of env for clojars username/token) and it's almsot gone: https://github.com/vlaaad/reveal/blob/master/build/deploy.clj
Yeah our one (not yet opensourced) is actually almost identical to deps deploy (it just wraps pomegrante/aether too), except it also supports private s3 wagons. I’m almost tempted to just patch deps-deploy with the code to do that, rather than extract and open ours.
I'd like to see thought go into credential management fwiw. I had a stab and discovered it's very tricky.
The other option is I guess to use cognitects s3 api to drive it; I think that hooks into all the possible AWS credential mechanisms
Though I think that would require you facading things for aether/pomegranate