-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting this to run issue and deploying with zeit question/issue #128
Comments
This bot is deployed to Heroku @Toxxn, not Zeit's now, maybe this could be mentioned in the contributing guidelines if a user would like to deploy their own version of it @amandeepmittal. The reason this uses Heroku is that the LevelDB database is stored locally with the bot. Now deployments are immutable meaning the filesystem can't be written to. |
Just to go over what happens with the bot it uses a similar queuing system to delay tweet where any tweets that match the query string (#100daysofcode) instead of being tweeted out as soon as they are hit the stream they're added to an object and assigned a random time (defined in the The counter your seeing is possibly because nothing has come into the object that contains the tweets that have matched the search criteria. |
@spences 10 I will use your comment in the guidelines. |
I got this to deploy, however it's acting strange,
it's starting to build okay, but gives me an error
it seems to just loop with the tweet counter...
Any help would be appreciated!
Thanks!
The text was updated successfully, but these errors were encountered: