https://github.com/emojitracker/emojitrack-feeder

:dizzy: consumes Twitter Streaming API for Emojitracker
https://github.com/emojitracker/emojitrack-feeder

Last synced: about 2 months ago
JSON representation

:dizzy: consumes Twitter Streaming API for Emojitracker

• Host: GitHub
• URL: https://github.com/emojitracker/emojitrack-feeder
• Owner: emojitracker
• Created: 2014-04-06T20:15:26.000Z (over 10 years ago)
• Default Branch: master
• Last Pushed: 2022-10-05T22:27:20.000Z (almost 2 years ago)
• Last Synced: 2024-05-21T12:22:56.979Z (4 months ago)
• Language: Ruby
• Homepage:
• Size: 148 KB
• Stars: 34
• Watchers: 6
• Forks: 7
• Open Issues: 13
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# emojitrack-feeder

This consumes the Twitter streaming API, processing and feeding the Redis instance for the rest of Emojitracker.

## Development Setup

 1. Make sure you have Ruby 2.7.3 installed. (This repository is configured with a VSCode devcontainer to make this easy.)

 2. Get the repository and basic dependencies going:

        bundle install --without=production

 3. Copy `.env-sample` to `.env` and configure required variables.

 4. Make sure you have Redis installed and running (if you are using the devcontainer, an instance is provided).

    The rules in `lib/config.rb` currently dictate the order a redis server instance is looked for.

 5. Run all processes via `foreman start` or `forego start` or `heroku start` (depending on which you have installed).

Be sure to note that while the processing power is fairly managable, the feeder component of emojitrack requires on it's own about 1MB/s of downstream bandwith, and ~250KB/s of upstream.  You can use the `MAX_TERMS` environment variable to process less emoji chars if you don't have the bandwidth where you are.

Note, **DO NOT** run the feeder process with REDIS_URL configured to the production server, ever.