How to access plugin paths via URL?
Pilvinen is trying to access a local file in a Docker container via URL for a web hook, but is getting a 404 error. Falco explains that the URL path for a file in a plugin is https://discourse.example.com/plugins/plugin-name/folder/a.txt.
However, Pilvinen discovers that the plugin they’re using is not a native Discourse plugin, but rather a PHP-based integration. zogstrip points out that the plugin is in the #plugin:extras category, which includes extensions and integrations that are not native Discourse plugins.
Pilvinen decides to try a native Discourse plugin for Discord integration, which Falco mentions is natively supported.
I’m trying to set up a web hook and I need to point the payload to a local file.
The file inside the Docker container is located at:
/var/www/discourse/plugins/distodis/docroot/
To what address does this translate to as URL?
I’ve pretty much tried everything I can think of and I’m getting 404 from all my pings.
Any ideas?
A file that lives in
/var/www/discourse/plugins/plugin-name/public/folder/a.txt
will be in the URL at
https://discourse.example.com/plugins/plugin-name/folder/a.txt
What does PHP have to do with Discourse?
Nothing directly, but this plugin is using PHP:
https://github.com/ellotheth/distodis
But now that I think about it … it might require an external web server, because Discourse doesn’t come with PHP support in nginx, right? 
That’s definitely not a Discourse plugin.
Posting from Discourse to Discord in natively supported in this plugin:
What? How so?
I found it here:
It’s in the Customization > Extras category…
A directory of all extensions & integrations for Discourse which are not Discourse plugins, i.e. a CMS plugin, a browser extension or a native application.
Hey, thanks a lot. I didn’t see that when I was searching for Discourse/Discord integration plugins. I’m gonna try that out!
Oh, ok. I should have read that more carefully. I just kind of assumed that it’s for plugins which are not official. 
