Libretime: Add a link to chat.libretime.org in the docs

[Robbt]

This is in relation to the discussion on #148 - where libretime.slack.com was created and people can use it. I realized since that topic was closed it would make sense to make the slack site semi-official otherwise only the people who were on that topic will ever join it.

EDIT: We have moved to Mattermost on https://chat.libretime.org/ with open signup. A link needs adding to the docs

[gusaus]

Cool - I think @ned-kelly will be able to hook this up?

[hairmare]

Can anyone who knows Slack clarify how we could add a sign-up/register link to the docs? Where would that link need to point to? All I can find is some docs about being allowed into a new Slack workspace because you sign up with a company email address and Slack matching the domain name parts to a workspace.

[ned-kelly]

@hairmare - Send me a PM on Slack and I'll help you hook it up, we need to add a DNS record for https://github.com/outsideris/slack-invite-automation which I'll setup tonight.

[ned-kelly]

@hairmare - Just an update, you can add: https://libretime-slack.herokuapp.com/ to the actual Libretime docs/homepage like you said in the initial issue - Happy to add in DNS if you want (i.e. slack.libretime.org) if we want to remove the herokuapp.com and use our own domain. @Robbt also shot you a PM on slack about passwords etc

[Robbt]

So the landing page on #543 includes a link to Slack, if we end up merging that then we can close this. The only thing that we might want to coordinate is pointing the DNS but that's up to @ned-kelly & @hairmare to coordinate. It's probably fine to use herokuapp for now since if that service were to go down the invite would crash and I don't see any real benefit to setting up a DNS entry other than it hiding the fact that we are using heroku from people.

[hairmare]

I'll add the DNS changes, @ned-kelly can you let me know what is actually needed? I think it's worth it for consistency.

Is the app really safe to use? I'm seeing a lot of large communities manage slack invites manually and there must be some reason for this.

[Robbt]

I suspect that we might run into spambots at some point, but we could always reconsider this if we run into that problem. In my mind it's better to be open to new users since we are mainly keeping Slack focused entirely on informal conversation rather than using it for our decision making platform.

[gusaus]

I 'think' there might be a way for admins to approve the email signups.
Would that help? Either way, we should be greeting anyone who joins...
should be pretty easy to screen out the bots.

On Fri, Oct 12, 2018 at 1:11 PM Robb [e-mail] wrote:

I suspect that we might run into spambots at some point, but we could
always reconsider this if we run into that problem. In my mind it's better
to be open to new users since we are mainly keeping Slack focused entirely
on informal conversation rather than using it for our decision making
platform.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/LibreTime/libretime/issues/538#issuecomment-429448604,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAG9TNATUV7xVwwubgm-W5935s7p6vjrks5ukPdugaJpZM4XMGjh
.

[hairmare]

I'm not afraid of bots as much as I'm concerned about bad actors. Bots should get screened by Slash themselves for the most part. Also, admitting additional users to the slack shouldn't be an additional burden to Administrators. The herokuapp the @ned-kelly published seems to solve all these problems so I'm basically waiting for some docs on how to set up the DNS entries needed. I'd also like to take some time to look into the actual code behind the herokup app.

[ned-kelly]

Hi guys - sorry for the delayed response - away from computer - in short
it’s pretty unlikely that we will get spambots on slack due to the fact
that you need to join via a one-time invite token that is sent to your
email from the inviter that’s running on heroku...

Re the code - it’s just a simple node app that does the work that’s running
on heroku - it’s the project I linked earlier in our discussions.

Re larger scale - these guys (comma ai) are using it - (I’m a member here
also) https://comma.ai and they have over 5,000 members so it’s obviously
doing the trick ok / really I doubt we will reach 5,000 slack members.

Re the DNS ill jump on and get the records for you when I’m back on a
computer - should be just a CNAME from memory.

On Sat, 13 Oct 2018 at 7:16 am, Lucas Bickel [e-mail]
wrote:

I'm not afraid of bots as much as I'm concerned about bad actors. Bots
should get screened by Slash themselves for the most part. Also, admitting
additional users to the slack shouldn't be an additional burden to
Administrators. The herokuapp the @ned-kelly
https://github.com/ned-kelly published seems to solve all these
problems so I'm basically waiting for some docs on how to set up the DNS
entries needed. I'd also like to take some time to look into the actual
code behind the herokup app.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/LibreTime/libretime/issues/538#issuecomment-429464601,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ1MRUjZ8ZPWoWewccd8Jw1WWuDDQI5Sks5ukQaPgaJpZM4XMGjh
.

>

Sent from Gmail Mobile

[paddatrapper]

Has there been any movement on this?

[Robbt]

Nope. I think we could simply add it to the README & the Docs page as we wait for the various finishing touches required for the new launch page. The invite app created by @ned-kelly still works.

[dmnktoe]

The Slack invite page doesn't work anymore—always get a Failed! token_revoked response.

[Robbt]

@dmnktoe Thanks for pointing this out. As I didn't set this up I'm not sure how to fix it. We have been considering alternatives to Slack as well. So perhaps now is a good time to give one of them a test run, or perhaps @ned-kelly can fix it.

[nscpro]

How to connect LibreTime slack team? Invite page says "Token Revoke"

[Robbt]

Yeah, I think we can say the Slack is officially dead until this is fixed. Nobody is currently using it so this is just as well. How do people want to move forward with this ?

[paddatrapper]

I can stand a mattermost instance up early next week and open it for user registration

[Robbt]

So how does mattermost compare to rocketchat and zulipchat and Slack ?

I am totally down for us hosting our own instance at this point but where would it be hosted and could it possible for there to be an offsite semi-regular backup that other admins could access in case anything happens to the host ?

Also can we connect logins to github and/or restrict them in some way to prevent spam ?

Just curious. I definitely think it's a good idea to get something like this setup and I'd prefer something free software to proprietary slack.

[paddatrapper]

It seems the closest to what Slack currently gives us and it's the one I'm most familiar with. I also already have a working Ansible role to stand a mattermost server up

I can set it up in a container and give people admin access in Mattermost. It would then be tied into my usual backup system. Management happens through Ansible, so changes happen as a MR against that repo. I'm currently looking at shifting things over from LXC to Docker, so which repo I use may change, but I plan on ironing that out tomorrow when I start planning the architecture I use

Mattermost supports GitLab single sign-on, but not Github, but their email registration system is protected by anti spam and admins have power to ban users.

[Robbt]

Ok, I did an export of our current Slack workspace so that we can in theory start with something that isn't empty. I'll send you the link for that. Have you tried a slack import before ?

I am ok with Mattermost community edition if that is what you are most familiar with. What will be the URL it is accessible via ? Should we try to get @hairmare to setup a DNS pointer to something like chat.libretime.org ?

I sent the link to you via PM in Slack. Since I don't have your e-mail.

[gusaus]

So the issue is https://libretime-slack.herokuapp.com/ no longer works? Pretty sure that's 'cuz Slack changed it so you wouldn't have to use herokuapp for email signups.

If this is just something we can fix with some settings change (I'm not sure exactly what it would be offhand), wouldn't it make sense to do that?

[paddatrapper]

Ok, I did an export of our current Slack workspace so that we can in theory start with something that isn't empty. I'll send you the link for that. Have you tried a slack import before ?

I haven't tried it before, but seems easy enough according to the docs

I am ok with Mattermost community edition if that is what you are most familiar with. What will be the URL it is accessible via ? Should we try to get @hairmare to setup a DNS pointer to something like chat.libretime.org ?

Yeah, I'll set up something with a .paddatrapper.com domain for the moment, but once I have an IP address to point to for an A or CNAME record, chat.libretime.org would work well

[paddatrapper]

So the issue is https://libretime-slack.herokuapp.com/ no longer works? Pretty sure that's 'cuz Slack changed it so you wouldn't have to use herokuapp for email signups.

Well that is more just the catalyst - Slack is proprietary and closed. We have been wanting to move over to something else for a while, just haven't had the time to actually do it

[hairmare]

I can set up chat.libretime.org with either a A or CNAME record. Just let me know what you need.

[jbatesuk]

I'd love to get an invite to the Slack/Mattermost group when it's back.

[paddatrapper]

I started playing with my new way of setting things up today, I hope to have it finished and working tomorrow or Wednesday

[paddatrapper]

@hairmare can you add a A record for chat.libretime.org to 206.189.241.202?

[hairmare]

Done, chat.libretime.org should now resolve to 206.189.241.202

[paddatrapper]

I use sendgrid to send emails from mattermost. In order to reduce the chance that emails end up in spam, can you also add the following DNS records?

em1300.libretime.org 1800 IN CNAME u3467589.wl090.sendgrid.net.
s1._domainkey.libretime.org 1800 IN CNAME s1.domainkey.u3467589.wl090.sendgrid.net.
s2._domainkey.libretime.org 1800 IN CNAME s2.domainkey.u3467589.wl090.sendgrid.net.

[paddatrapper]

Right, mattermost is up and running, but there are a few things I need to do before I can open it to registration and use:

• [x] Fix storage permission issues
• [x] Generate Kubernetes ConfigMap from configuration file
• [x] Set configuration options
• [x] Import slack archive

[paddatrapper]

@Robbt can you re-send me the slack archive? I didn't download it in time

[Robbt]

i sent it again, this one expires in 7 days. also on slack DM

[paddatrapper]

https://chat.libretime.org is now open for use! If you have an existing slack account, use the reset password link with the email you used for Slack

[gusaus]

@paddatrapper I wasn't able to log-in with the same user/pw as Slack. Looks like my user is in the system, but the pw reset didn't make it to my email address. Wondering if this is an issue w/ others.

Thanks for setting this up!

[Robbt]

Site looks like it is down right now. Got a SSL error and the regular http site didn't load.

[paddatrapper]

@gusaus: Looks like my user is in the system, but the pw reset didn't make it to my email address

So the slack export set all emails to [email protected]... Which of course will never work for password reset. I have no idea how else to do the linking...

@Robbt: Site looks like it is down right now. Got a SSL error and the regular http site didn't load.

Grr... I'm trying to debug. Seems the cluster times out connecting to letsencrypt at the moment...

[Robbt]

@paddatrapper - is it possible to manually alter the e-mails for people so they can reset their password after the effect ? If this is feasible then what would be a good way for people to send you their e-mails so that they can be fixed ? I guess slack would work for people that had accounts and they could DM you there to avoid needing to setup a new account on chat.libretime.org or perhaps there is a better strategy ?

Hopefully the lets encrypt stuff isn't too painful to figure out. Thanks for your work on this.

[paddatrapper]

That should be possible. I'll check when I get the instance back up and running... I'm travelling tomorrow, so it may only be Tuesday though. Slack DM works, or email [email protected]

[gusaus]

So you need the email folks used when they signed up to our Slack? You're able to see those if you go to Admin / Manage Members... actually it looks like @paddatrapper or maybe even @Robbt have been able to access. I bumped up your role so you should have full access.

[gusaus]

Might also make sense to inform everybody in Slack (@channel in #general would notify all members) about the move and anything they may need to do.

[paddatrapper]

@hairmare can you please update the DNS record to be a CNAME to prod.cluster.bitcast.co.za? I gave up with DigitalOcean's DNS issues and moved things over to Google Compute. I'm going to test it for a few days and then open it to general access

[paddatrapper]

@hairmare have you had a chance to update the DNS record yet? I've used prod.cluster.bitcast.co.za so that the backend is abstracted and doesn't require you updating the DNS record if it changes again.

[gusaus]

@paddatrapper Are we still waiting for @hairmare to update the DNS or are there some other issues?

[paddatrapper]

Yup. Waiting on DNS

[gusaus]

@hairmare Is there anything you need to make the update? An active chat room should help us coordinate programs like Hacktoberfest and connect with participants.

https://discourse.libretime.org/t/libretime-participation-in-hacktoberfest/387

[Robbt]

@paddatrapper can we set up a temporary domain name for this or is that a pain with mattermost etc and your current setup. I suspect that @hairmare is busy with no free time and thus hasn't tended to this DNS request yet.

[paddatrapper]

No problem. It can currently be accessed at https://chat.bitcast.co.za I'll run the slack import on Monday

[hairmare]

I updated the DNS records. Please accept my apologies for not being responsive on this.

The following records should now resolve properly.

chat.libretime.org.      3600 IN    CNAME   prod.cluster.bitcast.co.za.
em1300.libretime.org.        3600 IN    CNAME   u3467589.wl090.sendgrid.net.
s1._domainkey.libretime.org. 3600 IN    CNAME   s1.domainkey.u3467589.wl090.sendgrid.net.
s1._domainkey.libretime.org. 3600 IN    CNAME   s1.domainkey.u3467589.wl090.sendgrid.net.

I'm looking forward to the slack import on Monday and switching back to the Mattermost Desktop app (after having abandoned it due to my $JOB being the only Mattermost instance I connect to)!

[paddatrapper]

Slack data imported and emails updated. People should now be able to verify emails using the links emailed to them and reset password from the sign-in page. You may need to update your username if desired. If there are any issues, shout

[gusaus]

I'm in! Seems to have a similar look/feel to Slack!

Thanks again @paddatrapper and @hairmare for setting this up.

[Robbt]

Got the e-mail to validate my e-mail but unfortunately the link didn't work and it said to contact the admin. I also tried to reset my password but never got an e-mail and I couldn't register my username as it's "already in use". I think my browser crashed when I first tried to click the validate link. Any help getting it working would be rad. Thanks for hosting this.

[paddatrapper]

I'll send a new email reset to you