cog
cog copied to clipboard
operable
Bringing the power of the command line to chat
`Carrier.Messaging.GenMqtt` was first introduced when we reworked the chat provider API in summer 2016. The goal was to provide a `GenServer` style API on top of basic MQTT queue usage....
reference #1342 Currently adding roles and users to groups requires the user to hit two endpoints: `POST /v1/groups//users` and `POST /v1/groups//roles`. Instead we should just use the group create and...
There are a few inconsistencies with Cog's api. For example, when returning an error, some resources return json with an `errors` key and a list of errors, some return an...
Currently models are encoded to json via either a `Poison.Encoder` implementation or a phoenix view. This leads to inconsistent output of data for users dependent on where they access the...
Right now I'm manually updating install docs as part of each Cog release, it would be nice to automate this by building and releasing the book as part of every...
We have integration tests for connecting to chat, but we should also add an integration test for connecting to Relay, installing a bundle, and executing a command.
@tborels mentioned that he'd like more control over who is listed here, which makes sense. We could add an optional env var that allows you to override the users who...
If Cog has not yet been bootstrapped but a user attempts to talk to it via direct message or by attempting a command invocation, we should reply in chat that...
Most users will probably get the bot working and will want to immediately talk to it. Instead of telling them to go download, build, and run a series of commands...