-
issue is coming from the binding if not resolved.
For instance, `[idontexist.ipv4]` won't be resolved and the string is kept as is.
As all nodes then subscribe to the same private room, they are t…
-
When trying to access the `request.context` from a plugin context, a core_dump is triggered.
-
We need a view to enable the user to manage the plugins server-side. Including
- adding a new plugin
- showing currently installed plugins
- enabling/disabling an installed plugin
- removing an instal…
-
We should mention that plugins may throw exceptions during their initialization phase to signal, for instance, an invalid configuration. And that Kuzzle handles this case by logging an error and pursu…
-
Hi,
As I discussed with @benoitvidis today, when writing controller plugin, if you make a configuration or typing mistake you're redirected to the read controller when using REST protocol (GET).
**E…
-
As seen with @AnthonySendra , the timeout in Kuzzle is not really a timeout since requests are still being processed
Basically, setup a plugin Controller that do a setTimeout for 15 seconds and co…
ghost updated
6 years ago
-
Plugin name will be read from the mandatory `package.json` file. A unicity constraint must be enforced on plugins (only one plugin with a given name can be installed on a Kuzzle instance).
-
the documentation says:
```
context.accessors.execute(request, (error, request) => {
/*
Kuzzle's response can be obtained with request.response
See Request constructor documentation for m…
-
Following https://github.com/kuzzleio/kuzzle/pull/833, worker plugins will receive a SIGINT system call on shutdown.
Plugins that can use this interruption to cleanly exit. In the logger case, I/O bo…
-
This section should have its own documentation, separated from the Kuzzle plugins one, for the following reasons:
* its plugin context is different from the one received by other plugins
* protoco…