Closed amitaibu closed 8 years ago
I'm sorry, npm run bs
is currently imcomplete.
Usually, you can access app
from /manager
in the subsite.
(If you are running example: http://localhost:3000/job/manager
)
However, in development of the app,
It takes long time to build the package each time app.bundle.js
is changed.
So, I'm using npm run bs
to serve app.bundle.js
, and change app.bundle.js
path in example/Main.hs
.
jobManagerJSUrl _ = "http://localhost:3001/dist/app.bundle.js
umm, I think this is not good way.
Yeah, I'm interested in "Elm" and PureScript. I might rewrite this with any alt js π. but, I canβt decide what to use yet.
Thanks!
π - however now when I open the URL I get:
I suspect it's because I don't have Redis running. Are you using a Docker container to run Redis and somehow connect it to your Yesod app?
I also think it's cause, although I can't conclude without server side log.
No, I'm not using Docker. Would you need Docker? This library only uses Redis.
I did commit related.
"allow to change connection info for redis" https://github.com/nakaji-dayo/yesod-job-queue/commit/380b0b3a563ce8574e199cbd89400713baafc110
I'll check it and report - thanks.
Yes, after I did a brew install redis
it works fine. Now I can start learning from your library ;)
Thanks for report !
It's not written in the README how to invoke the app, but from a quick look it seems
npm run bs
is the right step. However I now get:What am I missing?
(btw, cyclejs is great but I prefer Elm π )