Fork me on GitHub
#untangled
<
2016-05-11
>
kenbier01:05:55

moving the migrations to the resource path so they are emitted as final artifacts fixed the issue

ethangracer14:05:04

@kenbier They couldn't be in in the src directory without triggering that error?

ethangracer16:05:58

@mahinshaw just implemented untangled websockets and made a cookbook, check it out: https://github.com/untangled-web/untangled-cookbook/tree/master/recipes/websockets

kenbier17:05:32

@ethangracer: unforunately i believe boot does not allow overlap between src and resource directories.

kenbier17:05:40

:source-paths   #{"src/client" "src/server" "src/shared" "scss"
                   "test/server" "test/client" "vendor/src"}
 :resource-paths #{"resources" "src/server/adstage-report-center/migrations”}

kenbier17:05:16

would yield an error

ethangracer17:05:01

huh, I haven’t played much with boot so not familiar with its needs

kenbier17:05:04

clojure.lang.ExceptionInfo: Assert failed: The :source-paths, :resource-paths, and :asset-paths must not overlap.
                            (empty? (set/intersection paths parents))

kenbier17:05:26

yeah, its makes some different assumptions

therabidbanana18:05:08

@ethangracer: This cookbook/untangled-websockets looks pretty awesome - excited to try it out in our project. Seems like it's the case, but just to clarify - with this setup all reads/mutations go over the websocket? Seems like the client example overrides networking completely, but I don't know the details of the untangled client well enough to be sure.

ethangracer18:05:25

that’d be a question for @mahinshaw — he wrote it! It does look to me like everything goes over the websocket if the mutation has a non-falsey value for the :remote keyword

therabidbanana18:05:17

Ah, I guess also thanks @mahinshaw !

mahinshaw18:05:02

@therabidbanana: Welcome. Yes the entire client network gets overriden, and all mutations and reads go over websocket.

therabidbanana18:05:21

That seems to make sense to me - we'll try it out and see how it works for us. Excited for push notifications because currently we've got a thread that blocks a certain read until work happens on the server and saves to the database.

mahinshaw19:05:19

If you use the basic components, you get websocket traffic for free. Push is something you hook up on the side.