tnguyen14/github2twitter

post event updates from github to twitter

github2twitter

publish github notifications to twitter

This app check Github's user's received events API every 5 minutes and publish any new event to a twitter account. This app can be deployed with docker.

Usage

:; docker-compose up -d

Stagger

If there are more than 1 event to update, the updates are staggered out in 1 minute interval by default. This stagger interval can be changed through the environment variable TWITTER_STAGGER.

Private Events

If a GITHUB_TOKEN env variable is set, the app will authorize with Github's API and get private events as well. If it is not set, it defaults to public events.

Environment Variables needed to run

• GITHUB_USERNAME
• GITHUB_TOKEN (optional, enable private events)
• TWITTER_CONSUMER_KEY
• TWITTER_CONSUMER_SECRET
• TWITTER_ACCESS_TOKEN
• TWITTER_ACCESS_TOKEN_SECRET
• TWITTER_STAGGER (optional, default to 60000 (1 minute))

These should be declared in a .env file.

Sample .env file:

GITHUB_TOKEN=632ad16ec20ddssaf7436d2daffds9da8a14f965c
GITHUB_USERNAME=tnguyen14
TWITTER_ACCESS_TOKEN=26dfad503-hg7A8CwVHdfdafeU1CWSdfyAOWhAUp
TWITTER_ACCESS_TOKEN_SECRET=dfddsfadfsdf342432413eadsM3Q3LbdfafhnZadfesM
TWITTER_CONSUMER_KEY=oTtYUU30adFdDtmJjrOgwj6Q
TWITTER_CONSUMER_SECRET=RkAw4Zx8Dadfad34DDDA3xzMu19gBCddKQvM5AUU2J3zSm8

License

Copyright (c) 2015 Tri Nguyen Licensed under the MIT license.

github2twitter's Issues

Consider using Lambda?

https://medium.com/@emckean/create-a-simple-free-text-driven-twitterbot-with-aws-lambda-node-js-b80e26209f5#.m9hgjq3i6

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

use alpine-node to reduce image size

https://github.com/mhart/alpine-node

use couchdb

use levelup

instead of #2, consider using levelup https://github.com/Level/levelup as no complex querying or indexing is required for this project.

Stagger not working?

The stagger function doesn't seem to be working right? Perhaps write a test for it?

add test