This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-05
Channels
- # aleph (1)
- # announcements (18)
- # babashka (145)
- # beginners (70)
- # calva (34)
- # cider (3)
- # clj-kondo (98)
- # cljdoc (5)
- # cljs-dev (13)
- # clojure (134)
- # clojure-europe (57)
- # clojure-nl (4)
- # clojure-uk (4)
- # clojurescript (40)
- # code-reviews (3)
- # conjure (1)
- # core-async (5)
- # data-science (3)
- # datomic (8)
- # fulcro (9)
- # google-cloud (2)
- # inf-clojure (9)
- # jobs (1)
- # lsp (9)
- # malli (25)
- # polylith (4)
- # reitit (4)
- # releases (2)
- # remote-jobs (3)
- # rewrite-clj (8)
- # shadow-cljs (34)
- # tools-build (1)
- # tools-deps (67)
Ya, it's really nice to be able to build/push in dockerless environments, right?
There are still some things in https://github.com/atomisthq/jibbit that I'm continuing to experiment with.
• I like to version control parameters like (base-image repository and digest, tagging strategy, whether to aot or not, etc.), so I like to add a jib.edn
alongside my deps.edn
. I feel like that could be controversial.
• the aot
thing has been interesting - it makes enough of a difference for cloudrun that I really wanted to have it but it slows down the build. I'm still trying to decide whether compiling the clj should be default or not
• a profile for running babashka in cloudrun could be useful too. It's just so fast (even with the http entrypoint)
• some default seccomp/apparmor profiles to go along with kube deployments