Anton is a fork of Holly.

At this point Anton has diverged a lot from Holly, however some of our changes might make it upstream at some point :).

In production, Anton runs via DJB supervise (or any other watcher process). On LaterPay servers it's deployed as a RPM and subsequently run from its service directory /opt/lp-supervise/run which loads Anton's run script. Anton is configured through environment variables set in its supervisord/daemontools config.

Here is an example config:

[program:anton]
user=anton
command=/srv/anton/.env/bin/python /srv/anton/holly.py
autostart=true
autorestart=true
environment=IRC_SERVER="YOUR.IRCSER.VER"
    IRC_PORT="8080",
    HTTP_BINDADDRESS="127.0.0.1",
    HTTP_PORT="8000",
    JENKINS_CHANNEL="#laterpay-ci",
    GITHUB_AUTH_TOKEN="[create an auth token]"
    ...

Anton supports external modules distributed through pypi by utilizing setuptools entry_point functionality.

If your installable Python package declares an entry point for "anton.modules.external", Anton will happily import your module. Here is a simple example:

""" ./setup.py """
# ...setup.py boilerplate omitted
setup(
    name="irc.anton.boink",
    ...,
    packages=['boink'],
    install_requires=[
        'irc.anton',
    ],
    entry_points={
        'anton.external.modules': ['randomboink = boinkmodule',]
    },
)

""" ./boinkmodule/__init__.py """
# -* coding: utf-8 *-

from anton import commands

@commands.register("!boink")
def boinkfunc(callback, args):
    return "boink"

The above creates an external module that, when installed into a virtualenv with Anton itself, will be automatically loaded and register the !boink command.

By sending a HTTP POST to GitHub via curl. The following example is adapted from the original docs.

curl -u 'laterpay-jenkins' -d '{"scopes":["repo"],"note":"OAuth Token for LaterPay Bots (authorized by [YOUREMAILADDRESS])"}' https://api.github.com/authorizations

This will return a JSON object that has your GitHub auth token. The note will show up in your GitHub user account. As in the above example, LaterPay has a dedicated jenkins user on GitHub that we use for this kind of thing.

JIRA has the most convoluted setup path for OAuth imaginable. That said: Here is how you authorize Anton on JIRA:

First, use openssl to generate a RSA key pair:

openssl genrsa -out anton.secretkey 2048
openssl rsa -pubout -in anton.secretkey

Now follow these steps:

• Log into JIRA as an Administrator
• Go to Settings -> Add-Ons -> Application Links
• Enter the URL of your Anton bot (or any URL, really) and click "Create New Link"
• Click "Continue"
• Enter an application name like "Anton IRC bot" and select "Generic Application", leave the other fields empty.
• Click "Continue"
• Now click "Edit" next to the "Anton IRC bot" entry
• Click on "Incoming Authentication"
• Set consumer key to the value of JIRA_AUTH_ID in Anton's config (for example: "anton")
• Set consumer name to "Anton IRC bot"
• Paste the public key without the -----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY----- lines into the "Public Key" field
• Click "Save"
• Log out of JIRA!

You will need to put the private key either into config.py or into the JIRA_AUTH_PRIVATEKEY environment variable. In this case, it's good to know that DJB envdir will replace ASCII 0 with newline characters when reading files in an envdir.

Finally it's time to authorize Anton. Do NOT use an JIRA administrator account for this (because: security!). Inside Anton's virtualenv run this:

bin/jirashell -s [your JIRA server URL] -od -ck [JIRA_AUTH_ID] -k /path/to/anton.secretkey -pt

• If, like me, you don't have browsers on your development VMs, you'll need to patch lib/python2.7/site-packages/tools/jirashell.py line 52 to output auth_url! I submitted a pull request for that.
• This command will launch a browser and go to your JIRA server. This is why you logged out before. Now log in with an unprivileged account (for example a member of the "Developers" group, which has access to all tickets which you want the bot to have access to).
• Authorize the application.
• jirashell will output a OAuth1 token and secret. You need to put these into JIRA_AUTH_TOKEN and JIRA_AUTH_SECRET.

Finally... you're done.

Anton's hangouts module uses a hack to go through Google Calendar to create Google Hangout links that IRC users can join. You need to obtain the necessary configuration values from two places: Your Google Developer console and Anton's hangouts module.

1. Create device client credentials on your Google developer console for Anton, choose "Other" as its OS.
2. Click on "APIs & auth"->"Consent screen" and set an application name. I recommend "Anton, the IRC bot".
3. Set the environment variables GOOGLE_HANGOUT_CLIENT_ID and GOOGLE_HANGOUT_CLIENT_SECRET to the new client id and secret accordingly.
4. Run the module to receive authorization credentials. You'll need internet access for that. python -m anton.modules.hangouts
5. Use your browser to navigate to the provided URL and enter the provided code while Anton polls Google for an access token. Allow access through a user account who belongs to your organization if you use Google Apps for Business. Also make sure to set GOOGLE_HANGOUT_CALENDAR_ID to a calendar which is not used for other purposes!
6. Complete the process in under 30 minutes.
7. Put the acquired refresh token into your config.

Enable "Automatically add video calls to events I create" in Google Calendar's settings for the user who authorized Anton to access his calendars.

Anton supports GitHub post requests and Jenkins callbacks.

Clone it, create a virtualenv and pip install it:

git clone https://github.com/laterpay/anton.git anton
virtualenv .env
.env/bin/pip install -e anton

Kristian (holly@doismellburning.co.uk) is maintaining Holly for the long term; contact him if you have any Holly issues/questions/opinions. LaterPay's fork was primarily architected by @jdelic.