You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
looks interesting and indeed does work, possibly also with a free plan Slack.
We're currently using SlackIn, does someone have experience if the free plan limits would represent an issue with this inviter too (i.e. a general Slack free plan limit)?
We had the inviter configured with the "join specific channels on new account" option.
This feature appears to only work with paid Slacks as I got to know while deploying an alternative to Heroku.
SLACK_CHANNELS
Comma-separated list of single guest channels to invite them to (leave blank for a normal, all-channel invite). In order to make this work, you have to have a paid account. You'll only be able to invite as many people as your number of paying members times 5.
Do we want to keep that URL and deployment or fix (upgrade) the other one?
I can provide a website change PR for the new one but would be happy if someone else would make one too.
I don't see any drawbacks in just setting up the new one as the 'main' one...
I've created a PR for the website to do the changeover. (InnerSourceCommons/innersourcecommons.org#56)
would it be worthwhile creating a (private?) repo to store the config/code of the inviter?
The only changes we made are custom credentials. Those I can definitely store in the vault @cewilliams has provided me with or we make a repo using GoPass. GoPass has been successfully vetted as being good&useful by colleagues of mine.
Activity
lenucksi commentedon Jul 29, 2019
We had the inviter configured with the "join specific channels on new account" option.
This feature appears to only work with paid Slacks as I got to know while deploying an alternative to Heroku.
The alternative for now lives here: https://innersourcecommons-inviter.herokuapp.com/
Do we want to keep that URL and deployment or fix (upgrade) the other one?
I can provide a website change PR for the new one but would be happy if someone else would make one too.
StingRayZA commentedon Jul 31, 2019
I don't see any drawbacks in just setting up the new one as the 'main' one...
I've created a PR for the website to do the changeover. (InnerSourceCommons/innersourcecommons.org#56)
would it be worthwhile creating a (private?) repo to store the config/code of the inviter?
lenucksi commentedon Jul 31, 2019
Thanks for making the PR.
What has been deployed is whatever has been the current master in rauchg/slackin as of Monday. [...] They don't do releases anymore since some years.
The only changes we made are custom credentials. Those I can definitely store in the vault @cewilliams has provided me with or we make a repo using GoPass. GoPass has been successfully vetted as being good&useful by colleagues of mine.
rrrutledge commentedon Aug 5, 2019
Since the
innersourcecommons-inviterlink on the main page is working again I deleted the magic join link from Slack that I had created at one point.rrrutledge commentedon Aug 5, 2019
InnerSourceCommons/innersourcecommons.org#57 should finish off fixing this.
lenucksi commentedon Aug 6, 2019
I would say that this is done for now. Thanks for making the PR's with the URL-updates and the reviews & tests.