Yeah, that’s right.
First, I’m installing Kong with rpm.
sudo yum install kong-community-edition-1.0.0.*.noarch.rpm --nogpgcheck
And then install a Kong plugin by luarocks.
luarocks install <rock-filename>
The rock-file is generated by pack it:
luarocks pack <plugin-name> <version>
Util now, everything goes fine, plugin install success.
And then modify the conf in /etc/conf/kong.conf (this file is copied from the kong.conf.default)
plugins = bundled, XXXX-custom-plugin
Save that conf and use this:
After that the XXXX-custom-plugin will nerver show in the plugins. (I’m using a third-party admin-gui Admin-gui).
Even I grep the url will get nothing:
curl http://localhost:8001 | grep XXXX-custom-plugin
That’s imply the XXXX-custom-plugin is not taking effect, right?
But, XXXX-custom-plugin take effect after I use this command:
But this command will cause kong stop(which I’m not expecting).
Is there any solution to avoid that?