Consolidate slurpers into this project.

[smashwilson]

Peril is a lot more distributed that in has to be. Even though you can write slurpers in any language and plug them in, we only have one slurper in Python and four in Ruby.

Let's just bring everything in locally and call it directly.

• [x] hubslurp
• [x] mailslurp
• [x] rssslurp
• [x] stackslurp

[smashwilson]

Oh, right, mailslurp runs as a Sinatra frontend.

I'm not sure how I'm going to make that one work. Maybe I can serialize events into a file, then consume it from the slurper?

[smashwilson]

I now have Dirslurp, which slurps yml files from a set of directories and interprets them as Event collections. That should do for Mailslurp.

/cc rackerlabs/mailslurp#2

[rgbkrk]

I guess I'm not sure why they can't still be separate projects, but all run on the same host.

[smashwilson]

I guess I'm not sure why they can't still be separate projects, but all run on the same host.

Simplicity.

With everything as Ruby source in the same project, I can:

• Deploy a single repo, which will simplify the Ansible playbook considerably;
• Share models, superclasses among all slurpers, not to mention unifying things like dependency management - reducing basically all of them to a single class each.

The major impetus for keeping them separate was to enable any of us to write slurpers in any language, using the JSON spec as the only interface. But, all but one of the slurpers are in Ruby and written by me, anyway. This'll be a big gain in enabling me to churn them out quickly.

[smashwilson]

Also, I'm still not sold on the Dirslurp thing. I'll probably keep it around just in case but I kind of want to have a Sinatra endpoint that Slurpers can extend somehow. :thought_balloon:

[smashwilson]

Okay, now to update the slurper.rb.example file and :shipit: