-
Notifications
You must be signed in to change notification settings - Fork 534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(docs): improve README & Deploy #785
Merged
Changes from all commits
Commits
Show all changes
29 commits
Select commit
Hold shift + click to select a range
25f1082
feat(doc): update README & deploy
juzhiyuan bedfbc5
feat(docs): added FAQ
juzhiyuan da2c257
fix: linkx
juzhiyuan 81ce834
feat(docs): update deploy with docker
juzhiyuan 63424f7
feat(docs): update FAQ
juzhiyuan fc051cd
feat: update README
juzhiyuan 4d8eade
feat: update README
juzhiyuan de3c204
feta: update README
juzhiyuan bcfab48
fix: link
juzhiyuan ba921e8
feat: update deploy with docker
juzhiyuan beb0a67
feat(docs): added tip for some users
juzhiyuan 95574cc
feat(doc): improve deploy with docker
juzhiyuan 21bfc23
feat(docs): improve deploy with docker
juzhiyuan fa8ae14
feat(doc): update run with docker
juzhiyuan d37a5fc
feat(doc): improve deploy
juzhiyuan 3589c1d
feat(doc): added more info
juzhiyuan 2dd4b2e
feat(doc): added more info
juzhiyuan fe0063a
feat(doc): remove extra info
juzhiyuan 701f87d
feat: added more detailed
juzhiyuan 62e7a15
fix: CI fail according `api/conf/conf.yaml ` is changed.
johzchen 8014a91
fix: revert changed
johzchen 90a421b
Merge branch 'v2.0' into feat-docs
johzchen f7691bd
Merge branch 'v2.0' into feat-docs
juzhiyuan de694e0
feat(docs): improve English version
juzhiyuan 775d102
feat(docs): use frontend instead, just like backend
juzhiyuan 1925da2
feat(docs): remove extra statements
juzhiyuan d55aa90
feat(docs): update typo
juzhiyuan 699774e
feat(docs): remove startup with message
juzhiyuan a57d29c
feat: update CI's name
juzhiyuan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
<!-- | ||
# | ||
# Licensed to the Apache Software Foundation (ASF) under one or more | ||
# contributor license agreements. See the NOTICE file distributed with | ||
# this work for additional information regarding copyright ownership. | ||
# The ASF licenses this file to You under the Apache License, Version 2.0 | ||
# (the "License"); you may not use this file except in compliance with | ||
# the License. You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, | ||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
# | ||
--> | ||
|
||
# FAQ | ||
|
||
### 1. Vue.js version of the Dashboard | ||
|
||
If you need a Vue.js build of the Apache APISIX Dashboard 1.0, use the [master-vue branch](https://github.com/apache/apisix-dashboard/tree/master-vue). | ||
|
||
### What are the differences between Dashboard version 2.0 and version 1.5? | ||
|
||
The 2.0 version of the dashboard removed MySQL from [version 1.5](https://github.com/apache/apisix-dashboard/tree/backup-1.5-latest) and will operate directly on etcd. | ||
|
||
### 3. Etcd compatibility issues | ||
|
||
If you are using Apache APISIX below v2.0, be aware that the data from the etcd v2 API is [not compatible](https://etcd.io/docs/v3.4.0/op-guide/v2-migration/) with the data from the v3 API. Apache APISIX Dashboard v2.0 and above uses the etcd v3 API, and apisix 1.5 and below uses the etcd v2 API. | ||
|
||
### 4. After modifying the plugin schema or creating a custom plugin in Apache APISIX, why can't I find it on the dashboard? | ||
|
||
Since the Dashboard caches the jsonschema data of the plugins in Apache APISIX, you need to synchronize the data in the Dashboard after you create your custom plugins in Apache APISIX, which currently **only supports manual operation**, this issue will be optimized in the following versions. Please follow the following guide. | ||
|
||
1. Install [Lua](https://www.lua.org/download.html) and `zip`. | ||
|
||
2. Execute the following commands. | ||
|
||
```sh | ||
# `$version` is the version number of Apache APISIX, e.g. master or 2.0. | ||
$ api/build-tools/schema-sync.sh $version | ||
``` | ||
|
||
If you have a custom plugin, make sure it is in the `apisix` directory and use the following command. | ||
|
||
```sh | ||
$ api/build-tools/schema-sync.sh /path/to/apisix | ||
|
||
# e.g | ||
$ api/build-tools/schema-sync.sh /usr/local/apisix | ||
``` | ||
|
||
After the command finishes executing, if you are using a binary `manager-api` that has already been built, you will need to manually copy `api/conf/schema.json` to the `conf` directory under the Dashboard **working directory**. where **working directory** refers to the `conf` directory under this [document](./deploy.md) is the `output` directory, or the directory with the modified name, that is generated in the root directory after the build is complete. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer the old style, it is clearer and easier to read.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The newer is formatted by tools 🤔 then it seems that it's not a good idea to have too many comments in this file.