Replies: 3 comments
-
As they are in a docker container I would assume it is some misconfiguration on the docker (or nginx) side of things as opposed to something wrong with this plugin. The configuration from the plugins standpoint looks fine to me. Is it possible to provide the docker and nginx configurations you are using? |
Beta Was this translation helpful? Give feedback.
-
I got rid of the errors via "properly" setting the socket.serverOptions.cors.origin
In my React Frontend I'm trying to catch updates of my Strapi Player Table like so, which doesn't work sadly :/
When I try to explicitly emit an event from my strapi controller like so: my Strapi build crashes, as it doesn't know $io
I'm using Typescript Version on of Strapi, and maybe the plugin doesn't register this type properly... |
Beta Was this translation helpful? Give feedback.
-
This plugin is built in js and therefore does not have any types. Ideally an index.d.ts would exists to prevent this but I have not done that yet. In the meantime I believe something along the lines of // ./index.d.ts
declare module "@strapi/strapi" {
interface Strapi {
$io: any;
}
} at the root of the project should resolve this typing issue for now. |
Beta Was this translation helpful? Give feedback.
-
What issue are you experiencing?
I'm running strapi and my frontend in a docker container.
I'm using nginx as reverse proxy.
Strapi url: http://localhost/strapi
frontend url: http:/localhost/frontend
in my client I just setup my socket like:
strapi/config/plugins.ts:
Steps To Reproduce
No response
What version of the plugin are you using?
2.0.4
What strapi version are you using?
4.15.5
Beta Was this translation helpful? Give feedback.
All reactions