This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-25
Channels
- # aleph (15)
- # beginners (65)
- # boot (46)
- # chestnut (3)
- # cider (1)
- # clara (11)
- # cljs-dev (5)
- # cljsjs (4)
- # cljsrn (13)
- # clojure (180)
- # clojure-dev (2)
- # clojure-italy (10)
- # clojure-russia (62)
- # clojure-spec (6)
- # clojure-uk (85)
- # clojurescript (45)
- # community-development (11)
- # crypto (3)
- # cursive (10)
- # datomic (94)
- # defnpodcast (2)
- # fulcro (4)
- # heroku (1)
- # hoplon (4)
- # jobs (3)
- # juxt (10)
- # leiningen (1)
- # luminus (4)
- # mount (13)
- # music (1)
- # off-topic (10)
- # onyx (2)
- # portkey (15)
- # proton (2)
- # re-frame (16)
- # reagent (10)
- # shadow-cljs (194)
- # spacemacs (2)
- # specter (2)
Hi @crimeminister could you define sub-Machfile support? There is the concept of extensions as shown here: https://github.com/juxt/mach/blob/master/examples/extensions/Machfile.edn (all the targets in the ext1.mach.edn
file are made available in the host Machfile.edn
Hi Jon, was thinking along these lines ^
i.e. invoking a Machfile in a sub-directory that is responsible for building a component of a larger system
I work in a mono-repo at work and if we don't factor our build scripts in some way insanity ensues
Off to read about extensions; at first blush it seems they might do the trick
Thanks!
Am guessing I could just mach/import
a Machfile from elsewhere in my repo…