orliesaurus / greetingslack Goto Github PK

Hi! Thanks for this wonderful project! Sadly, from 28.11.2022 on, free deployment using Heroku is not possible anymore :(

Starting November 28th, 2022, free Heroku Dynos, free Heroku Postgres, and free Heroku Data for Redis® will no longer be available.
To keep your apps running and retain your data, upgrade to paid resources as soon as possible.

So I wonder if there's an alternative host that I could use for free?

It would be rad if the welcome message could optionally be set from a file in the project root, like so:
https://github.com/edgi-govdata-archiving/archivers-greetingslack#about-this-fork

Why? Sometimes I set up bots like this for less technical organizations. Heroku (and editing envvars) is very advanced for them, but editing a file on github is something they are very comfortable with. In combination with auto-deploy, this allows them to more easily fend for themselves when I pass the project off to them :)

Hi all,

Deployed this today on a newly built workspace, getting the following method_deprecated warning. Any ideas anyone please?

2022-06-19T17:16:28.816798+00:00 app[worker.1]: DEBUG:urllib3.connectionpool:https://slack.com:443 "GET /api/rtm.start?token=<removed> HTTP/1.1" 200 60
2022-06-19T17:16:28.817507+00:00 app[worker.1]: INFO:root:{'ok': False, 'error': 'method_deprecated'}
2022-06-19T17:16:28.817545+00:00 app[worker.1]: Traceback (most recent call last):
2022-06-19T17:16:28.817555+00:00 app[worker.1]:   File "/app/bot.py", line 116, in <module>
2022-06-19T17:16:28.817684+00:00 app[worker.1]:     r = start_rtm()
2022-06-19T17:16:28.817686+00:00 app[worker.1]:   File "/app/bot.py", line 99, in start_rtm
2022-06-19T17:16:28.817765+00:00 app[worker.1]:     r = r["url"]
2022-06-19T17:16:28.817785+00:00 app[worker.1]: KeyError: 'url'
2022-06-19T17:16:28.930236+00:00 heroku[worker.1]: Process exited with status 1
2022-06-19T17:16:29.062921+00:00 heroku[worker.1]: State changed from up to crashed

Looks like runtime.txt needs to be updated to python-2.7.15 (assuming the rest of the app updates fine)

-----> Python app detected

 !     The latest version of Python 2 is python-2.7.15 (you are using python-2.7.13, which is unsupported).

 !     We recommend upgrading by specifying the latest version (python-2.7.15).

       Learn More: https://devcenter.heroku.com/articles/python-runtimes

-----> Installing python-2.7.13

 !     Requested runtime (python-2.7.13) is not available for this stack (heroku-18).

 !     Aborting.  More info: https://devcenter.heroku.com/articles/python-support

 !     Push rejected, failed to compile Python app.

 !     Push failed

Hi, getting the following error.

I am part of an organization where we want to greet users when they first enter our open #organizing channel, and explain the steps to taking part meaningfully in our group

greetingslack is so close to accommodating this, so I was hoping you might be open to an idea :)

Two things would be required:

1. allow the team_join message to be disabled via envvar
2. allow multiple envvars for various channel joins

For (2), I could easily imagine this taking the form of channel name being derived from envvars of a certain pattern, like GREETINGSLACK_MESSAGE_*

So:

• GREETINGSLACK_MESSAGE_RANDOM would be the message for #random
• GREETINGSLACK_MESSAGE_ORGANIZING_OPEN would be the message for #organizing-open

Curious your thoughts! Thanks so much for you consideration :)

Relies on: #12

Hi there! First off thanks so much for creating and sharing this! Super useful bot. :)

I followed the guide on this Medium article but am stuck after the deploy step. Here are the errors I get in the Heroku logs. A friend of mine tried as well on her Slack team and ran into the same problem. Did I miss a configuration step?

2017-06-07T20:00:47.258569+00:00 heroku[worker.1]: Starting process with command `python bot.py`
2017-06-07T20:00:47.896677+00:00 heroku[worker.1]: State changed from starting to up
2017-06-07T20:00:50.362696+00:00 app[worker.1]: Traceback (most recent call last):
2017-06-07T20:00:50.362718+00:00 app[worker.1]:   File "bot.py", line 58, in <module>
2017-06-07T20:00:50.362761+00:00 app[worker.1]:     r = start_rtm()
2017-06-07T20:00:50.362763+00:00 app[worker.1]:   File "bot.py", line 41, in start_rtm
2017-06-07T20:00:50.362793+00:00 app[worker.1]:     r = r["url"]
2017-06-07T20:00:50.362830+00:00 app[worker.1]: KeyError: 'url'
2017-06-07T20:00:50.478606+00:00 heroku[worker.1]: State changed from up to crashed
2017-06-07T20:00:50.464249+00:00 heroku[worker.1]: Process exited with status 1```

Right now, it only accepts channel id's

This would allow a default debug channel, and the ability to easily say in the docs "Create a channel called #greetingslack to test our the message on join" or something like that

Hi there! Thanks so much for this tool!

I've just realized that worker apps don't sleep, and so this app has unfortunately broughts all my free apps to a grinding halt for the month. (Wome of which are pretty critical, although shame on me for getting into that situations)

Getting things sorted on heroku is a little kafkaesque, as it's not as clear as throwing money at the problem :)

Anyhow, to help someone else from getting hit like this, I was wondering if there were any way to move this to using a web process, so that normal heroku sleeps come into play :)

Thoughts?

It seems the bot is pointing to the wrong im API call, and the new API call is conversations

I saw this in another slackbot. It was a hardcoded room that someone could create on the slack instance for testing, and just archive when done.

Would this be something you'd accept a pull request for?

I see usage of the word "broadcast" and things like that, so it's hard to be sure whether this is the sort of thing we're looking for. Even the code uses both "im" and "chat" endpoints, so it's hard to know :)

Can you confirm once and for all that this is a direct message as I suspect, and then I'd be happy to submit a PR clarifying this for the next person who really needs to spelled out explicitly ;)

I realized that os.environ[variable] isn't working with Heroku. I added a PR #19 with a solution using os.environ.get(variable).