This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-15
Channels
- # announcements (10)
- # asami (5)
- # babashka (49)
- # babashka-sci-dev (8)
- # beginners (25)
- # calva (98)
- # cider (2)
- # clj-kondo (22)
- # clojure (32)
- # clojure-dev (12)
- # clojure-europe (32)
- # clojure-nl (3)
- # clojure-spec (3)
- # clojure-uk (10)
- # clojurescript (12)
- # community-development (1)
- # conjure (71)
- # cursive (7)
- # datalog (6)
- # events (2)
- # figwheel-main (2)
- # fulcro (4)
- # jobs (2)
- # kaocha (3)
- # lsp (43)
- # membrane (12)
- # missionary (9)
- # off-topic (61)
- # pathom (7)
- # polylith (2)
- # reagent (38)
- # remote-jobs (4)
- # shadow-cljs (17)
- # specter (1)
- # tools-deps (38)
- # vim (51)
- # web-security (5)
@cap10morgan about the bb.edn pods, in this video Daniel Amber uses uberscript in combination with pods: https://youtu.be/jm0RXmyjRJ8 It might be good to support that too, e.g. just prepend load-pods into the uberscript or so, derived from bb.edn pods
👍 2
Or maybe we can support babashka.pods/declare
or so, a programmatic equivalent to the declarative one and re-use the code as much as possible
@borkdude For pods that need to communicate over a socket, do we need to add that to the bb.edn
pod declaration? Something like {:pods {my.socket/pod {:version "0.1.0" :transport :socket}}}
? Or is it expected that these can do a :describe
over stdio?