This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-19
Channels
- # admin-announcements (1)
- # beginners (26)
- # boot (6)
- # cider (14)
- # cljsjs (29)
- # cljsrn (19)
- # clojure (87)
- # clojure-austin (5)
- # clojure-belgium (10)
- # clojure-brasil (2)
- # clojure-dusseldorf (15)
- # clojure-greece (17)
- # clojure-russia (51)
- # clojure-sanfrancisco (4)
- # clojure-sweden (20)
- # clojure-uk (31)
- # clojurescript (111)
- # core-matrix (2)
- # cursive (9)
- # datascript (15)
- # datomic (41)
- # dirac (1)
- # emacs (8)
- # flambo (1)
- # funcool (4)
- # hoplon (72)
- # lein-figwheel (3)
- # off-topic (2)
- # om (79)
- # om-next (2)
- # onyx (17)
- # other-languages (16)
- # re-frame (62)
- # reagent (26)
- # remote-jobs (1)
- # rum (3)
- # spacemacs (5)
- # untangled (120)
@hlolli: huh, weird, I thought I did this before 😄
I sometimes get messages like Could not find metadata boot:core:2.6.0-SNAPSHOT/maven-metadata.xml in central (
at startup. But only once; if i run boot again I don’t get the message. Not a showstopper but i wonder what’s happening.
Had yet another idea. Other way would be a possibility to add a variable into boot.build, *ignore-missing-tasks*
(for lightweight projects that are not user in production/just for quick development).
Is there an "immediate" way to redirecting the out and err or dosh
?
I followed your advice about avoiding beanstalk guys thanks, ECS/EC2 seems like a way better solution in terms of manageability (is it even an english word?)
(using Alpine mini docker image)