This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-06
Channels
- # announcements (3)
- # beginners (83)
- # calva (11)
- # cider (24)
- # cljdoc (2)
- # cljs-dev (1)
- # clojure (216)
- # clojure-berlin (1)
- # clojure-dev (18)
- # clojure-europe (8)
- # clojure-italy (5)
- # clojure-losangeles (2)
- # clojure-nl (4)
- # clojure-spec (34)
- # clojure-uk (75)
- # clojuredesign-podcast (12)
- # clojurescript (33)
- # clojutre (13)
- # community-development (1)
- # core-async (38)
- # cursive (19)
- # datomic (28)
- # duct (3)
- # emacs (1)
- # events (5)
- # figwheel-main (3)
- # fulcro (93)
- # kaocha (20)
- # lambdaisland (2)
- # off-topic (40)
- # pathom (17)
- # pedestal (8)
- # quil (1)
- # re-frame (14)
- # reitit (19)
- # shadow-cljs (34)
- # sql (8)
- # tools-deps (6)
- # vim (1)
- # xtdb (8)
- # yada (18)
Hi. A duct noob question: in duct configuration, is there a way of having a "base" value for a key that's merged with a new value in each profile? So, for (absurd) example, if my base profile looks like this:
{:duct.profile/base
{:duct.core/project-ns foo
:foo/database {:db "mydb" :username "myuser"}}
:duct.profile/dev
#duct/include "dev"}
I want to be able to specify that the value for :foo/database
is merged with any value with the same key in each profile config. So, if my dev.edn
looked like this:
{:foo/database {:db "anotherdb"}}
the final value for :foo/database
would be (when the dev
profile is active):
{:foo/database {:db "anotherdb" :username "myuser"}}
Currently, this config would causes the base profile value for :foo/database
to be completed replaced with the value from the dev profile though.
Any thoughts? Or am I just approaching this problem from the wrong angle?