This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-26
Channels
- # aws-lambda (1)
- # beginners (71)
- # boot (70)
- # bristol-clojurians (1)
- # cider (2)
- # clara (13)
- # cljs-dev (96)
- # cljsjs (6)
- # cljsrn (5)
- # clojure (74)
- # clojure-android (3)
- # clojure-austin (4)
- # clojure-dev (10)
- # clojure-russia (6)
- # clojure-spec (28)
- # clojure-uk (128)
- # clojurescript (64)
- # cursive (2)
- # datascript (18)
- # datomic (116)
- # dirac (1)
- # emacs (12)
- # events (10)
- # hoplon (109)
- # jobs (1)
- # jobs-discuss (21)
- # leiningen (2)
- # luminus (6)
- # off-topic (19)
- # om (21)
- # om-next (5)
- # onyx (4)
- # parinfer (29)
- # perun (20)
- # re-frame (53)
- # reagent (21)
- # remote-jobs (5)
- # ring-swagger (2)
- # spacemacs (6)
- # untangled (42)
- # vim (5)
@richiardiandrea : yes, I'm using require-amcros
let me see if I can get a min failure case, I have this weird setup where my org file generates everything, so it's ahrd to share atm
uhm, yeah, even an error message might be helpful
basically, I could share my org file, but people can't run it without my .emacs.d/init.el
might be best if I just screen sahred to http://livecoding.tv
uhm, I might be done for the day soon...what is the error you get?
woah...odd very odd
however, the macro is defined as:
(defmacro compile-time-read-file [& rst]
"Hello World")
I assume you call the macro like (compile-time-read-file)
?
oh ok, so that syntax is odd to me
ah ok, now it makes sense 😄
back when I was using lein, I was able to get a single *.cljc file to comiple twice: to define the amcro in the clj compilation then to use it via (:require-macros [name-of-self-namesapce]) to use the amcros in cljs apparently this doesn't work with whatever boot setup I have right now
macros in .cljc
files should go in :clj
clauses iirc
different namespace?
yeah, different namespaces = works same namesapce = does not work, despite http://dev.clojure.org/jira/browse/CLJS-1782
@ag tmux and the lack of reattach-to-user-namespace
also often cause issues with programmatic notifications
@qqq boot reload —help
should show a on-jsload
option or similar. That’s what you’re looking for I think
@tbrooke The Boot+Netlify user I thought of the other day is @grounded_sage
@tbrooke last I checked my builds still weren't working on Netlify. It's either the boot version was older than I was running or they haven't quite figured it out yet.
I made a serious push for boot to be made a priority. Even though they say that they don't normally make it a priority to get have languages/build tool set up until at least a couple of people ask for it.
Personally hasn't been a priority for me to have automatic builds yet as I have been working on some more critical pieces to my own code. So I haven't pushed for it for a while.
@grounded_sage I’ll ask them too - I know most folks use S3 but Netlify is fast, cheap, free wth the banner, and provides a lot of convenience get it set and you could could crank out Perun or even Hoplon sites in no time
@tbrooke S3/Cloudfront is also cheap, if you don’t need any of netlify’s advanced features like prerendering etc. confetti may also be interesting to you https://github.com/confetti-clj/confetti
It basically helps putting together the AWS puzzle pieces for static sites
Hello! Can I run boot-environ with .lein-env to get easily keys in the :keys map in my repo map?
If not, how can I use the env function of boot-environ inside the :repositories map?
I'm trying to get my datomic credentials inside my datomic repo with boot-environ
@tbrooke: yea S3 is great though I'm interested in SPA development. So handling auto deployments and feature branches are big wins for me. I'm also convinced they are on the money with a lot of decisions they make to be a worthwhile investment.
how can I get vals from .boot-env with the environ task? in the docs it's only showing how to set
but I want to keep my db creds in another file outside build.boot
@vinnyataide: shameless self-promotion, but I wrote a blog on using datomic pro with boot. It doesn't use environ, but it does use environment variables and (I think) has a reasonable discussion of what you need to do to get things working and why seemingly obvious things won't necessarily work
jesus then we're back again with why sequence of operations matters, I was trying to pull datomic before adding the repository, shame! your blog pointed that out, now I think I can work with environ
just made datomic creds work with environ in a .boot-env file 😄 made a little adjustment in @geoffs files and good to go, but now I have 3 set-env!'s, is that normal?
and 2 requires, one after my system is loaded and one before to load env
so I can get my env function before getting the http://datomic.pro dep
One thing that I would be cognizant of though is that having multiple set-env!
s with dependencies in them can cause Aether's transitive dependency resolution algorithm to fail in strange ways because you're not giving it the full set of dependencies to resolve at any one time.
I don't personally have much experience, but just thinking about it, I would try and make sure that your main app dependencies are all in the same (probably final?) set-env!
and put boot
task related things together before that.
@geoffs ohhhh that seems more like it, two concerns of course, one for my deps conf and other for my system itself... gonna refactor that
@geoffs one concern though is that one set-env! is for setting the datomic repository and the other is to get datomic itself
hmm, you should be able to set the datomic repository in the same set-env!
as where you declare the datomic dependency
I thought I'd gotten there with the examples in my blog post, but I see I did not. so maybe you can't? Seems like it should work though...
lemme check
Is there a way to attach the build timestamp to locally install
ed SNAPSHOT builds? If I do a simple boot pom jar install
, it will install a jar into my local maven without the build timestamp (e.g. myproject-0.1.0-SNAPSHOT.jar
). However, if I do boot pom jar push
, it will push a timestamped version of the jar to my repository (e.g. myproject-0.1.0-20160524.001833-1.jar
).