This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-06-25
Channels
- # admin-announcements (6)
- # beginners (38)
- # boot (65)
- # cider (22)
- # clojure (81)
- # clojure-berlin (15)
- # clojure-india (1)
- # clojure-norway (1)
- # clojure-russia (10)
- # clojure-sg (3)
- # clojurebridge (1)
- # clojurescript (94)
- # core-typed (44)
- # editors (6)
- # euroclojure (80)
- # events (7)
- # instaparse (9)
- # jobs (2)
- # ldnclj (14)
- # off-topic (8)
- # om (3)
- # reading-clojure (6)
@podviaznikov: hm, does it not make sense to sync the fileset?
output files in the fileset that is
@jeluard: that's cool! to make it semi-permanent one could aim BOOT_HOME at a permanent ramdisk
@alandipert: I think it doesn’t make sense to sync fileset (at least it doesn’t sound important). Just wanted to check maybe there are other tasks that needed to do similar decision
@podviaznikov: it reminds me of pandeiro/boot-http a bit, which can serve files from either place or classpath
re: the namespaces-as-pods concept
@alandipert: do you know if I can force boot to sync write files to the target-path? I have following boot file https://github.com/hashobject/blog.hashobject.com/blob/master/build.boot. What is happening is that my task boot-s3
syncs target/public
directory. But that directory is empty until all tasks would be executed
@podviaznikov: i notice that in the boot-s3 task you do the work before calling the next handler (as with-pre-wrap
does)
have you tried running the next task and then doing the s3 work?
that makes sense. I didn’t. Going to try now
otherwise there are ways to force the sync using internal boot things, but i wouldn't advise it
why don't you like the idea of syncing the fileset itself?
by doing that it would be possible to e.g. sync the fileset at different points in the pipeline
the primary motivation for using the fileset is to avoid the kind of coordination needed to read target
at the right time
I probably misunderstood your answer to my previous question:) I thought that you said that syncing target
is a better way
but anyway, I fixed boot-s3 and it worked now
thank for the tip
also I didn’t think about idea of having s3-task sync fileset in different points in the chain
now that you said it it looks interesting
finally got auto-deployment working with boot/perun. Now I have my blog configured to be build on heroku and deployed to s3 automatically after I commit & push change to GitHub
awesome
sorry i was unclear, my point was that in general, the less tasks look at the real filesystem, the more flexible they are
alandipert: Great! You’re revealing the inspiration fors pods, right?! Fantom looks so cute and cross-platform and cool. Have you tried it?
@danielsz: i haven't tried it, no, but it's not a lisp so i don't feel especially compelled to 😉
i was intrigued tho by the lengths they go to be compatible with both the jvm and clr
they even have their own intermediate bytecode that translates to either
Well, I guess this is the story: http://fantom.org/forum/topic/355
"Like many open source projects, what you see today is the result of work done in our spare time. So there hasn't been any explicit funding. Things will be shaking up in a couple weeks, and we'll start to work on Fan more or less full-time. I'll be blogging about that in Dec."
podviaznikov: i would recommend not using the :target-path
in any way while boot is running
podviaznikov: the target dir is just a place for boot to dump the final state of the fileset before it exits, so you can do things with the artifacts you build
while boot is running the target dir is unmanaged shared state, and as such there can be no guarantees about its contents
i can't imagine anything you can do with the target dir that you can't do with (boot.core/output-files fileset)
podviaznikov: for example https://gist.github.com/3fff1e472f730ea8b22f
the key part there is making the temp dir (line 5), and then syncing the fileset to that (line 11)
@micha: thank for your opinion. I’ll add this to boot-s3
Bodil live coded uKanren at EuroClojure, and people are raving about Adam Tornhill’s talks. BCN is where all the fun is. Waiting for the videos.
I was told the talks are going to be online but they aren't able to get them online the same day. You should be able to watch them soon though.
Adam Tornhill is my new hero, you should really really watch his talk once it gets online
he's got a cool blog http://adamtornhill.com/
wagjo: have you ever heard of a lisp in which macros receive their arguments macroexpanded but not evaluated?
it's strange, because i'd imagine it would be discussed somewhere, lisp is extremely well documented
so a macro can't propagate exceptions up the stack if something fails during macroexpansion
this is why we must now (ns foo <?php= isClojure ? ":gen-class" : null ?>)
or whatever the syntax is now 😉