This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-26
Channels
- # admin-announcements (2)
- # aws (1)
- # beginners (21)
- # boot (61)
- # cider (5)
- # cljs-dev (94)
- # cljsrn (35)
- # clojure (106)
- # clojure-austin (3)
- # clojure-belgium (1)
- # clojure-dev (4)
- # clojure-dusseldorf (9)
- # clojure-greece (2)
- # clojure-mexico (1)
- # clojure-russia (40)
- # clojure-spec (61)
- # clojure-uk (17)
- # clojurescript (151)
- # code-art (1)
- # component (7)
- # core-async (4)
- # cursive (1)
- # datomic (9)
- # dirac (55)
- # funcool (12)
- # hoplon (118)
- # incanter (12)
- # jobs (8)
- # juxt (1)
- # lein-figwheel (6)
- # mount (2)
- # off-topic (2)
- # om (76)
- # onyx (28)
- # other-lisps (1)
- # planck (7)
- # re-frame (9)
- # reagent (13)
- # ring-swagger (2)
- # specter (1)
- # yada (22)
Would anyone running Onyx in-house be interested in a twice-monthly knowledge sharing session/show-and-tell-thing? It'd be interesting to see how companies are managing their Onyx deployments in the wild. We can answer questions during that time, too. Anyone else is welcome to lurk as well.
@michaeldrogalis: definitely would attend, as would a couple of my peers (aha!)
@michaeldrogalis: I'd be interested in lurking and perhaps presenting down the road. I got pulled into another project for the last few months, but should be back working with Onyx soon as the other project is wrapping up.
@michaeldrogalis: I think we would be interested at some point (too early now I suppose)
@nha @acron @manderson @jeroenvandijk @greywolve Cool, we could do the first one and talk about the new application template that's coming out for 25-30 minutes or something. @gardnervickers has lots to show.
... Timezones are going to be hard. Just from you all above, that stretches from the Pacific coast to eastern Europe at least.
I would like to tune in and listen as well
I'll send out a poll thingy later today or tomorrow so that we can pick an optimal time, then. Having some mind-share between the community will take us all a long way. 🙂
@michaeldrogalis: lets send poll out to the newsletter list too. I’d like to hear about what people want to hear from that too
Excellent. @tcoupland @v.solovyov @manderson @acron @nha: If ya'll are signed up for the news letter, can you PM me your emails so I can send directly? I'd look you up here later, but Slack deletes messages 10,000 back 😞
Anyone else who isn’t signed up for the newsletter, here is the link: http://eepurl.com/beFW_P
Unfortunately not. You could use a task with a timer trigger to inject “task” segments, but this is non-ideal because they wouldn’t be outputting to the same job
This will get better in a future release
We're unlikely to ever add a cron-scheduler to Onyx. It's out of scope for the project. You'd be much better served by a project that specifically does scheduling.
Individual tasks that perform some action on a timer, as @lucasbradstreet said, are one thing. But for job and task repetition, you should look elsewhere for a supporting tool.
Sketching out a scraper architecture in my head and trying to fit all the pieces together
something like mesos chronos or whatever kubernetes is doing is probably the right place to manage those sorts of jobs
alternatively have a process that just writes a segment to a kafka/whatever topic every now and again and make sure you monitor it
Yeah the main concern is having an easy ui rather than distributed systems guarantees. Thanks though!
@michaeldrogalis: (on Onyx in-house) we are not using Onyx yet, but hopefully in the near future. I’d love to lurk as well!
:thumbsup:
This is going to be fun
@fhanreich: Sounds good!