This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-04
Channels
- # adventofcode (171)
- # beginners (160)
- # boot (13)
- # chestnut (2)
- # cider (6)
- # cljs-dev (15)
- # cljsjs (35)
- # cljsrn (1)
- # clojure (139)
- # clojure-argentina (3)
- # clojure-brasil (1)
- # clojure-greece (31)
- # clojure-italy (5)
- # clojure-russia (5)
- # clojure-spec (18)
- # clojure-uk (11)
- # clojurescript (42)
- # clojurex (6)
- # core-async (12)
- # cursive (14)
- # dirac (13)
- # emacs (13)
- # events (1)
- # fulcro (46)
- # graphql (7)
- # leiningen (10)
- # lumo (3)
- # mount (31)
- # off-topic (20)
- # onyx (30)
- # perun (4)
- # planck (47)
- # re-frame (28)
- # reagent (14)
- # ring (5)
- # shadow-cljs (3)
- # spacemacs (7)
- # specter (13)
- # timbre (3)
- # unrepl (65)
- # yada (8)
Hi all: let's say you've started you're dev
pipeline. What is the generally recommended way to signal to the rest of the app that you are in "development" mode?
@zalky that really depends on you, and the app. in a classic web backing with .edn
config file you will have different folders with different configs and you can then have inside there a :debug
key or something
@richiardiandrea: thanks for the suggestion. I found this while doing some research: https://github.com/weavejester/environ, dead simple to use for now.
@zalky bit of a clojure question really, buuuut, we have dev/dev.clj added to the classpath during development. Developers start their system from there, and the system function has :dev
hardcoded in as a profile.
Then we use that to read an Aero config. Then the code uses the config to decide what to do beyond there.
@dominicm: thanks for the response! Will keep that in the back pocket if environ is not sufficient.
@zalky We use this one: https://github.com/dunaj-project/crispin - it’s awesome, but not well known
It supports an in project config.clj file (which just contains edn) + overriding via environment variables and more (but the first two is how we typically use it)
We set environment variables in our CI server so you can override per environment without creating different config files
Would it make sense to make an issue on Boot to separate the resolution and download of plugins from the adding of them to the classpath? More context here https://github.com/Deraen/sass4clj/issues/23
There's lots of places that want to be able to download the dependencies ahead of build time for lots of good reasons.