Skip to content

Run the npm start after pull docker and get errors #39

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

Closed
HolyB opened this issue Feb 28, 2017 · 7 comments
Closed

Run the npm start after pull docker and get errors #39

HolyB opened this issue Feb 28, 2017 · 7 comments

Comments

@HolyB
Copy link

HolyB commented Feb 28, 2017

No description provided.

@kengz
Copy link
Owner

kengz commented Feb 28, 2017

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.

@kengz
Copy link
Owner

kengz commented Feb 28, 2017

Btw, the second error is from telegram bot. Just to be sure, have you updated the config file with the latest key?

@kengz
Copy link
Owner

kengz commented Feb 28, 2017

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

@kengz
Copy link
Owner

kengz commented Mar 1, 2017

oh you dont. only set "ACTIVATE": true, for what u need. When not using Telegram, make sure you set "ACTIVATE": false, for telegram

@kengz
Copy link
Owner

kengz commented Mar 1, 2017

hmm ok, let' try npm uninstall telegrambot and npm uninstall hubot-telegram. error seems to point to the activation of those

@kengz
Copy link
Owner

kengz commented Mar 1, 2017

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

@kengz
Copy link
Owner

kengz commented Mar 1, 2017

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!

@HolyB HolyB closed this as completed Aug 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants