Closed HolyB closed 7 years ago
Btw, the second error is from telegram bot. Just to be sure, have you updated the config file with the latest key?
The files in config/
mentioned at the second line here. Specifically for Telegram: https://github.com/kengz/aiva/blob/master/config/example-default.json#L23
oh you dont. only set "ACTIVATE": true,
for what u need. When not using Telegram, make sure you set "ACTIVATE": false,
for telegram
hmm ok, let' try npm uninstall telegrambot
and npm uninstall hubot-telegram
. error seems to point to the activation of those
Hmm weird. Somehow it's still triggering the telegram deployment. Did u edit both the default.json and production and json? Npm runs the first by default, and the second if specific production flag
Hmm is it working on slack now? Try to talk to the bot "@aiva ping" and it should reply you (or use whatever you name the bot).
If so then it should be fine. The single error log might be related to the currently open issues; that I have to dig separately.
No problems!
The Docker build hasn't been updated in a while; refer to #26 and #9
For now I'd recommend running on a direct machine, if that's possible? would be stabler, and easier to debug too.