This project is discontinued and uses a longer supported part of the Twitter API. Courier now does receiving and sending of Twitter messages for RapidPro.

---

RapidPro Message Mage

High performance Dropwizard based webserver for receiving incoming messages on behalf of RapidPro.

Building

Without tests:

mvn clean package -DskipTests=true

Building with tests requires that Postgresql and Redis servers are running, then:

testdb/init.sh temba  # setup the test database based on schema from given database
mvn clean package     # run the build with tests against the test database

Running

The Mage configuration file contains several references to environment variables which must be defined on your system. This can be done easily in a wrapper shell script which sets the variables, e.g.

#!/bin/bash
export PRODUCTION=0
export DATABASE_URL=...
export REDIS_HOST=localhost
export REDIS_DATABASE=8
export TEMBA_HOST=localhost:8000
export TEMBA_AUTH_TOKEN=...
export TWITTER_API_KEY=...
export TWITTER_API_SECRET=...
export SEGMENTIO_WRITE_KEY=
export SENTRY_DSN=
export LIBRATO_EMAIL=
export LIBRATO_API_TOKEN=
exec "$@"

And then is invoked like:

./env.sh java -jar `ls target/mage-*.jar` server config.yml

Logging

To enable logging of Twitter stream messages, update the logging section of config.yml

logging:
    appenders:
      - type: console
        threshold: DEBUG
        target: stdout
    loggers:
        "com.sun.jersey.api.container.filter.LoggingFilter": DEBUG
        "io.rapidpro.mage.twitter.TwitterClients": DEBUG

Debugging

In IntelliJ:

1. Add new run configuration of type Application
2. Set main class to io.rapidpro.mage.MageApplication
3. Set program arguments to server config.yml