This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-05-28
Channels
- # announcements (19)
- # aws (4)
- # babashka (17)
- # beginners (74)
- # biff (2)
- # calva (5)
- # cider (6)
- # clerk (14)
- # clj-kondo (12)
- # cljs-dev (3)
- # clojure (40)
- # clojure-dev (26)
- # clojure-europe (28)
- # clojure-nl (1)
- # clojure-norway (39)
- # clojure-sweden (1)
- # clojure-uk (4)
- # conjure (2)
- # docker (35)
- # emacs (24)
- # graalvm (15)
- # graphql (1)
- # gratitude (4)
- # holy-lambda (2)
- # hyperfiddle (8)
- # introduce-yourself (3)
- # jobs (3)
- # nrepl (2)
- # off-topic (9)
- # pedestal (8)
- # reitit (5)
- # releases (3)
- # remote-jobs (3)
- # yamlscript (1)
I'm thankfull for #CLX41ASCS and #C03S1KBA2 itself for being such an amazing productivity tool. Working directly on my kubernetes cluster to implement my software is just amazing. And so much more that can be done. Furthermore i'm really greatfull for how many great and experienced users are using clojure therefore we get stable libraries that are just really well done. Never seen such thing before. THANK YOU !!!


shoutouts to ring, httpkit, hiccup, data.xml, data.zip, next.jdbc and nearly every other lib i touch 😄
Care to comment on what you build on your K8s cluster? Custom resource defs, operators, controllers, or something else? I would like to know what benefits you are finding with babashka and clj in K8s land
I'm currently just woring on a normal application that can run test for our company in a cluster. The tests are run by kubernetes jobs which are managed by my application. I konw there is jenkins and stuff but the company wants a sofisticated tool that matches our requirements. Like displaying the report in one place and stuff. So in general i'm just coding the kubernetes "runner" stuff directly in the cluster to test out my functionality.