This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-12
Channels
- # beginners (2)
- # boot (1)
- # cider (3)
- # cljsrn (28)
- # clojure (70)
- # clojure-russia (1)
- # clojure-spec (21)
- # clojure-uk (2)
- # clojurescript (16)
- # component (10)
- # data-science (5)
- # datomic (9)
- # emacs (5)
- # fulcro (2)
- # jobs (1)
- # juxt (1)
- # klipse (23)
- # lumo (1)
- # mount (12)
- # off-topic (4)
- # parinfer (1)
- # re-frame (20)
- # ring-swagger (2)
- # spacemacs (4)
@pandeiro: usually you would only keep "`required`" config params in a classpath. you can replace an existing config file in a classpath by another config file in a classpath using :resource
:
(cprop/load-config :resource "path/to/another/config-in-classpath.edn")
@tolitius Thanks; so the solution I came up with was to manually exclude the classpath config prior to building the uberjar for deployment; that way the actual production config is used, not merged with the repo's "production-like" config
The reason for having a production-like config checked in was for production CLJS builds and being able to run the production uberjar in docker locally
@tolitius just convenience 🙂 I want to have long names in the code, but shorter names at the REPL
@pandeiro I see. I usually keep a "`the repo's "production-like" config`" in dev-resources
which is in classpath during development, but never builds into an uberjar