From 7dfc802b753f21afcb656b13d30d49bc548ac150 Mon Sep 17 00:00:00 2001
From: tv <tv@krebsco.de>
Date: Fri, 17 Apr 2020 22:41:53 +0200
Subject: Reaktor.API: make configurable

---
 README.md | 41 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)

(limited to 'README.md')

diff --git a/README.md b/README.md
index fecb136..c5a5cc6 100644
--- a/README.md
+++ b/README.md
@@ -29,3 +29,44 @@
     withArgs ["config.json"] main
     :r
 
+# HTTP API
+
+  Reaktor can provide an HTTP API so external applications can control
+  its behavior.  At the moment this is restricted to send PRIVMSGs to
+  registered channels.
+
+## Enable the HTTP API
+
+  To enable the HTTP API, a listening address has to be configured.
+  This address can be a TCP port, specified like follows:
+
+    {
+      "API": {
+        "listen": "inet://127.0.0.1:7777"
+      }
+    }
+
+  or it can be an Unix domain socket, specified like follows:
+
+    {
+      "API": {
+        "listen": "unix:/path/to/reaktor.sock"
+      }
+    }
+
+## Example usage of the HTTP API
+
+  Let's say your reaktor instance has been configured to listen to
+  inet://localhost:7777, and the register plugin has been configured
+  to join #somechannel.  Then it is possible to send a PRIVMSG to
+  this channel using e.g. following command:
+
+    curl -fsSv http://localhost:7777/ \
+        -H content-type:application/json \
+        -d "$(jq -n '{command:"PRIVMSG",params:["#somechannel","derp!"]}')"
+
+  And similarly if unix:/path/to/reaktor.sock has been used instead:
+
+    curl -fsSv --unix-socket /path/to/reaktor.sock http://dontcare/ \
+        -H content-type:application/json \
+        -d "$(jq -n '{command:"PRIVMSG",params:["#somechannel","derp!"]}')"
-- 
cgit v1.2.3