Each call by rabbitmq should be parametrizable by a edn.map

refactor things in namespaces:

• github-ns
• message-broker

etc

currently the events are raw sent to client. Lot of info it sent. Reflect if it is possible/usefull to implement a filter or just delegate the filtrage to application developer and/or to shell-handler

Implement something like this for future, it should be possible to listen to other events then repository events, since currently this the only one possible.

;; this specify which events we want to listen to and notify then.

;; public is in GitHub terminology what is not private.

{:criver-config {
             ;; full-repo-name: owner/repo-name,  events: this are the events which you are interested for
             ;; https://developer.github.com/v3/activity/events/

             ;; TODO: issue event of repository isn't implemented
             ;; this events are targeting a repository. there are others for user/orgs which are interesting too. (later)
             :repository-events [
               {:full-repo-name "MalloZup/fullrocketmetal" :events["repository", "issue"]},
               {:full-repo-name "MalloZup/missile" :events["repository"]},
               {:full-repo-name "MalloZup/kubeojo" :events["repository"]},
             ],

             ;; -----  TODO: THIS IS NOT implemented ----------------
             ;; implement this later on
             ;; user events
             :user-events [
             ;; user-full contains also the private and public events  (need authentication
             ;; public contains only public events
               {:user "MalloZup" :events["user-full"]},
             ],
             :organisation-events [
             ;; organisation public events
               {:organisation "openSUSE" :events["org"]},
             ]
            ;; --------------------------------------------------------------
            ;; rabbitmq or kafka
            :message-broker {:type "rabbitmq" :config {
                                                       ;; TODO: exchange-name it might be passed to each event. Here is global
                                                       :exchange-name "branzino"}
                            }
}}

an user should specify via EDN which event he wants to use

Research about queue of rabbitmq on client side

[consumer] Received a message: fb, delivery tag: 23, content type: text/plain, type: github.repo

desc:

Create rocket.chat bot which monitors pull requests on Github and reminds about reviews.

• we need to add a sleep timeout for daemon configurable for the server.
• we need to seprate first basic things as CLI:
  ** init function need to initiate various connection => done
  ** start function will launch the server as daemon => done

research how to interface with other storage

• https://zookeeper.apache.org/doc/current/zookeeperStarted.html#sc_InstallingSingleMode
• ceph

etc

• initialize the exchange queue correctly

pass the payload which contains all the metadata of an event to a ENV variable which can be accessed by the script handler so this can be filtered

add logging library to cosmic-river

This event should be sent by a message broker. IT should be an abstraction and not hardcoded to rabbitmq

By default the config is the PWD where the binary is executed.
It should be passed as parameter custom to CLI additionally, eg should be possible --config blab

add authentification user map to server so we have more rate-limit

Implement apache kafka as message broker alternative to rabbitmq

A River plus a cosmos would be great or any other ideas reflecting the name 🚀

• Every 5 min or customizable timeout, watch for new events
• make the daemon function to main

later

• implement config file location as parameter

IT might be already that with the langohr library we could acess a remote server rabbitmq but I'm not sure about this.

Implement the shell handler

This namespace should contain all message broker specific functions

Document all the possible variables and their behaviour for server and client