deploy on Heroku

[lagleki]

I wish there was a fast method of deploying Kassy on Heroku.

[drkno]

Potentially something that could be contributed? Currently there is docker which is a starting point. It would be good to support, but isn't something we can currently prioritise.

[matthewhartstonge]

For this to work, there doesn't seem to be much change needed albeit - assuming it just works on heroku. It looks like package.json needs to be updated with an engine, and a web script added.
So you should end up with something like the following, notice the change in engines and scripts.

{
  "name": "kassy",
  "version": "3.5.1",
  "description": "Extensible general purpose chat bot.",
  "main": "main.js",
  "dependencies": {
    "babel-plugin-transform-strict-mode": "^6.3.13",
    "babel-polyfill": "^6.3.14",
    "babel-preset-es2015": "^6.3.13",
    "babel-register": "^6.3.13",
    "babylon": "^6.8.0",
    "chalk": "^1.1.3",
    "cline": "^0.8.2",
    "colors": "^1.1.2",
    "deasync": "^0.1.4",
    "facebook-chat-api": "1.1.0",
    "figlet": "^1.1.1",
    "fs-extra": "^0.26.3",
    "monkey-patches-node-telegram-bot-api": "0.0.1",
    "node-telegram-bot-api": "^0.21.1",
    "npm": "^3.7.5",
    "redwrap": "*",
    "request": "^2.72.0",
    "rimraf": "^2.4.4",
    "sandbox": "^0.8.6",
    "sanitize-filename": "^1.5.3",
    "skyweb": "0.0.2",
    "stripcolorcodes": "^0.1.0",
    "tmp": "^0.0.28",
    "ws": "^0.8.0"
  },
  "devDependencies": {
    "chai": "^3.5.0",
    "grunt": "latest",
    "grunt-contrib-watch": "^1.0.0",
    "grunt-mocha-cli": "^2.1.0",
    "grunt-run": "^0.6.0",
    "mocha": "^2.4.5"
  },
  "engines": {
    "node": "4.4.5"
  },
  "scripts": {
    "test": "grunt test",
    "start": "node main.js",
    "web": "node main.js"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/mrkno/Kassy.git"
  },
  "author": "Matthew Knox",
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/mrkno/Kassy/issues"
  },
  "homepage": "https://github.com/mrkno/Kassy"
}

[lagleki]

Can anyone confirm that Telegram gatewaying is working?

[drkno]

@lagleki you should ask @phillipadsmith

[phillipadsmith]

@lagleki Yes, it is working as far as I can tell, i.e., the bot I'm running is up on Telegram (more so that Skype!)

[drkno]

Skype is one of those pet problems.... Should have a SkypeBot integration soon to fix the problem permanently.

[phillipadsmith]

SkypeBot

Can you say more about this? Very curious...

[drkno]

Basically a WIP of https://developer.microsoft.com/en-us/skype/bots

[phillipadsmith]

Oh, those Skype bots! Sweet. :-)

[lagleki]

@phillipadsmith Skype integration doesn't work on Heroku? But why?

[drkno]

@lagleki its more a matter of Skype in general being broken everywhere thanks to #133 and other upstream regressions. Hopefully when the SkypeBots branch has landed we can forget about this issue.

[phillipadsmith]

@lagleki Yep, what @mrkno said. :-)

[parasdsingh]

@matthewhartstonge I tried deploying to heroku using the package.json edit. Unfortunately it didn't work. So I proceeded on with the recommended Procfile.

web: node main.js facebook

PS: Logging into Facebook is pain. They keep blocking Heroku servers for security purposes

The application runs but with a few issues.

• During startup, after modules are loaded I see the following error

2016-10-08T17:18:13.340358+00:00 app[web.1]: Loading module 'update'...     [DONE]
2016-10-08T17:18:13.347076+00:00 app[web.1]: fatal: Not a git repository (or any parent up to mount point /app)
2016-10-08T17:18:13.347078+00:00 app[web.1]: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
2016-10-08T17:18:14.143608+00:00 app[web.1]: Starting integrations...

• 60 seconds after startup, I see the following error which crashes it.

2016-10-08T17:19:04.025109+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch

I realize this one might be fixed by changing the Procfile to

worker: node main.js facebook

but I'm unsure since Concierge need to listen to HTTP traffic via the integrations. I've seen a patch for this by adding a stub express.js GET listener.

Any suggestions?

[drkno]

@ParasDPain @matthewhartstonge even if you do get it to launch on Heroku, the filesystem will be readonly (which means no persistent configuration, no module installation/uninstallation). Potentially you could partially get around the problem by committing a config and the modules (Hubots approach) or using the CLI options to point the module directory to /tmp which is r/w but it still isn't ideal.