Re: Does the apisix v0.9 support cluster limit-conn and limit-req using redis

by the way, all the limit-* plugins in Apache APISIX are based on leaky buckets, and plugins based on token buckets are welcome. Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Ming Wen 于2019年11月27日周三 下午9:48写道： > Hi, Lang, > Not yet. Both of them are in the TODO list, welcome PR. > > Thanks

Re: [DISCUSS] archive or delete dashborad-built repository

To avoid confusion it might be better to delete it. On Wed, Nov 27, 2019 at 8:24 PM junxu chen wrote: > I should prefer to delete the repo rather than archiving it. > > Because we could build dashboard from source. And archiving repo may cause > compatibility issues . > > On Wed, Nov 27, 2019 a

Re: [DISCUSS] parpare for Apache release of apisix-dashboard

how about we set a install option with or without dashboard?? -- Original -- From: YuanSheng Wang https://www.shaoyaoju.org/>; > > > Ming Wen https://github.com/apache/incubator-apisix-dashboard/pull/73 > > > > Thanks, > > Ming Wen, Apache APISIX > > Twitter: _Wen

Re: [DISCUSS] parpare for Apache release of apisix-dashboard

+1 release the dashboard separately It's easier. On Wed, Nov 27, 2019 at 10:05 PM Zhiyuan Ju wrote: > I would prefer to release the dashboard in separate, and I would love to be > the release manager this time. > > Best Regards! > @ Zhiyuan Ju > > > Ming Wen 于2019

Re: [DISCUSS] parpare for Apache release of apisix-dashboard

I would prefer to release the dashboard in separate, and I would love to be the release manager this time. Best Regards! @ Zhiyuan Ju Ming Wen 于2019年11月27日周三 下午6:00写道： > yes, Zhiyuan Ju already added license headers for all files[1], > and checked the NOTICE and LI

Re: Does the apisix v0.9 support cluster limit-conn and limit-req using redis

Hi, Lang, Not yet. Both of them are in the TODO list, welcome PR. Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Lang Wang 于2019年11月27日周三 下午7:27写道： > Hi comunity, > > I know the current v0.9 support cluster limit-count by using redis/redis > cluster. Does the current release apisix v0.9 sup

Re: [DISCUSS] archive or delete dashborad-built repository

I should prefer to delete the repo rather than archiving it. Because we could build dashboard from source. And archiving repo may cause compatibility issues . On Wed, Nov 27, 2019 at 8:07 PM Linsir Wu wrote: > I would prefer archiving it too. > > Ming Wen 于2019年11月26日周二 下午3:56写道： > > > hello,

Re: [DISCUSS] archive or delete dashborad-built repository

I would prefer archiving it too. Ming Wen 于2019年11月26日周二 下午3:56写道： > hello, community > > The dashborad-built repository[1] stores the compiled code. They cannot be > handled well about licenses, so they are not included in the release > version of Apache APISIX. > > So, does this repo no longer

Does the apisix v0.9 support cluster limit-conn and limit-req using redis

Hi comunity, I know the current v0.9 support cluster limit-count by using redis/redis cluster. Does the current release apisix v0.9 support cluster limit-conn and limit-req using redis?

Re: [DISCUSS] parpare for Apache release of apisix-dashboard

yes, Zhiyuan Ju already added license headers for all files[1], and checked the NOTICE and LICENSE files. [1] https://github.com/apache/incubator-apisix-dashboard/pull/73 Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Willem Jiang 于2019年11月27日周三 下午5:53写道： > +1 to release the dashboard firs

Re: [DISCUSS] parpare for Apache release of apisix-dashboard

+1 to release the dashboard first. My question is do we have a clear license dependency analyze of dashboard already? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Nov 27, 2019 at 5:35 PM Ming Wen wrote: > > hello, community, > I think it's time to prepare the Apache release of dash

[DISCUSS] parpare for Apache release of apisix-dashboard

hello, community, I think it's time to prepare the Apache release of dashboard[1]. Here are two options, let's discuss which one is more suitable: 1. Prepare dashboard release separately 2. Released with APISIX 1.0 IMO, I recommend using the first one, which is faster and less risky. In addition