Getting this to run issue and deploying with zeit question/issue

[StephenEller86]

I got this to deploy, however it's acting strange,
it's starting to build okay, but gives me an error

(node:116) UnhandledPromiseRejectionWarning: OpenError: IO error: /home/nowuser/src/src/helpers/blacklistUsersDb/LOCK: No such file or directory
    at /home/nowuser/src/node_modules/levelup/lib/levelup.js:91:23
    at /home/nowuser/src/node_modules/abstract-leveldown/abstract-leveldown.js:41:14
    at /home/nowuser/src/node_modules/deferred-leveldown/deferred-leveldown.js:20:21
    at /home/nowuser/src/node_modules/abstract-leveldown/abstract-leveldown.js:41:14
    at /home/nowuser/src/node_modules/abstract-leveldown/abstract-leveldown.js:41:14
(node:116) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:116) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
No open port found. Make sure 'npm start' creates an HTTP server on a port (any).
More details: https://err.sh/now-cli/no-open-port-found
====================
TWEET COUNTER=100
====================
...

it seems to just loop with the tweet counter...

Any help would be appreciated!

Thanks!

[spences10]

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.

[spences10]

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 .env file range) before being tweeted at the interval set.

The counter your seeing is possibly because nothing has come into the object that contains the tweets that have matched the search criteria.

[amandeepmittal]

@spences 10 I will use your comment in the guidelines.