> In fact, the split will make the situation more complex.
> Now we require the `package.json` stuff and need to handle complex
> dependency cases (like the apisix-base I mentioned in that issue).
> These problems are not existent if we don't split the plugin.
> We have to develop a custom new pack
El mar., 15 de marzo de 2022 12:52 a. m., Fei Liang
escribió:
> > 1. Term Compile is too generic, could you give us some examples about
> this process;
>
> eg. in */rockspec/apisix-master-0.rockspec*, it has dependencies "lualdap
> = 1.2.6-1".
> in fact, only plugin ldap-auth.lua (/apisix/plugi
> if we want have the marketplace, the version dependency is necessary.
No thanks. The marketplace is not even in the 2022 roadmap.
> if the plugin is independent. the user can write their own plugins, and
install it by apisix-dashboard or other method for dynamic installing.
Currently, we alrea
>> if we want have the marketplace, the version dependency is necessary.
> No thanks. The marketplace is not even in the 2022 roadmap.
yeah, so I couldn't mean split it to the dependent repo. I only mean split.
>> if the plugin is independent. the user can write their own plugins, and
>>install i
> now, the only enable plugin method, is changing the APISIX source.
and if use the dashboard to enable plugin, by the document
https://apisix.apache.org/docs/dashboard/FAQ
This is incorrect. We have maintained many Enterprise edition plugins
without modifying APISIX to load it.
Enabling a new pl
Hi community,
I am Jing Li, from the Apache APISIX community.
We are going to hold Apache APISIX Summit Asia 2022 in May. In order to
achieve good publicity effect, we want to invite SkyWalking community as a
cooperative community, so we want to apply for* the use of SkyWalking logo*.
Please let
