You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/03/07 06:56:53 UTC
[GitHub] [apisix-website] moonming opened a new pull request #945: docs: Optimize text descriptions and keywords.
moonming opened a new pull request #945:
URL: https://github.com/apache/apisix-website/pull/945
Fixes: #[Add issue number here]
Changes:
<!-- Add here what changes were made in this pull request and if possible provide links showcasing the changes. -->
Screenshots of the change:
<!-- Add screenshots depicting the changes. -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
👷 Deploy Preview for *apache-apisix* processing.
🔨 Explore the source changes: 15e4857387093ee516c63802a9e982e19ca2a864
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/6228002aacaff40008021720](https://app.netlify.com/sites/apache-apisix/deploys/6228002aacaff40008021720)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
✔️ Deploy Preview for *apache-apisix* ready!
🔨 Explore the source changes: 30e547e29f789553fda9d75b812696fc4b7e6a36
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/6226f004a4f46500089ed05d](https://app.netlify.com/sites/apache-apisix/deploys/6226f004a4f46500089ed05d)
😎 Browse the preview: [https://deploy-preview-945--apache-apisix.netlify.app](https://deploy-preview-945--apache-apisix.netlify.app)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] moonming commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
moonming commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1062655984
> > > Batching all of these procedures (rename, update keywords, descriptions, add text contents) up in one pull request is not a wise decision. It creates the following problems.
> > >
> > > 1. Once a file is renamed, its contents appear as all new during review. This creates trouble for reviewers. Put yourself in reviewers' shoes, how would you feel when you need to review a pull request with 215 files (the number of files in this pull request as of 17:36 GMT+8)?
> > > 2. Many of the files are ended with time stamp `2022xxxxx` suffixes. Please fix them.
> > > 
> > > 3. Some of the files are already published on Medium[1] page, which also provides link referring back to Apache APISIX's blog[2]. Do you know changing all links could lead to reference failures as well?
> > >
> > > I would suggest break this pull request into different parts and solve them one by one.
> > >
> > > 1. Identify all files that can't be renamed directly for Reason 3 stated above. It can be solved with a trick called `slug`. Update keywords, update descriptions, add text contents on them. This could be a pull request.
> > > 2. Update keywords, update descriptions, add text contents for the rest of the files. This could be one or more pull requests, preferably submitting them by months or quarters.
> > > 3. Rename files in Part 2. The reason to leave the renaming at the end are to ease the process of review and to avoid merge conflicts. Please think of other contributors and other pull requests hanging there as well. This could be another pull request.
> > >
> > > I know you are eager to solve this problem soon. But using brutal force to solve the problem just isn't the most effective way. Things are always more complicated than your imagination. Please think twice before you act.
> > > Please fix the lint as well, thanks!
> > > [1]https://medium.com/@ApacheAPISIX [2]https://apisix.apache.org/blog
> >
> >
> > 1 and 2 are both fixed. and 3 is not the issue of apisix website, and we can update the links in Medium after this PR merged.
>
> There are another 15 problems listed below. The cause is only renaming en-us blogs' names but not zh-cn blogs' names, or the other way around. Please fix them.
>
> 1. When renaming or adding `slug` to files, please make sure en-us blogs' names and `slug`(if any) are matched up with those of zh-cn blogs'.
> 2. The existing `-API-` in filenames is not acceptable, it will create problems of case sensitive URLs again. Please modify them to `-api-`.
>
> Here is the list of 15 problems.
>
> 1. OPA
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/12/24/open-policy-agent-API-gateway
> 2. website/blog/2021/12/22/google-logging-API-gateway.md
> 2. Google Cloud Logging
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/12/22/google-logging-API-gateway
> 2. website/blog/2021/12/22/google-logging-API-gateway.md
> 3. Datadog
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/12/datadog-API-gateway
> 2. website/blog/2021/11/12/datadog-API-gateway.md
> 4. Observability of API gateway
>
> 1. website/blog/2021/11/04/observability-of-api-gateway.md
> 2. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/04/observability-of-api-gateway/
> 5. Airwallex
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/03/airwallex-api-gateway/
> 2. website/blog/2021/11/03/airwallex-API-gateway.md
> 6. WPS
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/28/wps-usercase
> 2. website/blog/2021/09/28/WPS-API-gateway.md
> 7. UPYUN
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/24/upyun-API-gateway
> 2. website/blog/2021/09/24/upyun-API-gateway.md
> 8. DIAN
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/18/xiaodian-API-gateway
> 2. website/blog/2021/09/18/xiaodian-API-gateway.md
> 9. Tencent Cloud
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/16/tencent-cloud-API-gateway
> 2. website/blog/2021/09/16/tencent-cloud-API-gateway.md
> 10. Youzanyun
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/14/youzan-mocroservice-API-gateway
> 2. website/blog/2021/09/14/youzan-mocroservice-API-gateway.md
> 11. China Mobile Cloud
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/13/china-mobile-cloud-api-gateway
> 2. website/blog/2021/09/13/china-mobile-cloud-api-gateway.md
> 12. iQiYi
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/07/iqiyi-api-gateway
> 2. website/blog/2021/09/07/iQIYI-API-gateway.md
> 13. Airwallex Interview
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/17/airwallex-apache-apisix
> 2. website/blog/2021/08/17/airwallex-apache-apisix.md
> 14. Apache APISIX Architecture Analysis
>
> 1. [https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/10/dynamically-manage-Nginx-clustering](https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/16/using-the-apache-apisix-openid-connect-plugin-for-centralized-authentication)
> 2. website/blog/2021/08/10/dynamically-manage-Nginx-clustering.md
> 15. Hyperchain
>
> 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/09/apache-apisix-in-hyperchain
> 2. website/blog/2021/08/09/Apache-APISIX-in-Hyperchain.md
>
> Once fixed, please examine in https://deploy-preview-945--apache-apisix.netlify.app/ carefully. Or it takes other reviewers' time to do it for you, which would very likely to slow down the review, approve, and merging process.
all fixed, please take a look
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r821244205
##########
File path: website/blog/2022/01/21/apisix-hashicorp-vault-integration.md
##########
@@ -25,6 +25,10 @@ tags: [Technology,Authentication]
With the rise of microservice-based architecture, keeping things secure has become much more challenging than earlier. We are far beyond the point where our 100 instances of backend servers are accessing our database server with a single static secret credential because if in case of a credential leakage the whole system is compromised and revocation of that credential causes a massive service outage (now no one can access anything unless the instances are reconfigured). We can't eliminate the possibility of a security breach because sometimes unexpected does happen. Instead, it's totally up to us to control the blast radius in these situations. To tackle scenarios like this, a popular solution like [HashiCorp Vault](https://www.vaultproject.io/) comes into the picture in a production environment to act as an identity-based secrets and encryption management system. In this article, I have demonstrated how to integrate Vault with Apache APISIX (a cloud-native API Gateway) [jwt-auth p
lugin](https://apisix.apache.org/docs/apisix/plugins/jwt-auth) to effectively use excellence from both worlds.
+
+### About Apache APISIX
+
+[Apache APISIX](https://github.com/apache/apisix) is a dynamic, real-time, high-performance API gateway that provides rich traffic management features such as load balancing, dynamic upstream, canary release, service meltdown, authentication, observability, etc. Apache APISIX not only supports dynamic plug-in changes and hot-plugging, but also has a number of useful plug-ins.OpenID Connect Plug-in for Apache APISIX With support for the OpenID Connect protocol, users can use this plug-in to enable Apache APISIX to interface with Authing services and be deployed as a centralized authentication gateway in the enterprise.
Review comment:
```suggestion
### About Apache APISIX
[Apache APISIX](https://github.com/apache/apisix) is a dynamic, real-time, high-performance API gateway that provides rich traffic management features such as load balancing, dynamic upstream, canary release, service meltdown, authentication, observability, etc. Apache APISIX not only supports dynamic plug-in changes and hot-plugging, but also has a number of useful plug-ins.OpenID Connect Plug-in for Apache APISIX With support for the OpenID Connect protocol, users can use this plug-in to enable Apache APISIX to interface with Authing services and be deployed as a centralized authentication gateway in the enterprise.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r821242997
##########
File path: website/i18n/zh/docusaurus-plugin-content-blog/2022/01/21/apisix-hashicorp-vault-integration.md
##########
@@ -9,12 +9,12 @@ authors:
title: "Technical Writer"
url: "https://github.com/yzeng25"
image_url: "https://avatars.githubusercontent.com/u/36651058?v=4"
-keywords:
+keywords:
- Apache APISIX
- HashiCorp
- Vault
-- jwt-auth
-- 认证
+- API网关
Review comment:
```suggestion
- API 网关
```
##########
File path: website/i18n/zh/docusaurus-plugin-content-blog/2022/01/21/apisix-xrpc-details-and-miltilingual.md
##########
@@ -9,12 +9,9 @@ authors:
title: "Technical Writer"
url: "https://github.com/SylviaBABY"
image_url: "https://avatars.githubusercontent.com/u/39793568?v=4"
-keywords:
-- 多协议
+keywords:
+- API网关
Review comment:
```suggestion
- API 网关
```
##########
File path: website/i18n/zh/docusaurus-plugin-content-blog/2022/01/25/apisix-grpc-web-integration.md
##########
@@ -9,11 +9,11 @@ authors:
title: "Technical Writer"
url: "https://github.com/yzeng25"
image_url: "https://avatars.githubusercontent.com/u/36651058?v=4"
-keywords:
+keywords:
- Apache APISIX
- gRPC
-- gRPC-Web
-- Ecology
+- API网关
Review comment:
```suggestion
- API 网关
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r821241942
##########
File path: website/blog/2021/08/31/Apache APISIX × KubeSphere-a-better-gateway-and-K8S-Ingress-Controller.md
##########
@@ -1,5 +1,5 @@
---
-title: "Apache APISIX × KubeSphere: Providing a better gateway and K8S Ingress Controller"
+title: "Apache APISIX × KubeSphere: Providing a better API gateway and K8S Ingress Controller"
Review comment:
```suggestion
title: "Apache APISIX × KubeSphere: Providing a better API Gateway and K8s Ingress Controller"
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] moonming commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
moonming commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1061271508
@SylviaBABY @juzhiyuan I removed all history files. please check again
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] yzeng25 commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
yzeng25 commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1063850043
> > > > Batching all of these procedures (rename, update keywords, descriptions, add text contents) up in one pull request is not a wise decision. It creates the following problems.
> > > >
> > > > 1. Once a file is renamed, its contents appear as all new during review. This creates trouble for reviewers. Put yourself in reviewers' shoes, how would you feel when you need to review a pull request with 215 files (the number of files in this pull request as of 17:36 GMT+8)?
> > > > 2. Many of the files are ended with time stamp `2022xxxxx` suffixes. Please fix them.
> > > > 
> > > > 3. Some of the files are already published on Medium[1] page, which also provides link referring back to Apache APISIX's blog[2]. Do you know changing all links could lead to reference failures as well?
> > > >
> > > > I would suggest break this pull request into different parts and solve them one by one.
> > > >
> > > > 1. Identify all files that can't be renamed directly for Reason 3 stated above. It can be solved with a trick called `slug`. Update keywords, update descriptions, add text contents on them. This could be a pull request.
> > > > 2. Update keywords, update descriptions, add text contents for the rest of the files. This could be one or more pull requests, preferably submitting them by months or quarters.
> > > > 3. Rename files in Part 2. The reason to leave the renaming at the end are to ease the process of review and to avoid merge conflicts. Please think of other contributors and other pull requests hanging there as well. This could be another pull request.
> > > >
> > > > I know you are eager to solve this problem soon. But using brutal force to solve the problem just isn't the most effective way. Things are always more complicated than your imagination. Please think twice before you act.
> > > > Please fix the lint as well, thanks!
> > > > [1]https://medium.com/@ApacheAPISIX [2]https://apisix.apache.org/blog
> > >
> > >
> > > 1 and 2 are both fixed. and 3 is not the issue of apisix website, and we can update the links in Medium after this PR merged.
> >
> >
> > There are another 15 problems listed below. The cause is only renaming en-us blogs' names but not zh-cn blogs' names, or the other way around. Please fix them.
> >
> > 1. When renaming or adding `slug` to files, please make sure en-us blogs' names and `slug`(if any) are matched up with those of zh-cn blogs'.
> > 2. The existing `-API-` in filenames is not acceptable, it will create problems of case sensitive URLs again. Please modify them to `-api-`.
> >
> > Here is the list of 15 problems.
> >
> > 1. OPA
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/12/24/open-policy-agent-API-gateway
> > 2. website/blog/2021/12/22/google-logging-API-gateway.md
> > 2. Google Cloud Logging
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/12/22/google-logging-API-gateway
> > 2. website/blog/2021/12/22/google-logging-API-gateway.md
> > 3. Datadog
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/12/datadog-API-gateway
> > 2. website/blog/2021/11/12/datadog-API-gateway.md
> > 4. Observability of API gateway
> >
> > 1. website/blog/2021/11/04/observability-of-api-gateway.md
> > 2. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/04/observability-of-api-gateway/
> > 5. Airwallex
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/03/airwallex-api-gateway/
> > 2. website/blog/2021/11/03/airwallex-API-gateway.md
> > 6. WPS
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/28/wps-usercase
> > 2. website/blog/2021/09/28/WPS-API-gateway.md
> > 7. UPYUN
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/24/upyun-API-gateway
> > 2. website/blog/2021/09/24/upyun-API-gateway.md
> > 8. DIAN
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/18/xiaodian-API-gateway
> > 2. website/blog/2021/09/18/xiaodian-API-gateway.md
> > 9. Tencent Cloud
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/16/tencent-cloud-API-gateway
> > 2. website/blog/2021/09/16/tencent-cloud-API-gateway.md
> > 10. Youzanyun
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/14/youzan-mocroservice-API-gateway
> > 2. website/blog/2021/09/14/youzan-mocroservice-API-gateway.md
> > 11. China Mobile Cloud
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/13/china-mobile-cloud-api-gateway
> > 2. website/blog/2021/09/13/china-mobile-cloud-api-gateway.md
> > 12. iQiYi
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/07/iqiyi-api-gateway
> > 2. website/blog/2021/09/07/iQIYI-API-gateway.md
> > 13. Airwallex Interview
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/17/airwallex-apache-apisix
> > 2. website/blog/2021/08/17/airwallex-apache-apisix.md
> > 14. Apache APISIX Architecture Analysis
> >
> > 1. [https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/10/dynamically-manage-Nginx-clustering](https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/16/using-the-apache-apisix-openid-connect-plugin-for-centralized-authentication)
> > 2. website/blog/2021/08/10/dynamically-manage-Nginx-clustering.md
> > 15. Hyperchain
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/09/apache-apisix-in-hyperchain
> > 2. website/blog/2021/08/09/Apache-APISIX-in-Hyperchain.md
> >
> > Once fixed, please examine in https://deploy-preview-945--apache-apisix.netlify.app/ carefully. Or it takes other reviewers' time to do it for you, which would very likely to slow down the review, approve, and merging process.
>
> all fixed, please take a look
So I went through the first 2 and last 3, they are not fixed yet.
For these files, please update the Chinese blogs' filenames as well.
Take the first one, OPA, for example, you will need to update the Chinese blog’s file name to `open-policy-agent-API-gateway.md`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r821266333
##########
File path: website/i18n/zh/docusaurus-plugin-content-blog/2022/01/17/apisix-kafka-integration.md
##########
@@ -9,12 +9,11 @@ authors:
title: "Technical Writer"
url: "https://github.com/SylviaBABY"
image_url: "https://avatars.githubusercontent.com/u/39793568?v=4"
-keywords:
+keywords:
- Apache APISIX
- Apache Kafka
-- Kafka
-- 日志
-- 监控
+- API网关
Review comment:
```suggestion
- API 网关
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
✔️ Deploy Preview for *apache-apisix* canceled.
🔨 Explore the source changes: 08c1debb7d5d4aa6f081e357c67c3a21c7dcb8c4
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/62269ee82c1546000777069e](https://app.netlify.com/sites/apache-apisix/deploys/62269ee82c1546000777069e)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SkyeYoung commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SkyeYoung commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1065906097
> Apache APISIX Website is hosted on the ASF's Infra, by Apache Web Server. We could build 301 rules but the ASF Infra may not accept it easily (bcoz I tried to enable HTTPS by default but got rejected 😅).
Got it.
But I think plugin-client-redirect should work, I will try to fix the problem of it. Maybe one day.😜
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
✔️ Deploy Preview for *apache-apisix* ready!
🔨 Explore the source changes: 73d58e1e51cb6d3d339db5f244714eb7975f590a
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/6225aca68648a2000725741c](https://app.netlify.com/sites/apache-apisix/deploys/6225aca68648a2000725741c)
😎 Browse the preview: [https://deploy-preview-945--apache-apisix.netlify.app](https://deploy-preview-945--apache-apisix.netlify.app)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
✔️ Deploy Preview for *apache-apisix* canceled.
🔨 Explore the source changes: 63a3c81a397b634180c93d4fa763adbdd358263e
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/62269f417aef6000071fb3a1](https://app.netlify.com/sites/apache-apisix/deploys/62269f417aef6000071fb3a1)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] moonming commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
moonming commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1064929343
>
it will not affect SEO if not change slugs, right?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] moonming commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
moonming commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1064928972
> 3\. `slug`s
it will not affect SEO if not change `slugs`, right?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
👷 Deploy Preview for *apache-apisix* processing.
🔨 Explore the source changes: 73d58e1e51cb6d3d339db5f244714eb7975f590a
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/6225aca68648a2000725741c](https://app.netlify.com/sites/apache-apisix/deploys/6225aca68648a2000725741c)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] moonming commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
moonming commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1061272364
> Batching all of these procedures (rename, update keywords, descriptions, add text contents) up in one pull request is not a wise decision. It creates the following problems.
>
> 1. Once a file is renamed, its contents appear as all new during review. This creates trouble for reviewers. Put yourself in reviewers' shoes, how would you feel when you need to review a pull request with 215 files (the number of files in this pull request as of 17:36 GMT+8)?
> 2. Many of the files are ended with time stamp `2022xxxxx` suffixes. Please fix them.
> 
> 3. Some of the files are already published on Medium[1] page, which also provides link referring back to Apache APISIX's blog[2]. Do you know changing all links could lead to reference failures as well?
>
> I would suggest break this pull request into different parts and solve them one by one.
>
> 1. Identify all files that can't be renamed directly for Reason 3 stated above. It can be solved with a trick called `slug`. Update keywords, update descriptions, add text contents on them. This could be a pull request.
> 2. Update keywords, update descriptions, add text contents for the rest of the files. This could be one or more pull requests, preferably submitting them by months or quarters.
> 3. Rename files in Part 2. The reason to leave the renaming at the end are to ease the process of review and to avoid merge conflicts. Please think of other contributors and other pull requests hanging there as well. This could be another pull request.
>
> I know you are eager to solve this problem soon. But using brutal force to solve the problem just isn't the most effective way. Things are always more complicated than your imagination. Please think twice before you act.
>
> Please fix the lint as well, thanks!
>
> [1]https://medium.com/@ApacheAPISIX [2]https://apisix.apache.org/blog
1 and 2 are both fixed. and 3 is not the issue of apisix website, and we can update the links in Medium after this PR merged.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] juzhiyuan commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1061462829
Hi, @moonming, there exist some conflicts that must be resolved locally.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r821266190
##########
File path: website/i18n/zh/docusaurus-plugin-content-blog/2022/01/13/how-to-proxy-dubbo-in-apache-apisix.md
##########
@@ -9,10 +9,10 @@ authors:
title: "Technical Writer"
url: "https://github.com/SylviaBABY"
image_url: "https://avatars.githubusercontent.com/u/39793568?v=4"
-keywords:
+keywords:
- Apache APISIX
- Apache Dubbo
-- 代理操作
+- API网关
Review comment:
```suggestion
- API 网关
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] moonming commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
moonming commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1062457445
> Hi, @moonming, there exist some conflicts that must be resolved locally.
>
> 
all conflicts resolved
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SkyeYoung commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SkyeYoung commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r824434126
##########
File path: website/blog/2021/06/21/use-Java-to-write-Apache-APISIX-plugins.md
##########
@@ -1,11 +1,11 @@
---
-title: "How to Write an Apache APISIX Plugin in Java"
-slug: 2021/06/21/use-java-to-write-apache-apisix-plugins
+title: "How to use Java to write plugins for API Gateway?"
+slug: 2021/06/21/how-to-use-java-to-write-plugins-for-api-gateway
Review comment:
> the article's original URL will be 404.
Can we use https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-client-redirects/ ？
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] yzeng25 commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
yzeng25 commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060413894
Batching all of these procedures (rename, update keywords, descriptions, add text contents) up in one pull request is not a wise decision. It creates the following problems.
1. Once a file is renamed, its contents appear as all new during review. This creates trouble for reviewers. Put yourself in reviewers' shoes, how would you feel when you need to review a pull request with 215 files (the number of files in this pull request as of 17:36 GMT+8)?
2. Many of the files are ended with time stamp `2022xxxxx` suffixes. Please fix them.
3. Some of the files are already published on Medium[1] page, which also provides link referring back to Apache APISIX's blog[2]. Do you know changing all links could lead to reference failures as well?
I would suggest break this pull request into different parts and solve them one by one.
1. Identify all files that can't be renamed directly for Reason 3 stated above. It can be solved with a trick called `slug`. Update keywords, update descriptions, add text contents on them. This could be a pull request.
2. Update keywords, update descriptions, add text contents for the rest of the files. This could be one or more pull requests, preferably submitting them by months or quarters.
3. Rename files in Part 2. The reason to leave the renaming at the end are to ease the process of review and to avoid merge conflicts. Please think of other contributors and other pull requests hanging there as well. This could be another pull request.
I know you are eager to solve this problem soon. But using brutal force to solve the problem just isn't the most effective way. Things are always more complicated than your imagination. Please think twice before you act.
Please fix the lint as well, thanks!
[1]https://medium.com/@ApacheAPISIX
[2]https://apisix.apache.org/blog
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060366893
@moonming I think this PR can be turned off temporarily, or you can take two or three old articles to revise and demonstrate. Because there are too many documents involved in this PR, it will affect the subsequent modification of updating user case English picture and lead to the emergence of PR conflict.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
👷 Deploy Preview for *apache-apisix* processing.
🔨 Explore the source changes: 63a3c81a397b634180c93d4fa763adbdd358263e
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/62269f417aef6000071fb3a1](https://app.netlify.com/sites/apache-apisix/deploys/62269f417aef6000071fb3a1)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] moonming commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
moonming commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r822380045
##########
File path: website/blog/2021/05/24/Tencent-Games.md
##########
@@ -1,13 +1,12 @@
---
title: "How to use API Gateway to process 1 billion traffic daily for Tencent?"
-slug: 2021/05/24/tencent-games
+slug: 2021/05/24/how-tencent-game-use-API-geteway
Review comment:
all fixed
##########
File path: .gitignore
##########
@@ -31,3 +31,5 @@ tmp/*
.netlify
scripts/yarn.lock
+
+.history
Review comment:
I just ignored all history in Git.
##########
File path: website/blog/2021/06/21/use-Java-to-write-Apache-APISIX-plugins.md
##########
@@ -1,11 +1,11 @@
---
-title: "How to Write an Apache APISIX Plugin in Java"
-slug: 2021/06/21/use-java-to-write-apache-apisix-plugins
+title: "How to use Java to write plugins for API Gateway?"
+slug: 2021/06/21/how-to-use-java-to-write-plugins-for-api-gateway
Review comment:
Got it. But we need a better uri.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
👷 Deploy Preview for *apache-apisix* processing.
🔨 Explore the source changes: 245f16ce6e72c2ed67922acdd3b7d9793cfde258
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/62285fcfb523660008a1e448](https://app.netlify.com/sites/apache-apisix/deploys/62285fcfb523660008a1e448)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
✔️ Deploy Preview for *apache-apisix* ready!
🔨 Explore the source changes: 15e4857387093ee516c63802a9e982e19ca2a864
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/6228002aacaff40008021720](https://app.netlify.com/sites/apache-apisix/deploys/6228002aacaff40008021720)
😎 Browse the preview: [https://deploy-preview-945--apache-apisix.netlify.app](https://deploy-preview-945--apache-apisix.netlify.app)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r821266466
##########
File path: website/i18n/zh/docusaurus-plugin-content-blog/2022/01/04/authing-API-gateway.md
##########
@@ -9,12 +9,12 @@ authors:
title: "Technical Writer"
url: "https://github.com/yzeng25"
image_url: "https://avatars.githubusercontent.com/u/36651058?v=4"
-keywords:
+keywords:
- Apache APISIX
- Authing
- OpenID
- Authentication
-- 插件
+- API网关
Review comment:
```suggestion
- API 网关
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] yzeng25 edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
yzeng25 edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1063850043
> > > > Batching all of these procedures (rename, update keywords, descriptions, add text contents) up in one pull request is not a wise decision. It creates the following problems.
> > > >
> > > > 1. Once a file is renamed, its contents appear as all new during review. This creates trouble for reviewers. Put yourself in reviewers' shoes, how would you feel when you need to review a pull request with 215 files (the number of files in this pull request as of 17:36 GMT+8)?
> > > > 2. Many of the files are ended with time stamp `2022xxxxx` suffixes. Please fix them.
> > > > 
> > > > 3. Some of the files are already published on Medium[1] page, which also provides link referring back to Apache APISIX's blog[2]. Do you know changing all links could lead to reference failures as well?
> > > >
> > > > I would suggest break this pull request into different parts and solve them one by one.
> > > >
> > > > 1. Identify all files that can't be renamed directly for Reason 3 stated above. It can be solved with a trick called `slug`. Update keywords, update descriptions, add text contents on them. This could be a pull request.
> > > > 2. Update keywords, update descriptions, add text contents for the rest of the files. This could be one or more pull requests, preferably submitting them by months or quarters.
> > > > 3. Rename files in Part 2. The reason to leave the renaming at the end are to ease the process of review and to avoid merge conflicts. Please think of other contributors and other pull requests hanging there as well. This could be another pull request.
> > > >
> > > > I know you are eager to solve this problem soon. But using brutal force to solve the problem just isn't the most effective way. Things are always more complicated than your imagination. Please think twice before you act.
> > > > Please fix the lint as well, thanks!
> > > > [1]https://medium.com/@ApacheAPISIX [2]https://apisix.apache.org/blog
> > >
> > >
> > > 1 and 2 are both fixed. and 3 is not the issue of apisix website, and we can update the links in Medium after this PR merged.
> >
> >
> > There are another 15 problems listed below. The cause is only renaming en-us blogs' names but not zh-cn blogs' names, or the other way around. Please fix them.
> >
> > 1. When renaming or adding `slug` to files, please make sure en-us blogs' names and `slug`(if any) are matched up with those of zh-cn blogs'.
> > 2. The existing `-API-` in filenames is not acceptable, it will create problems of case sensitive URLs again. Please modify them to `-api-`.
> >
> > Here is the list of 15 problems.
> >
> > 1. OPA
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/12/24/open-policy-agent-API-gateway
> > 2. website/blog/2021/12/22/google-logging-API-gateway.md
> > 2. Google Cloud Logging
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/12/22/google-logging-API-gateway
> > 2. website/blog/2021/12/22/google-logging-API-gateway.md
> > 3. Datadog
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/12/datadog-API-gateway
> > 2. website/blog/2021/11/12/datadog-API-gateway.md
> > 4. Observability of API gateway
> >
> > 1. website/blog/2021/11/04/observability-of-api-gateway.md
> > 2. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/04/observability-of-api-gateway/
> > 5. Airwallex
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/03/airwallex-api-gateway/
> > 2. website/blog/2021/11/03/airwallex-API-gateway.md
> > 6. WPS
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/28/wps-usercase
> > 2. website/blog/2021/09/28/WPS-API-gateway.md
> > 7. UPYUN
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/24/upyun-API-gateway
> > 2. website/blog/2021/09/24/upyun-API-gateway.md
> > 8. DIAN
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/18/xiaodian-API-gateway
> > 2. website/blog/2021/09/18/xiaodian-API-gateway.md
> > 9. Tencent Cloud
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/16/tencent-cloud-API-gateway
> > 2. website/blog/2021/09/16/tencent-cloud-API-gateway.md
> > 10. Youzanyun
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/14/youzan-mocroservice-API-gateway
> > 2. website/blog/2021/09/14/youzan-mocroservice-API-gateway.md
> > 11. China Mobile Cloud
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/13/china-mobile-cloud-api-gateway
> > 2. website/blog/2021/09/13/china-mobile-cloud-api-gateway.md
> > 12. iQiYi
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/07/iqiyi-api-gateway
> > 2. website/blog/2021/09/07/iQIYI-API-gateway.md
> > 13. Airwallex Interview
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/17/airwallex-apache-apisix
> > 2. website/blog/2021/08/17/airwallex-apache-apisix.md
> > 14. Apache APISIX Architecture Analysis
> >
> > 1. [https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/10/dynamically-manage-Nginx-clustering](https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/16/using-the-apache-apisix-openid-connect-plugin-for-centralized-authentication)
> > 2. website/blog/2021/08/10/dynamically-manage-Nginx-clustering.md
> > 15. Hyperchain
> >
> > 1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/09/apache-apisix-in-hyperchain
> > 2. website/blog/2021/08/09/Apache-APISIX-in-Hyperchain.md
> >
> > Once fixed, please examine in https://deploy-preview-945--apache-apisix.netlify.app/ carefully. Or it takes other reviewers' time to do it for you, which would very likely to slow down the review, approve, and merging process.
>
> all fixed, please take a look
So I went through the first 2 and last 3, they are not fixed yet.
For these files, please update the Chinese blogs' filenames as well.
Take the first one, OPA, for example, you will need to update the Chinese blog’s file name to `open-policy-agent-API-gateway.md`. Since the capitalized letters `API` is not acceptable, you would then need to change both files' names tp `open-policy-agent-api-gateway.md`. Try to build a MVP before applying to all.
The expected results are:
1. URLs does not contain capitalized letters.
2. Blogs' file names are exact matched.
3. `slug`s (if any) are exact matched.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
👷 Deploy Preview for *apache-apisix* processing.
🔨 Explore the source changes: 30e547e29f789553fda9d75b812696fc4b7e6a36
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/6226f004a4f46500089ed05d](https://app.netlify.com/sites/apache-apisix/deploys/6226f004a4f46500089ed05d)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] moonming commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
moonming commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1061432857
@SylviaBABY all fixed, thx
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] moonming commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
moonming commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1061440213
@juzhiyuan please take a look
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] juzhiyuan commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r822304801
##########
File path: .gitignore
##########
@@ -31,3 +31,5 @@ tmp/*
.netlify
scripts/yarn.lock
+
+.history
Review comment:
https://stackoverflow.com/questions/60687569/should-one-track-files-in-ones-history-folder-in-git
After searching Google, the `.history` folder is created by user, our repo doesn't contain this folder.
##########
File path: website/blog/2021/05/24/Tencent-Games.md
##########
@@ -1,13 +1,12 @@
---
title: "How to use API Gateway to process 1 billion traffic daily for Tencent?"
-slug: 2021/05/24/tencent-games
+slug: 2021/05/24/how-tencent-game-use-API-geteway
Review comment:
```suggestion
slug: 2021/05/24/how-tencent-game-uses-api-geteway
```
##########
File path: website/blog/2021/06/21/use-Java-to-write-Apache-APISIX-plugins.md
##########
@@ -1,11 +1,11 @@
---
-title: "How to Write an Apache APISIX Plugin in Java"
-slug: 2021/06/21/use-java-to-write-apache-apisix-plugins
+title: "How to use Java to write plugins for API Gateway?"
+slug: 2021/06/21/how-to-use-java-to-write-plugins-for-api-gateway
Review comment:
Please note, once you updated the slug, the article's original URL will be 404.
##########
File path: website/i18n/zh/docusaurus-plugin-content-blog/2022/01/24/apisix-with-qingcloud-meetup.md
##########
@@ -15,7 +15,7 @@ tags: [Events]
-## 议题 1：API网关上云，如何定义一款好的API网关
+## 议题 1：API 网关上云，如何定义一款好的API 网关
Review comment:
```suggestion
## 议题 1：API 网关上云，如何定义一款好的 API 网关
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] yzeng25 commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
yzeng25 commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1061902191
> > Batching all of these procedures (rename, update keywords, descriptions, add text contents) up in one pull request is not a wise decision. It creates the following problems.
> >
> > 1. Once a file is renamed, its contents appear as all new during review. This creates trouble for reviewers. Put yourself in reviewers' shoes, how would you feel when you need to review a pull request with 215 files (the number of files in this pull request as of 17:36 GMT+8)?
> > 2. Many of the files are ended with time stamp `2022xxxxx` suffixes. Please fix them.
> > 
> > 3. Some of the files are already published on Medium[1] page, which also provides link referring back to Apache APISIX's blog[2]. Do you know changing all links could lead to reference failures as well?
> >
> > I would suggest break this pull request into different parts and solve them one by one.
> >
> > 1. Identify all files that can't be renamed directly for Reason 3 stated above. It can be solved with a trick called `slug`. Update keywords, update descriptions, add text contents on them. This could be a pull request.
> > 2. Update keywords, update descriptions, add text contents for the rest of the files. This could be one or more pull requests, preferably submitting them by months or quarters.
> > 3. Rename files in Part 2. The reason to leave the renaming at the end are to ease the process of review and to avoid merge conflicts. Please think of other contributors and other pull requests hanging there as well. This could be another pull request.
> >
> > I know you are eager to solve this problem soon. But using brutal force to solve the problem just isn't the most effective way. Things are always more complicated than your imagination. Please think twice before you act.
> > Please fix the lint as well, thanks!
> > [1]https://medium.com/@ApacheAPISIX [2]https://apisix.apache.org/blog
>
> 1 and 2 are both fixed. and 3 is not the issue of apisix website, and we can update the links in Medium after this PR merged.
There are another 15 problems listed below. The cause is only renaming en-us blogs' names but not zh-cn blogs' names, or the other way around. Please fix them.
1. When renaming or adding `slug` to files, please make sure en-us blogs' names and `slug`(if any) are matched up with those of zh-cn blogs'.
2. The existing `-API-` in filenames is not acceptable, it will create problems of case sensitive URLs again. Please modify them to `-api-`.
Here is the list of 15 problems.
1. OPA
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/12/24/open-policy-agent-API-gateway
4. website/blog/2021/12/22/google-logging-API-gateway.md
3. Google Cloud Logging
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/12/22/google-logging-API-gateway
2. website/blog/2021/12/22/google-logging-API-gateway.md
5. Datadog
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/12/datadog-API-gateway
2. website/blog/2021/11/12/datadog-API-gateway.md
6. Observability of API gateway
1. website/blog/2021/11/04/observability-of-api-gateway.md
2. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/04/observability-of-api-gateway/
7. Airwallex
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/11/03/airwallex-api-gateway/
2. website/blog/2021/11/03/airwallex-API-gateway.md
8. WPS
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/28/wps-usercase
2. website/blog/2021/09/28/WPS-API-gateway.md
9. UPYUN
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/24/upyun-API-gateway
2. website/blog/2021/09/24/upyun-API-gateway.md
10. DIAN
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/18/xiaodian-API-gateway
2. website/blog/2021/09/18/xiaodian-API-gateway.md
11. Tencent Cloud
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/16/tencent-cloud-API-gateway
2. website/blog/2021/09/16/tencent-cloud-API-gateway.md
12. Youzanyun
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/14/youzan-mocroservice-API-gateway
2. website/blog/2021/09/14/youzan-mocroservice-API-gateway.md
13. China Mobile Cloud
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/13/china-mobile-cloud-api-gateway
2. website/blog/2021/09/13/china-mobile-cloud-api-gateway.md
14. iQiYi
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/09/07/iqiyi-api-gateway
2. website/blog/2021/09/07/iQIYI-API-gateway.md
15. Airwallex Interview
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/17/airwallex-apache-apisix
2. website/blog/2021/08/17/airwallex-apache-apisix.md
16. Apache APISIX Architecture Analysis
1. [https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/10/dynamically-manage-Nginx-clustering](https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/16/using-the-apache-apisix-openid-connect-plugin-for-centralized-authentication)
2. website/blog/2021/08/10/dynamically-manage-Nginx-clustering.md
17. Hyperchain
1. https://deploy-preview-945--apache-apisix.netlify.app/zh/blog/2021/08/09/apache-apisix-in-hyperchain
2. website/blog/2021/08/09/Apache-APISIX-in-Hyperchain.md
Once fixed, please examine in https://deploy-preview-945--apache-apisix.netlify.app/ carefully. Or it takes other reviewers' time to do it for you, which would very likely to slow down the review, approve, and merging process.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
✔️ Deploy Preview for *apache-apisix* ready!
🔨 Explore the source changes: 9dbeacda00a10bc5ca300f94bc48d7635a30c2c9
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/6228610aee103200078befb0](https://app.netlify.com/sites/apache-apisix/deploys/6228610aee103200078befb0)
😎 Browse the preview: [https://deploy-preview-945--apache-apisix.netlify.app](https://deploy-preview-945--apache-apisix.netlify.app)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r821242065
##########
File path: website/blog/2021/09/07/iQIYI-API-gateway.md
##########
@@ -1,8 +1,8 @@
---
-title: "Based on Apache APISIX, iQIYI API Gateway Update and landing practice"
-slug: 2021/09/07/iqiyi-usercase
+title: "Why did iQIYI choose Apache APISIX as the api gateway?"
Review comment:
```suggestion
title: "Why did iQIYI choose Apache APISIX as the API Gateway?"
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
👷 Deploy Preview for *apache-apisix* processing.
🔨 Explore the source changes: 08c1debb7d5d4aa6f081e357c67c3a21c7dcb8c4
🔍 Inspect the deploy log: [https://app.netlify.com/sites/apache-apisix/deploys/62269ee82c1546000777069e](https://app.netlify.com/sites/apache-apisix/deploys/62269ee82c1546000777069e)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] moonming removed a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
moonming removed a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1064928972
> 3\. `slug`s
it will not affect SEO if not change `slugs`, right?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] juzhiyuan commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1065903817
> > it will not affect SEO if not change slugs, right?
>
> Sure. But 301 redirect is also a solution.
Apache APISIX Website is hosted on the ASF's Infra, by Apache Web Server. We could build 301 rules but the ASF Infra may not accept it easily (bcoz I tried to enable HTTPS by default but got rejected 😅).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SkyeYoung commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SkyeYoung commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r824549411
##########
File path: website/blog/2021/06/21/use-Java-to-write-Apache-APISIX-plugins.md
##########
@@ -1,11 +1,11 @@
---
-title: "How to Write an Apache APISIX Plugin in Java"
-slug: 2021/06/21/use-java-to-write-apache-apisix-plugins
+title: "How to use Java to write plugins for API Gateway?"
+slug: 2021/06/21/how-to-use-java-to-write-plugins-for-api-gateway
Review comment:
> Previously tried plugin-client-redirect, but it was not able to pass checks.
>
> [#903 (comment)](https://github.com/apache/apisix-website/pull/903#issuecomment-1050774757)
What a strange problem.🤔
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] yzeng25 commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
yzeng25 commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r824544353
##########
File path: website/blog/2021/06/21/use-Java-to-write-Apache-APISIX-plugins.md
##########
@@ -1,11 +1,11 @@
---
-title: "How to Write an Apache APISIX Plugin in Java"
-slug: 2021/06/21/use-java-to-write-apache-apisix-plugins
+title: "How to use Java to write plugins for API Gateway?"
+slug: 2021/06/21/how-to-use-java-to-write-plugins-for-api-gateway
Review comment:
Previously tried plugin-client-redirect, but it was not able to pass checks.
https://github.com/apache/apisix-website/pull/903#issuecomment-1050774757
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SkyeYoung commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SkyeYoung commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1064936712
> it will not affect SEO if not change slugs, right?
Sure. But 301 redirect is also a solution.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] juzhiyuan commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
juzhiyuan commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1064927127
Hi, just one alert: if this PR gets merged, all changes files' URLs will change and it will indeed affect SEO.
Also check https://github.com/apache/apisix-website/issues/957
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r821244205
##########
File path: website/blog/2022/01/21/apisix-hashicorp-vault-integration.md
##########
@@ -25,6 +25,10 @@ tags: [Technology,Authentication]
With the rise of microservice-based architecture, keeping things secure has become much more challenging than earlier. We are far beyond the point where our 100 instances of backend servers are accessing our database server with a single static secret credential because if in case of a credential leakage the whole system is compromised and revocation of that credential causes a massive service outage (now no one can access anything unless the instances are reconfigured). We can't eliminate the possibility of a security breach because sometimes unexpected does happen. Instead, it's totally up to us to control the blast radius in these situations. To tackle scenarios like this, a popular solution like [HashiCorp Vault](https://www.vaultproject.io/) comes into the picture in a production environment to act as an identity-based secrets and encryption management system. In this article, I have demonstrated how to integrate Vault with Apache APISIX (a cloud-native API Gateway) [jwt-auth p
lugin](https://apisix.apache.org/docs/apisix/plugins/jwt-auth) to effectively use excellence from both worlds.
+
+### About Apache APISIX
+
+[Apache APISIX](https://github.com/apache/apisix) is a dynamic, real-time, high-performance API gateway that provides rich traffic management features such as load balancing, dynamic upstream, canary release, service meltdown, authentication, observability, etc. Apache APISIX not only supports dynamic plug-in changes and hot-plugging, but also has a number of useful plug-ins.OpenID Connect Plug-in for Apache APISIX With support for the OpenID Connect protocol, users can use this plug-in to enable Apache APISIX to interface with Authing services and be deployed as a centralized authentication gateway in the enterprise.
Review comment:
```suggestion
### About Apache APISIX
[Apache APISIX](https://github.com/apache/apisix) is a dynamic, real-time, high-performance API gateway that provides rich traffic management features such as load balancing, dynamic upstream, canary release, service meltdown, authentication, observability, etc. Apache APISIX not only supports dynamic plug-in changes and hot-plugging, but also has a number of useful plug-ins.OpenID Connect Plug-in for Apache APISIX With support for the OpenID Connect protocol, users can use this plug-in to enable Apache APISIX to interface with Authing services and be deployed as a centralized authentication gateway in the enterprise.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on a change in pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on a change in pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#discussion_r821244989
##########
File path: website/blog/2022/01/25/apisix-grpc-web-integration.md
##########
@@ -22,6 +22,9 @@ tags: [Technology,Ecosystem]
<!--truncate-->
+### About Apache APISIX
+
+[Apache APISIX](https://github.com/apache/apisix) is a dynamic, real-time, high-performance API gateway that provides rich traffic management features such as load balancing, dynamic upstream, canary release, service meltdown, authentication, observability, etc. Apache APISIX not only supports dynamic plug-in changes and hot-plugging, but also has a number of useful plug-ins.OpenID Connect Plug-in for Apache APISIX With support for the OpenID Connect protocol, users can use this plug-in to enable Apache APISIX to interface with Authing services and be deployed as a centralized authentication gateway in the enterprise.
Review comment:
```suggestion
### About Apache APISIX
[Apache APISIX](https://github.com/apache/apisix) is a dynamic, real-time, high-performance API gateway that provides rich traffic management features such as load balancing, dynamic upstream, canary release, service meltdown, authentication, observability, etc. Apache APISIX not only supports dynamic plug-in changes and hot-plugging, but also has a number of useful plug-ins.OpenID Connect Plug-in for Apache APISIX With support for the OpenID Connect protocol, users can use this plug-in to enable Apache APISIX to interface with Authing services and be deployed as a centralized authentication gateway in the enterprise.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] SylviaBABY commented on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
SylviaBABY commented on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1061316274
@moonming I left some comments about details and Lint comments in CI(the last 2 comments), pls update.
Others LGTM, will approve and go on fixing the SEO details in the future.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-website] netlify[bot] edited a comment on pull request #945: docs: Optimize text descriptions and keywords.
Posted by GitBox <gi...@apache.org>.
netlify[bot] edited a comment on pull request #945:
URL: https://github.com/apache/apisix-website/pull/945#issuecomment-1060250333
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org