search

ekmartin / slack-irc

Connects Slack and IRC channels by sending messages back and forth.
MIT License
587 stars 155 forks source link

Only token accepted when Slack now uses a full URL #28

Closed WDShannon closed 9 years ago

WDShannon commented 9 years ago

There is only a token accepted in the config.json file, but when I create a slackbot, they give me a personal URL to use instead. Am I doing something incorrectly here?

ekmartin commented 9 years ago

Hi! You should be creating a Slack bot user (not adding a Slackbot integration): image

It's available from the same place you found the Slackbot integration. It's a bit confusing :confused: Then you should get an API token like this: image

WDShannon commented 9 years ago

Aha! I was using the SlackBot, not a regular bot. Thanks for the explanation!

ekmartin commented 9 years ago

No problem :)

WDShannon commented 9 years ago

So, you have a docker linked in the bottom of the readme on your page, can you explain what that is used for? Sorry for such a simple question.

ekmartin commented 9 years ago

It's just a Dockerfile that sets up an Ubuntu container with node.js and slack-irc - no need for it if you don't want to run slack-irc inside a Docker container :)

WDShannon commented 9 years ago

So, I would use that to keep my slack-irc runnig in the background of my server?

ekmartin commented 9 years ago

No, you don't need Docker for that. You can use anything that's made for keeping a process alive as a daemon. If you're cloning the repository you can run index.js with node through something like nodemon or forever.

I'm running slack-irc on an Ubuntu server, so I have an init.d service that runs index.js with forever. It looks like this: https://gist.github.com/ekmartin/8423b95bb15196e33196 - however it'll work nicely if you just install forever and run forever start index.js --config config.json too (which will start it in the background).

WDShannon commented 9 years ago

Thanks for that information, that's exactly what I want to do.