This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-09
Channels
- # admin-announcements (5)
- # architecture (8)
- # beginners (7)
- # boot (41)
- # braveandtrue (1)
- # cider (77)
- # clara (3)
- # cljs-dev (56)
- # cljsjs (7)
- # cljsrn (7)
- # clojure (44)
- # clojure-austin (3)
- # clojure-brasil (1)
- # clojure-hk (3)
- # clojure-russia (137)
- # clojure-spec (14)
- # clojure-uk (44)
- # clojurescript (33)
- # cloverage (3)
- # core-async (10)
- # css (1)
- # cursive (16)
- # datomic (116)
- # devcards (14)
- # emacs (1)
- # events (1)
- # funcool (2)
- # functionalprogramming (1)
- # hammock-driven-dev (1)
- # jobs-rus (124)
- # lein-figwheel (1)
- # leiningen (1)
- # liberator (4)
- # melbourne (3)
- # mount (73)
- # off-topic (3)
- # om (4)
- # om-next (15)
- # onyx (38)
- # other-languages (4)
- # perun (2)
- # proton (36)
- # protorepl (2)
- # random (1)
- # re-frame (56)
- # reagent (7)
- # specter (4)
- # testing (1)
- # untangled (13)
- # yada (18)
@micha: have you seen this before? https://docs.gradle.org/current/userguide/gradle_daemon.html
i wonder how they handled the cwd problem
what’s a way to get images into your output ./target with boot such that I can reference them via url(‘images/foo.png’)
in css? is it as simple as sift :move
?
the target directory isn't good for that, it's better to serve files from the classpath in dev
and when you deploy you're probably not deploying to your own machine, you're probably making an uberjar or war file or pushing things to s3
the sift
task will move things around in the fileset, and correspondingly in the classpath
so locally I can just make sure i’m serving images/
from wherever, but how do I package up that dir later to ensure it’s included?
lets just assume I use a boot task to bunlde everything into the standard main.js and main.out dirs, then those two files are served from some s3 bucket
i suppose just sifting images/* into __ would do it, i’m just not sure what _ should be