Discourse Slackdoor Plugin

Personalização Plugin
1

DEPRECATION NOTICE

This plugin is now deprecated.

There is no plan to maintain or enhance it.

As of August 17, 2019, it still works but with limitations.

In particular:

  1. It doesn’t unfurl messages that don’t start with the link (this was always the case).
  2. It does not really do what one would expect in threads; the message is “unfurled” in the main channel.

In addition, outgoing webhooks are no longer recommended by Slack. They recommend creating a Slack App for this kind of integration now.

You may find this plugin useful as is, despite these limitations, but doing so comes with the above limitations and the risks that come with using software that is no longer maintained.

It is unclear whether there is any existing alternative to this plugin, so there is likely an opportunity for someone else to make something that solves this problem in a better way.

The discourse-slackdoor plugin allows Slack to unfurl links to your private Discourse instance.

Usage

When you post a message that starts with a link to a post or a topic in your private Discourse instance, a bot will post a message that contains the unfurled content as a reply.

Setup

  1. Configure an outgoing webhook on your Slack instance.
  2. Install and configure the discourse-slackdoor plugin.

Configure an Outgoing Webhook in Slack

Set the following values for your outgoing webhook:

  • Channels: All
  • Trigger Word(s): <https://forum.example.com/t/
  • URL: https://forum.example.com/slackdoor/knock
  • Token: (autogenerated, but copy value to add to your plugin settings)

You can also choose a name and icon for the bot’s posts.

Install and Configure Discourse-Slackdoor Plugin

  1. Install the plugin using this how to guide.
  2. Go to the Site Settings for your Discourse instance and type slackdoor into the filter to show the settings for the plugin.
    • enabled
    • token
    • username

The token should be set to the value that is generated by Slack when you create the webhook.

The username should be a user that can see topics you want to be able to share to Slack (but not topics that you don’t want to share).

Issues or Questions?

Please post any issues or questions in this topic.

13 curtidas
Help configuring Slack Discourse plugin
Allow Slack to unfurl/expand links to "login-required" Discourse instance
Discourse for Private Communities
Code review request for `slackdoor` plugin
Prevent Slack from unfurling anything for login-required sites
Prevent Slack from unfurling anything for login-required sites
2

A compatibility issue with this plugin was introduced in Discourse commit eaf87f07701b70903dcc88a7235371a00cc61083.

If you are on that version or newer of Discourse, you should update this plugin.

Discourse is creating their own officially supported Slack plugin and this is a feature on their todo list, so hopefully in the not-too-distant future this plugin will become obsolete :wink:

4 curtidas
5

Qual é o status deste plugin? Ele ainda funciona? Verifiquei o plugin oficial do Slack (obsoleto) e sua substituição, mas parece que o foco não é permitir a unfurling de URLs em instâncias privadas do Discourse.

6

Isso ainda é útil, @mcwumbly, ou está totalmente obsoleto?

7

Este plugin agora está descontinuado.

Não pretendo mantê-lo ou aprimorá-lo.

Ele ainda funciona, mas com limitações.

Em particular:

  1. Ele não expande mensagens que não começam com o link (isso sempre foi o caso).
  2. Ele não faz exatamente o que você espera em threads; a mensagem é “expandida” no canal principal.

Além disso, webhooks de saída não são mais recomendados pelo Slack. Eles recomendam criar um Aplicativo do Slack para esse tipo de integração agora.

Até recentemente, tínhamos usado este plugin apesar desses riscos, mas decidimos desinstalá-lo recentemente, pois estava causando mais confusão do que benefícios.

Não tenho conhecimento de nenhuma outra integração existente que ofereça a capacidade de expandir mensagens para instâncias privadas do Discourse neste momento, então as pessoas podem continuar a achar este útil como está, mas fazê-lo vem com as limitações acima e os riscos de usar software que não é mais mantido.

Há uma oportunidade para que outra pessoa crie algo que resolva esse problema de maneira melhor.

O README e a OP/Wiki acima foram atualizados de acordo.

4 curtidas