You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CHANGELOG.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -29,18 +29,18 @@ This is a release candidate.
29
29
30
30
# Core
31
31
32
-
- Refactor front-end with Admin-API.
32
+
- Refactor frontend with Admin-API.
33
33
- Manager-API removes dependency on MySQL.
34
34
- Support plugin orchestration.
35
-
- Setting standards for front-end internationalization.
35
+
- Setting standards for frontend internationalization.
36
36
- New deployment pattern.
37
37
- Add more test cases.
38
38
- Document Enhancement.
39
39
- Add back-end E2E test examples.
40
40
- Improve CI testing.
41
41
- Support log save to local file.
42
42
- Optimize the deployment process.
43
-
- Add E2E test examples to the front-end. [#619](https://github.com/apache/apisix-dashboard/pull/619)
43
+
- Add E2E test examples to the frontend. [#619](https://github.com/apache/apisix-dashboard/pull/619)
44
44
- Fix the Promethues plugin updating incorrect values when updating routes. [#666](https://github.com/apache/apisix-dashboard/pull/666)
45
45
- Fix page display exceptions when the Redirect option is selected as Enable HTTPS in the Route page. [#692](https://github.com/apache/apisix-dashboard/pull/692)
Copy file name to clipboardexpand all lines: README.md
+36-62
Original file line number
Diff line number
Diff line change
@@ -21,90 +21,64 @@ English | [简体中文](./README.zh-CN.md)
21
21
22
22
# Apache APISIX Dashboard
23
23
24
-
Apache APISIX Dashboard for [Apache APISIX](https://github.com/apache/apisix)
24
+
## What's Apache APISIX Dashboard
25
25
26
-
The goal of Apache APISIX Dashboard project is to let users to quickly experience and learn Apache APISIX, but it still cannot be used directly in a production environment.
26
+
The Apache APISIX Dashboard is designed to make it as easy as possible for users to operate [Apache APISIX](https://github.com/apache/apisix) through a frontend interface.
27
27
28
-
Its function is always a subset of Apache APISIX, and may lag behind the rapid iteration of Apache APISIX.
28
+
The Dashboard is the control plane and performs all parameter checks; Apache APISIX mixes data and control planes and will evolve to a pure data plane.
29
29
30
-
If you need to use the Apache APISIX Dashboard project in a production system, you need to enhance user permissions, communication security, high availability and other advanced features.
30
+
This project includes `manager-api`, which will gradually replace `admin-api` in Apache APISIX.
31
31
32
-
## Installation
32
+
Note: Currently the Dashboard does not have complete coverage of Apache APISIX features, [visit here](https://github.com/apache/apisix-dashboard/milestones) to view the milestones.
33
33
34
-
Support multiple ways to install Apache APISIX Dashboard
34
+

35
35
36
-
### Docker
36
+
##Project structure
37
37
38
-
Start a runnable version by the following method
39
-
40
-
-[Deploy With Docker](./docs/deploy-with-docker.md)
41
-
42
-
### Build from Source Code
43
-
44
-
To build Apache APISIX Dashboard from source code, first make sure that your `golang` version is 1.13 or greater.
45
-
46
-
Also you need to make sure that `Node.js` and `yarn` are installed.
Then you can find all files (configuration files, executable files, web static resources) needed to run Apache APISIX Dashboard in the `./output` directory.
55
-
56
-
Start by the following commands.
57
-
58
-
```sh
59
-
$ cd ./output
60
-
$ exec ./manager-api
39
+
.
40
+
├── CHANGELOG.md
41
+
├── CHANGELOG.zh-CN.md
42
+
├── CODE_OF_CONDUCT.md
43
+
├── CONTRIBUTING.md
44
+
├── Dockerfile
45
+
├── LICENSE
46
+
├── Makefile
47
+
├── NOTICE
48
+
├── README.md
49
+
├── README.zh-CN.md
50
+
├── api
51
+
├── docs
52
+
├── licenses
53
+
└── web
61
54
```
62
55
63
-
`makefile` provides the following commands.
56
+
1. The `api` directory is used to store the `manager-api` source codes, which is used to manage `etcd` and provide APIs to the frontend interface.
57
+
2. The `web` directory is used to store the frontend source codes.
64
58
65
-
```text
66
-
Makefile rules:
59
+
## Build then launch
67
60
68
-
help: Show Makefile rules
69
-
build: Build Apache APISIX Dashboard, it contains web and manager-api
70
-
api-test: Run the tests of manager-api
71
-
api-run: Run the manager-api
72
-
api-stop: stop manager-api
73
-
go-lint: Lint Go source code
74
-
license-check: Check Apache APISIX Dashboard Source Codes for Apache License
75
-
```
61
+
Support the following ways currently.
76
62
77
-
For more detailed construction steps, see - [Build from Source Codes](./docs/deploy.md)
63
+
-[Source Codes](./docs/deploy.md)
64
+
-[Docker](./docs/deploy-with-docker.md)
78
65
79
-
### For developer
66
+
##Development
80
67
81
-
Apache APISIX Dashboard provides a management interface for [Apache APISIX](https://github.com/apache/apisix), you need to [install APISIX first](https://github.com/apache/apisix#configure-and-installation).
68
+
Please refer to the [Development Guide](./docs/develop.md).
82
69
83
-
Please refer to here to start `manager-api` and `web`respectively.
Please refer to the [Contribution Guide](./CONTRIBUTING.md) for a more detailed infomation.
103
77
104
78
## FAQ
105
79
106
-
1. If you need the Apache APISIX Dashboard 1.0 which is built with Vue.js, please refer to [master-vue](https://github.com/apache/apisix-dashboard/tree/master-vue).
80
+
Please refer to the [FAQ](./docs/FAQ.md) for more known issues.
107
81
108
-
2. The Apache APISIX Dashboard 2.0 removes MySQL which [Apache APISIX Dashboard 1.5](https://github.com/apache/apisix-dashboard/tree/backup-1.5-latest) is relied on.
82
+
## License
109
83
110
-
3. If you are using APISIX 1.5 or below, kindly note that the v2 api store and v3 api store are [separate and isolated](https://etcd.io/docs/v3.4.0/op-guide/v2-migration/). Apache APISIX Dashboard v2.0 and above use the etcd v3 api, APISIX 1.5 and below use the etcd v2 api.
# Licensed to the Apache Software Foundation (ASF) under one or more
4
+
# contributor license agreements. See the NOTICE file distributed with
5
+
# this work for additional information regarding copyright ownership.
6
+
# The ASF licenses this file to You under the Apache License, Version 2.0
7
+
# (the "License"); you may not use this file except in compliance with
8
+
# the License. You may obtain a copy of the License at
9
+
#
10
+
# http://www.apache.org/licenses/LICENSE-2.0
11
+
#
12
+
# Unless required by applicable law or agreed to in writing, software
13
+
# distributed under the License is distributed on an "AS IS" BASIS,
14
+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
15
+
# See the License for the specific language governing permissions and
16
+
# limitations under the License.
17
+
#
18
+
-->
19
+
20
+
# FAQ
21
+
22
+
### 1. Vue.js version of the Dashboard
23
+
24
+
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).
25
+
26
+
### What are the differences between Dashboard version 2.0 and version 1.5?
27
+
28
+
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.
29
+
30
+
### 3. Etcd compatibility issues
31
+
32
+
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.
33
+
34
+
### 4. After modifying the plugin schema or creating a custom plugin in Apache APISIX, why can't I find it on the dashboard?
35
+
36
+
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.
37
+
38
+
1. Install [Lua](https://www.lua.org/download.html) and `zip`.
39
+
40
+
2. Execute the following commands.
41
+
42
+
```sh
43
+
# `$version` is the version number of Apache APISIX, e.g. master or 2.0.
44
+
$ api/build-tools/schema-sync.sh $version
45
+
```
46
+
47
+
If you have a custom plugin, make sure it is in the `apisix` directory and use the following command.
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.
0 commit comments