This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-18
Channels
- # admin-announcements (1)
- # beginners (4)
- # boot (18)
- # cider (4)
- # cljsrn (17)
- # clojure (77)
- # clojure-austin (6)
- # clojure-greece (6)
- # clojure-spec (81)
- # clojure-uk (6)
- # clojurescript (32)
- # code-art (2)
- # core-async (12)
- # cursive (1)
- # datomic (1)
- # emacs (15)
- # funcool (1)
- # hoplon (108)
- # om (9)
- # onyx (83)
- # planck (1)
- # re-frame (3)
- # reagent (4)
- # specter (6)
- # spirituality-ethics (4)
- # yada (9)
heya guys, what’s the proper way to setup boot so that you can (:require
files from other roots outside of ./src/cljs
?
I’m trying :source-paths #{“../other/place/src/cljs/}
as well as src/cljs/specific-module
and alos src/cljs/specific-module/specific-file.cljs
, but they all fail for one reason or another.
With the last, the compilation fails. With the first, the compilation fails because it’s seemingly including every file in ..//other/place/cljs/
, but my existing cljs project doesnt include some of the necessary dependencies. In the middle case, the compilation goes through, but a call to :require-macros
macros fails with “cannot find module__init.class”.
I can get the :require-macros to not complain by including ../other/place/src/clj
instead of ../other/place/src/cljs/specific_module
, but then goog.resolve fails with a nameToPath error.
It just seems like any permutation has errors one way or another. Is it possible to do this or no?
(for clarity- I’m just trying to share code between sub-projects… I have a bunch of useful libraries and framework-ey type stuff sitting in the project root. I don’t have time to pull each of these out into fully independent modules, though, and so I figured it would be easiest to just make boot think those dirs were part of my project.)
that's a much cleaner way to do it because you don't need to merge the builds for the sub projects into your main build
@zaffy just to clarify you are looking to add env variables to your build pipeline not your application correct?
yes, trying to load DB connection parameters at startup from the environment vars @flyboarder
As far as my understanding goes 'boot-environ' is for setting task params not app params
As in your app will also need to know about how to load environ params
And doesn't have access to the ones set in the pipeline