This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-04
Channels
- # arachne (1)
- # beginners (41)
- # boot (92)
- # capetown (8)
- # cider (10)
- # cljsjs (4)
- # cljsrn (42)
- # clojure (94)
- # clojure-india (1)
- # clojure-russia (48)
- # clojure-sanfrancisco (1)
- # clojure-spec (34)
- # clojure-uk (13)
- # clojurescript (29)
- # cursive (12)
- # datavis (4)
- # datomic (10)
- # dirac (63)
- # editors-rus (16)
- # emacs (57)
- # funcool (5)
- # hoplon (22)
- # jobs (2)
- # lein-figwheel (3)
- # leiningen (5)
- # onyx (51)
- # other-languages (2)
- # proton (1)
- # protorepl (2)
- # re-frame (34)
- # remote-jobs (1)
- # sfcljs (5)
- # spacemacs (1)
- # specter (2)
- # sql (20)
- # test-check (54)
- # yada (1)
@micha is that cljs-console
?
I btw use that and I like it a lot
yes it is in lambone as well
there is one little thing to be careful of, a dot in var name...I opened an issue there
basically as long as i'm computing i'm happy. when i'm playing with build options i'm annoyed š
I have no idea how I haven't see that lib before. That pretty much solves the problem that led me to start this discussion š
@richiardiandrea: oh nice, i'll fix that
thanks! I was thinking of a warning, just because you won't see them as env vars, not a big deal anyways
yes that was a good idea as well, basically this is good when using cprop
for instance
that has _
for going one level deeper in the map nesting and .
for replacing a -
it's environ
competitor
by totilius (aka -> mount
)
yeah, it is working fine, just in that https://github.com/adzerk-oss/env/blob/master/src/adzerk/env.clj#L8
when-not
+ warning
because you won't see it in the results and you might wonder why and spend some time banging your head
yeah true...
Micha btw why do we filter
I guess due to this: https://github.com/adzerk-oss/env/blob/master/src/adzerk/env.clj#L20 ?
ah yes, because then it becomes a symbol
like my applications usually have a handful of settings that are configured in the deployment
and regular environment variables in the upstart script seem to me to be very easy to deal with
but like if i need to configure which sql server to connect to i can just make a SQL_HOST
env var
yes I do that too, but for instance there is a log4j2
property to set a custom conf
and some other I don't remember
but I use env/def
mostly for dev in my profile.boot
typical example here:
(case ~type
"prod" (env/def
database_name "db-name"
database_username ""
database_password "")
"test" (env/def
database_name "db-name-test")
(env/def
conf "external-config.edn"
database_name "db-name"
database_username ""
database_password ""))
yes, you do an extra step š
and my command like is messy: boot dev -t dev
ok no wait
that defaults to dev of course
yes very true, here I basically use env/def
every time I need to setup a var programmatically, using boot
(defn set-env-props! []
(let [postgres-db (get (env/env) "database_name")]
(case ~type
"prod" (env/def
database_jdbc.url ""
search_url "")
"test" (env/def
database_jdbc.url (str "jdbc:postgresql://" (d/endpoint-with-port! "postgres") "/" postgres-db "-test")
search_url (str "http://" (d/endpoint-with-port! "elasticsearch")))
(env/def
database_jdbc.url (str "jdbc:postgresql://" (docker/endpoint-with-port! "postgres") "/" postgres-db)
search_url (str "http://" (d/endpoint-with-port! "elasticsearch"))))))
more code as you said š
i guess i do a lot of stuff in bash anyway, so it's natural for me to think in a certain way
and another disadvantage is that I need to wrap everything in conch
and in a pod
no but you are right, this is bash anyways
where "this" means something like https://gist.github.com/arichiardi/123518858254b7bd974543653c7027ba
@micha: First cut: https://gist.github.com/kennyjwilli/97f83cc49934bc08af4d3905487a9b49
boot push provides a :repo-map option, where you can define a repository map (makes perfect sense). However, what if you have more than 1 repo-map? Defining the repo-map the same way you would define repositories
[["whatever" {:url "cool-url"}]]
doesn't work (makes sense as well, it's not a map). Can boot push take multiple repo-maps?so you can do like
boot push -r whatever
@kurt-yagram: repo-map options is mostly for defining e.g. credentials for single deploy repository
if you need to deploy to multiple repositories you would define all in set-env! :repositories
and use multiple push tasks: (comp (push :repo "a") (push :repo "b"))
allright, the thing is: I wanted to have the repositories per task, and repo-map looked like a nice solution - but it didn't work out since I wanted to give a -r option to push. Now, I just defined 2 other tasks, in each of them setting a different repo-map for the push command. Thanks anyway
how can you split tasks over different files? Now, I tried to do
(load "versioning")
, but I get an error it can't find my file: java.io.FileNotFoundException: Could not locate boot/versioning__init.class or boot/versioning.clj on classpath.
. The file boot/versioning.clj is present from the same directory of build.boot.hey all, iām revisiting the issue that is preventing me from supporting Boot in nightcode. if anyone has any new ideas for possible workarounds, please let me know. iād love to get it into the next release. https://github.com/oakes/boot-clj-issue
@kurt-yagram: why not use clojure.core/require
?
for example: (print (apply str (repeat 100 "hoi\n"))))
only prints 3 lines instead of 100?
Does anyone know how to get the offline status of boot? I'd like to pass that onto a task.
Wait nvm it's in the env