This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-30
Channels
- # babashka (46)
- # beginners (234)
- # bristol-clojurians (4)
- # cider (7)
- # clj-kondo (39)
- # cljdoc (8)
- # cljs-dev (10)
- # cljsjs (10)
- # cljsrn (24)
- # clojure (84)
- # clojure-brasil (7)
- # clojure-europe (12)
- # clojure-germany (4)
- # clojure-italy (3)
- # clojure-nl (41)
- # clojure-spec (17)
- # clojure-uk (66)
- # clojurescript (64)
- # conjure (161)
- # cursive (12)
- # data-science (45)
- # datomic (20)
- # devops (11)
- # docker (2)
- # duct (9)
- # events (7)
- # figwheel (1)
- # figwheel-main (20)
- # fulcro (32)
- # graalvm (5)
- # helix (82)
- # jackdaw (9)
- # jobs-discuss (19)
- # kaocha (11)
- # local-first-clojure (1)
- # malli (6)
- # meander (3)
- # nrepl (12)
- # off-topic (2)
- # other-lisps (15)
- # pathom (14)
- # rdf (6)
- # re-frame (8)
- # reactive (1)
- # reagent (5)
- # reitit (4)
- # rum (3)
- # shadow-cljs (77)
- # spacemacs (3)
- # sql (9)
- # test-check (31)
- # tools-deps (13)
- # vim (62)
- # xtdb (18)
It doesn't actually use docker for anything unless you request it to run the container or upload it to the docker instance. When it's composing layers/container images, it does so, logically, as a collection of tarballs
it also uses the google distroless containers by default, which are pretty small (smaller than alpine) and allow you to layer in debian packages if you need to
I have my whole clojure project using bazel, but if you just wanted the devops portion, you could easily use rules_foreign_jvm to reuse a lein deploy
or lein install
jar/war and then have rules_docker layer that onto a java image
rules_docker will automatically follow the dependencies set up by rules_jvm_external (under the hood, this is coursier, the same as SBT) and add the necessary classpath for you
nice if you're already using bazel, but probably a lot to bite off if you don't have any experience with it