This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-13
Channels
- # aleph (16)
- # announcements (8)
- # aws (5)
- # babashka (54)
- # beginners (48)
- # calva (7)
- # cider (7)
- # clojure (209)
- # clojure-brasil (4)
- # clojure-europe (20)
- # clojure-italy (12)
- # clojure-nl (21)
- # clojure-uk (69)
- # clojurescript (24)
- # cursive (11)
- # datascript (7)
- # datomic (47)
- # emacs (14)
- # graphql (20)
- # hoplon (25)
- # jobs (1)
- # kaocha (1)
- # leiningen (14)
- # meander (7)
- # off-topic (44)
- # other-languages (1)
- # pathom (20)
- # re-frame (2)
- # reagent (51)
- # reitit (3)
- # remote-jobs (1)
- # shadow-cljs (46)
- # spacemacs (5)
- # sql (65)
- # tools-deps (86)
- # vim (11)
Danke je wel @U052852ES
@skuro right. passing env vars to a subprocess can be done like this:
$ bb '(shell/sh "bb" "-e" "(System/getenv \"FOOBAR\")" :env {"FOOBAR" "123"})'
{:exit 0, :out "\"123\"\n", :err ""}
so here I invoke bb as a sub-process which reads the env var FOOBAR, which I pass from the parent process
@skuro
If you need anything beyond clojure.java.shell
you can drop down to ProcessBuilder
.
e.g. like here: https://github.com/borkdude/babashka.curl/blob/3104d234a63fca71f0d3557c5d3dc23f4fbc294f/src/babashka/curl.clj#L24
ProcessBuilder also accepts env vars.