Live data from Hacker News

Show HN: Beehive – An open source IFTTT powered by Go's templating engine

github.com

41–45 of 45 posts

Re: Show HN: Beehive – An open source IFTTT powered by Go's templating engine

#41

Quite interesting that this just been posted. I have to produce an events application with a UI similar to this: http://i.imgur.com/e0R1Kp5.png The UI is already done, so that's not the reason for the post. My question is, on the backend, is there a pattern I can use to easily execute the steps? I know there is a combination of logic, cron, a MQ and a db to hold the flow. But I am unsure on how best to approach the d…

Conversio.com offers abandoned cart recovery

Re: Show HN: Beehive – An open source IFTTT powered by Go's templating engine

#42
Neat! I've been looking at a few things similar to this for various purposes recently, one thing I'd like is some sort of mix of this plus some content analysis system for managing an email inbox and then performing actions based on and using the data contained within, for example an email comes in with some sort of semi-structured data / information - it's contents is analysed, it's put in some sort of group like a 'this is an SNMP alert' then the data is formatted / munged into another form of structured / passable days and then routed off to another email address, I.e. Create a markdown / whatever table, Look for IP addresses and FQDNs, pair them if they're on the same line and create an extra column with a human-usable hyperlink, send it on to an email that logs a ticket in whatever ticket management system is in use at the receiving end. That's just one simple example I could make up off the top of my head, but I'd like to easily create some neat logic rules based on the content and then use some of that content to decide where it should be routed onto, again to use a ticketing / helpdesk situation as an example just because it's what I thought of just then - an email comes in and if it contains certain keywords or phrases a response will be sent back with a table / list of information to fill out in the form of questions like 'please include the following information in your reply...' and it might have some basic information gathering steps for the end user like getting their IP address, OS etc... then when they reply the system could pickup that data, munge / transform it into some sort of standard / structured format, do some more troubleshooting like pinging the IP provided, doing a whois, perhaps relating the data to a list of clients or something and then passing it on to the right team or ticketing system via email again. I think the key to this would be to use something like the OSS product mentioned here that's more modern and lightweight coupled with a nice query / rule builder interface that's fast and responsive and easy to test. Business rules / logic apps I've used in big corps in the past have been a combination, mix of, or all of the following: slow and resource hungry, proprietary with all forms of vendor lock-in, hard to build rules and apply them, require up to a whole team to support and maintain them, and often not technically focused / directed.

Re: Show HN: Beehive – An open source IFTTT powered by Go's templating engine

#43
When I started learning Elixir/Phoenix this type of system was the first thing that came out of my mind when I was covering the Erlang/BEAM/OTP parts because of their nature.

If anyone else is interested in starting something similar in Elixir just ping me :)

Re: Show HN: Beehive – An open source IFTTT powered by Go's templating engine

#44
post #22

"Shortly" we had that topic here already: https://news.ycombinator.com/item?id=4441913 But most of the stuff is not alive anymore... But there are some interesting new ones: https://github.com/cantino/huginn https://trigger-happy.eu/infos not sure if this is alive: https://sourceforge.net/projects/semanticwebpipe Do you know some other (open source) event and agent system tools? (there are tons of commercial hosted I…

Project Flogo: http://flogo.io

Re: Show HN: Beehive – An open source IFTTT powered by Go's templating engine

#45

Quite interesting that this just been posted. I have to produce an events application with a UI similar to this: http://i.imgur.com/e0R1Kp5.png The UI is already done, so that's not the reason for the post. My question is, on the backend, is there a pattern I can use to easily execute the steps? I know there is a combination of logic, cron, a MQ and a db to hold the flow. But I am unsure on how best to approach the d…

that interface looks really useful, is there anyway I could get my hands on something like that. It'll be of even greater benefit if you can describe the process of building that interface. edit: nevermind I read the comments down the thread
Post reply on HN