This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (9)
- # alda (21)
- # announcements (1)
- # beginners (68)
- # boot (241)
- # braid-chat (18)
- # cider (32)
- # cljs-dev (4)
- # cljsrn (11)
- # clojure (60)
- # clojure-dusseldorf (1)
- # clojure-germany (1)
- # clojure-poland (212)
- # clojure-russia (64)
- # clojure-sg (10)
- # clojurescript (212)
- # core-async (1)
- # css (14)
- # datomic (1)
- # emacs (9)
- # funcool (2)
- # hoplon (18)
- # jobs (1)
- # ldnclj (1)
- # lein-figwheel (5)
- # leiningen (3)
- # om (190)
- # onyx (46)
- # parinfer (13)
- # proton (3)
- # re-frame (7)
- # reagent (10)
- # ring-swagger (2)
- # slack-help (3)
- # specter (1)
- # yada (31)
I do not understand the startup section of the dashboard. What's behind the core.clj file that you want to run? and in which project add (def env (onyx.api/start-env env-config)) in onyx-starter or onyx-dashboard?
You’re supposed to go sexp by sexp through core.clj in onyx-starter evaluating forms until you get here
(def env (onyx.api/start-env env-config))
That will start the “enviornment”, which the dashboard with connect to
What you could do is run this test, but block right before the
@(promise) or something. That will keep the environment up and running for you you to connect the dashboard to
What happens is during the test, Onyx has some convenience functions that stand up the infrastructure needed for an Onyx cluster in-memory. At the end of the test, in the
finally block, it’s shut down. I just suggested blocking with
@(promise) if you wanted to stop the test from tearing down the in-memory infrastructure so that you could connect to it with the dashboard.
@a.espolov: Using the dashboard is going to be a little tricky for that particular example
If you wanted to run 5 instances of
:filter, say, in addition to 1 instance of an input and 1 instance of an output, you would need at least 7 “peers” running either locally or across your cluster.
It is hard for me to evaluate whether onyx to my task. Suppose that there are several types of tasks: a. perform get request + disassemble + add reply to database b. run phantomjs run query + disassemble + add reply to database c. send email
and it is not clear how to declare a data schema and work with data. https://github.com/onyx-platform/beginners-guide/blob/master/chapters/chapter-3.md here says that there is an automatic database schema generation
@a.espolov: Those headers are suggestions with things that you can do with Onyx data, and more generally with Clojure data.
Onyx doesn't ship something like that out of the box. It's a design suggestion for user applications.
@michaeldrogalis: onyx ClojureSG talk has been given. Time to write my Jepsen post!
our usual tools, CircleCI + AWS CodeDeploy, and then upstart + some bash (there’s always some bash) to actually start jars
we have a nifty script which ensures that only one instance in an ASG actually submits jobs
That sounds neat. I'm glad you're up and running, that deserves a big congrats.
Marching steadily to the 0.9.0 release. Stateful operations will get expressiveness. Streaming engine upgrade on its way too, will be right on par with the fastest known design.