Skip to content
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

Running on Heroku #4

Open
forresto opened this issue May 14, 2014 · 4 comments · May be fixed by #11
Open

Running on Heroku #4

forresto opened this issue May 14, 2014 · 4 comments · May be fixed by #11

Comments

@forresto
Copy link

FYI, to get this running on Heroku I had to make a couple of tweaks:

config.js, the process.env.PORT

outgoingWebhookServer: {
  port: Number(process.env.PORT || 5000),

lib/slack.js, the 0.0.0.0

var server = new Hapi.Server('0.0.0.0', config.slack.outgoingWebhookServer.port, {
@rknLA
Copy link
Owner

rknLA commented May 14, 2014

Want to submit that as a pull request, instead of inline code?

@turnrye
Copy link

turnrye commented Aug 9, 2014

What did you use for your Procfile? Mine is just "web: node ." and it seems to go down after a period of inactivity...

@forresto
Copy link
Author

forresto commented Aug 9, 2014

@RyanTurner I've been keeping the bot up as a single worker dyno, but that means I can't post slack -> irc. That works for me, since I'm just using it to archive. To keep a web one up, you need >1 dyno (or a hack like this: http://www.gingilipino.com/brian/keep-heroku-apps-up.html).

dannon pushed a commit to dannon/irc-slack-echo-fork that referenced this issue Aug 31, 2014
dannon pushed a commit to dannon/irc-slack-echo-fork that referenced this issue Sep 1, 2014
@zylinx
Copy link

zylinx commented Nov 4, 2014

needed to do this for debian too, thanks

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

Successfully merging a pull request may close this issue.

4 participants