Git Product home page Git Product logo

apinto-dashboard's Introduction

Apinto Dashboard

Apinto Dashboad主版本应与 Apinto主版本一起使用。 最新发布的Apinto Dashboad版本是3.0.1,可与Apinto0.12.10以上版本兼容。

Demo

体验地址:demo-dashboard.apinto.com

提供6个体验账号:apinto-1、apinto-2、apinto-3、apinto-4、apinto-5、apinto-6

密码均为:12345678

什么是Apinto Dashboad V3.0

Apinto Dashboard V3.0 是一个可视化控制台项目,基于开源网关 Apinto,并满足企业级 API 网关需求场景。通过 Dashboard,可以管理集群、上游、应用和 API 等模块,并以集群维度管理各个模块的生命周期。该项目具有出色的用户操作体验,配置流程简短,上手难度低。

Apinto Dashboard与Apinto交互流程如下图所示: img_v2_22590d84-f8a4-4d3a-9c67-b481ecfdf1fg

集群管理:管理各个环境的集群,给集群配置证书、配置并发布该集群下的环境变量、监控并管理集群下各个网关节点、配置管理等。

上游服务:上游管理和服务发现。服务发现支持consul、eureka、nacos注册中心;上游管理是管理所有提供API调用的后端系统,都需要上线到指定的集群才生效;

API管理:支持业务域分组,管理所有后端系统提供的API及其生命周期,根据业务上下线到相应的集群。

应用管理:管理所有调用方,配置请求网关的鉴权,以及支持转发后端的额外参数鉴权,上下线到指定集群生效。

服务治理:针对不同集群配置并上线限流、访问、熔断、灰度、缓存等策略,保障网关集群以及后端系统稳定工作。

网关插件:即将开放,管理Apinto插件,Apinto内置几十个插件,同时支持自定义添加插件。

企业插件:即将提供并支持自定义业务型企业插件,供用户安装使用,业务型企业插件如:用户角色、监控告警、日志、API文档、开放平台、安全防护、数据分析、调用链、mock、在线调测、安全测试、国密、多协议……

系统管理:配置邮箱,配置告警模板等。

迭代计划

image

如果您是个人开发者,可基于API网关相关的业务场景开发有价值的网关插件或企业级插件,并且愿意分享给Apinto,您将会成为Apinto的杰出贡献者或得到一定的收益。 如果您是企业,可基于Apinto网关开发企业级插件,成为Apinto的合作伙伴。

部署

安装包部署
安装前,需要确保已经安装了Mysql 5.7.x或以上版本、Redis 5.0-6.2.7,并且Redis使用Cluster模式启动。若未安装,可参考下文的`安装Redis及Mysql`教程

1、下载最新版本`apinto-dashboard`

apinto-dashboard v3.0.1版本示例

wget https://github.com/eolinker/apinto-dashboard/releases/download/v3.0.1/apserver_v3.0.1_linux_amd64.tar.gz

安装包支持Linux、Darwin系统,AMD64、ARM64架构,使用者可以按需到Release页面进行下载。

2、解压安装包,并进入对应目录

tar -zxvf apserver_v3.0.1_linux_amd64.tar.gz && cd apserver_v3.0.1

3、安装程序

./install.sh

执行过程中,我们可以选择安装的目录,若无需更改,输入y即可

4、编辑配置文件config.yml

port: 服务监听的端口号
mysql:
  user_name: "数据库用户名"
  password: "数据库密码"
  ip: "数据库IP地址"
  port: 端口号
  db: "数据库DB"
error_log:
  dir: work/logs               # 日志放置目录, 仅支持绝对路径, 不填则默认为执行程序上一层目录的work/logs. 若填写的值不为绝对路径,则以上一层目录为相对路径的根目录,比如填写 work/test/logs, 则目录为可执行程序所在目录的 ../work/test/logs
  file_name: error.log         # 错误日志文件名
  log_level: warning            # 错误日志等级,可选:panic,fatal,error,warning,info,debug,trace 不填或者非法则为info
  log_expire: 7d                # 错误日志过期时间,默认单位为天,d|天,h|小时, 不合法配置默认为7d
  log_period: day               # 错误日志切割周期,仅支持day、hour
redis:
  user_name: "redis集群密码"
  password: "redis集群密码"
  addr:
   - 192.168.128.198:7201
   - 192.168.128.198:7202

示例配置

port: 18080
mysql:
  user_name: "root"
  password: "123456"
  ip: "127.0.0.1"
  port: 33306
  db: "apinto"
error_log:
  dir: work/logs               # 日志放置目录, 仅支持绝对路径, 不填则默认为执行程序上一层目录的work/logs. 若填写的值不为绝对路径,则以>上一层目录为相对路径的根目录,比如填写 work/test/logs, 则目录为可执行程序所在目录的 ../work/test/logs
  file_name: error.log         # 错误日志文件名
  log_level: warning            # 错误日志等级,可选:panic,fatal,error,warning,info,debug,trace 不填或者非法则为info
  log_expire: 7d                # 错误日志过期时间,默认单位为天,d|天,h|小时, 不合法配置默认为7d
  log_period: day               # 错误日志切割周期,仅支持day、hour
redis:
  user_name: ""
  password: "123456"
  addr:
   - 172.100.0.1:7201
   - 172.100.0.1:7202

5、启动控制台

./run.sh start
Docker部署
安装前,需要确保已经安装了Mysql 5.7.x或以上版本、Redis 5.0-6.2.7,并且Redis使用Cluster模式启动。若未安装,可参考下文的`安装Redis及Mysql`教程

1、安装`Apinto-Dashboard`
docker run -dt --name apinto-dashboard --restart=always \
-p 18080:8080 -v /var/log/apinto/apinto-dashboard/work:/apinto-dashboard/work \
--network=apinto --privileged=true \
-e MYSQL_USER_NAME=root -e MYSQL_IP=apinto_mysql \
-e MYSQL_PWD={MYSQL_PWD} -e MYSQL_PORT=3306 -e MYSQL_DB=apinto \
-e REDIS_ADDR=172.100.0.1:7201,172.100.0.1:7202,172.100.0.1:7203 \
-e REDIS_PWD={REDIS_PWD} eolinker/apinto-dashboard

上述配置中,使用 "{}" 包裹的均为变量,相关变量说明如下:

  • MYSQL_PWD:Mysql数据库root用户的密码
  • REDIS_PWD:Redis数据库密码

示例命令:

docker run -dt --name apinto-dashboard --restart=always \
-p 18080:8080 -v /var/log/apinto/apinto-dashboard/work:/apinto-dashboard/work \
--network=apinto --privileged=true \
-e MYSQL_USER_NAME=root -e MYSQL_IP=apinto_mysql \
-e MYSQL_PWD=123456 -e MYSQL_PORT=3306 -e MYSQL_DB=apinto \
-e REDIS_ADDR=172.100.0.1:7201,172.100.0.1:7202,172.100.0.1:7203 \
-e REDIS_PWD=123456 eolinker/apinto-dashboard
安装Redis及Mysql
1、新建docker网段
docker network create --driver bridge --subnet=172.100.0.0/24 --gateway=172.100.0.1 apinto

2、安装Mysql

docker run -dt --name apinto_mysql -p {PORT}:3306 \
-v /var/lib/apinto/mysql:/var/lib/mysql \
--network=apinto --privileged=true --restart=always \
-e MYSQL_ROOT_PASSWORD={PASSWORD} -e MYSQL_DATABASE=apinto \
mysql:5.7.34 --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci

上述命令中,使用{}包裹的为可修改变量,变量说明如下

  • PORT:宿主机映射端口号
  • PASSWORD:Mysql数据库root用户的密码

示例命令:

docker run -dt --name apinto_mysql -p 33306:3306 \
-v /var/lib/apinto/mysql:/var/lib/mysql \
--network=apinto --privileged=true \
-e MYSQL_ROOT_PASSWORD=123456 -e MYSQL_DATABASE=apinto \
mysql:5.7.34 --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci

3、安装Redis

docker run -dt --name redis_cluster --restart=always \
-v /var/lib/apinto/redis-cluster/data:/usr/local/cluster_redis/data \
-e REDIS_PWD={PASSWORD} -e HOST={HOST} -e PORT=7201 \
--net=host eolinker/cluster-redis:6.2.7

上述命令中,使用{}包裹的为可修改变量,变量说明如下

  • PASSWORD:Redis数据库密码
  • HOST:Redis广播IP,可设置宿主机的局域网IP/外网IP,建议此处设置宿主机的局域网IP。

查看宿主机IP方法如下:

ip route

执行后得到下列IP列表,从下表可以看到,宿主机默认局域网ip172.18.31.253

示例命令:

docker run -dt --name redis_cluster --restart=always \
-v /var/lib/apinto/redis-cluster/data:/usr/local/cluster_redis/data \
-e REDIS_PWD=123456 -e HOST=172.18.31.253 -e PORT=7201 \
--net=host eolinker/cluster-redis:6.2.7
Docker-Compose一键部署
使用该方式部署,会将Mysql、Redis也一并安装启动。

1、编辑`docker-compose.yml`文件
vi docker-compose.yml

2、修改文件配置

version: '3'
services:
  mysql:
    image: mysql:5.7.34
    privileged: true
    restart: always
    container_name: apinto_mysql
    hostname: apinto_mysql
    command:
      - "--character-set-server=utf8mb4"
      - "--collation-server=utf8mb4_unicode_ci"
    ports:
      - "33306:3306"
    environment:
      - MYSQL_ROOT_PASSWORD={MYSQL_PWD}
      - MYSQL_DATABASE=apinto
    volumes:
      - /var/lib/apinto/mysql:/var/lib/mysql
    networks:
      - apinto
  apinto-dashboard:
    image: eolinker/apinto-dashboard
    container_name: apinto-dashboard
    privileged: true
    restart: always
    networks:
      - apinto
    ports:
      - "18080:8080"
    depends_on:
      - mysql
      - redis_cluster
    environment:
      - MYSQL_USER_NAME=root
      - MYSQL_PWD={MYSQL_PWD}
      - MYSQL_IP=apinto_mysql
      - MYSQL_PORT=3306                 #mysql端口
      - MYSQL_DB="apinto"
      - ERROR_DIR=/apinto-dashboard/work/logs  # 日志放置目录
      - ERROR_FILE_NAME=error.log          # 错误日志文件名
      - ERROR_LOG_LEVEL=info               # 错误日志等级,可选:panic,fatal,error,warning,info,debug,trace 不填或者非法则为info
      - ERROR_EXPIRE=7d                    # 错误日志过期时间,默认单位为天,d|天,h|小时, 不合法配置默认为7d
      - ERROR_PERIOD=day                  # 错误日志切割周期,仅支持day、hour
      - REDIS_ADDR=172.100.0.1:7201,172.100.0.1:7202,172.100.0.1:7203,172.100.0.1:7204,172.100.0.1:7205,172.100.0.1:7206 #Redis集群地址 多个用,隔开
      - REDIS_PWD={REDIS_PWD}                         # Redis密码
    volumes:
      - /var/log/apinto/apinto-dashboard/work:/apinto-dashboard/work   #挂载log到主机目录
  redis_cluster:
    container_name: redis_cluster
    image: eolinker/cluster-redis:6.2.7
    hostname: redis_cluster
    privileged: true
    restart: always
    environment:
      - REDIS_PWD={REDIS_PWD}
      - PORT=7201
      - HOST={HOST}
    volumes: 
      - /var/lib/apinto/redis-cluster/data:/usr/local/cluster_redis/data
    network_mode: host
networks:
  apinto:
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: 172.100.0.0/24

上述配置中,使用 "{}" 包裹的均为变量,相关变量说明如下:

  • MYSQL_PWD:mysql数据库root用户初始化密码
  • REDIS_PWD:redis密码
  • HOST:Redis广播IP,可设置宿主机的局域网IP/外网IP,建议此处设置宿主机的局域网IP。

查看宿主机IP方法如下:

ip route

执行后得到下列IP列表,从下表可以看到,宿主机默认局域网ip172.18.31.251

替换后配置示例如下:

version: '3'
services:
  mysql:
    image: mysql:5.7.34
    privileged: true
    restart: always
    container_name: apinto_mysql
    hostname: apinto_mysql
    command:
      - "--character-set-server=utf8mb4"
      - "--collation-server=utf8mb4_unicode_ci"
    ports:
      - "33306:3306"
    environment:
      - MYSQL_ROOT_PASSWORD=123456
      - MYSQL_DATABASE=apinto
    volumes:
      - /var/lib/apinto/mysql:/var/lib/mysql
    networks:
      - apinto
  apinto-dashboard:
    image: eolinker/apinto-dashboard
    container_name: apinto-dashboard
    privileged: true
    restart: always
    networks:
      - apinto
    ports:
      - "18080:8080"
    depends_on:
      - mysql
      - redis_cluster
    environment:
      - MYSQL_USER_NAME=root
      - MYSQL_PWD=123456
      - MYSQL_IP=apinto_mysql
      - MYSQL_PORT=3306                 #mysql端口
      - MYSQL_DB="apinto"
      - ERROR_DIR=/apinto-dashboard/work/logs  # 日志放置目录
      - ERROR_FILE_NAME=error.log          # 错误日志文件名
      - ERROR_LOG_LEVEL=info               # 错误日志等级,可选:panic,fatal,error,warning,info,debug,trace 不填或者非法则为info
      - ERROR_EXPIRE=7d                    # 错误日志过期时间,默认单位为天,d|天,h|小时, 不合法配置默认为7d
      - ERROR_PERIOD=day                  # 错误日志切割周期,仅支持day、hour
      - REDIS_ADDR=172.100.0.1:7201,172.100.0.1:7202,172.100.0.1:7203,172.100.0.1:7204,172.100.0.1:7205,172.100.0.1:7206 #Redis集群地址 多个用,隔开
      - REDIS_PWD=123456                         # Redis密码
    volumes:
      - /var/log/apinto/apinto-dashboard/work:/apinto-dashboard/work   #挂载log到主机目录
  redis_cluster:
    container_name: redis_cluster
    image: eolinker/cluster-redis:6.2.7
    hostname: redis_cluster
    privileged: true
    restart: always
    environment:
      - REDIS_PWD=123456
      - PORT=7201
      - HOST=172.18.31.251
    volumes: 
      - /var/lib/apinto/redis-cluster/data:/usr/local/cluster_redis/data
    network_mode: host
networks:
  apinto:
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: 172.100.0.0/24

3、启动程序

docker-compose.yml文件所在目录下执行下列命令,即可一键完成部署。

docker-compose up -d

部署完成结果如下图

浏览器访问

部署完成后,在浏览器输入地址:http://{ip或域名}:{端口号},访问控制台页面

初始账号:admin ,初始密码:12345678 ,部署完成后,建议修改密码。

  • 联系我们

apinto-dashboard's People

Contributors

chaos-cn avatar chen2eric avatar dot-liu avatar hmzzrcs avatar maggieyyy avatar wuk0 avatar zouchenli avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

apinto-dashboard's Issues

help request:

Description

/home/runner/work/apinto-dashboard/apinto-dashboard/app/apserver/redis.go:22

连不上redis

Environment

version: '3'
services:
mysql:
image: mysql:5.7.21
privileged: true
restart: always
container_name: apinto_mysql
hostname: apinto_mysql
ports:
- "33306:3306"
environment:
- MYSQL_ROOT_PASSWORD=123456
- MYSQL_DATABASE=apinto
volumes:
- /var/lib/apinto/mysql:/var/lib/mysql
networks:
- apinto
apinto-dashboard:
image: eolinker/apinto-dashboard
container_name: apinto-dashboard
privileged: true
restart: always
networks:
- apinto
ports:
- "18182:8080"
depends_on:
- mysql
- redis_cluster
environment:
- MYSQL_USER_NAME=root
- MYSQL_PWD=123456
- MYSQL_IP=apinto_mysql
- MYSQL_PORT=3306 #mysql端口
- MYSQL_DB="apinto"
- ERROR_DIR=/apinto-dashboard/work/logs # 日志放置目录
- ERROR_FILE_NAME=error.log # 错误日志文件名
- ERROR_LOG_LEVEL=info # 错误日志等级,可选:panic,fatal,error,warning,info,debug,trace 不填或者非法则为info
- ERROR_EXPIRE=7d # 错误日志过期时间,默认单位为天,d|天,h|小时, 不合法配置默认为7d
- ERROR_PERIOD=day # 错误日志切割周期,仅支持day、hour
- REDIS_ADDR=172.100.0.1:7201,172.100.0.1:7202,172.100.0.1:7203,172.100.0.1:7204,172.100.0.1:7205,172.100.0.1:7206 #Redis集群地址 多个用,隔开
- REDIS_PWD=123456 # Redis密码
volumes:
- /var/log/apinto/apinto-dashboard/work:/apinto-dashboard/work #挂载log到主机目录
redis_cluster:
container_name: redis_cluster
image: eolinker/cluster-redis:6.2.7
hostname: redis_cluster
privileged: true
restart: always
environment:
- REDIS_PWD=123456
- PORT=7201
- HOST=10.1.38.172
volumes:
- /var/lib/apinto/redis-cluster/data:/usr/local/cluster_redis/data
network_mode: host
networks:
apinto:
driver: bridge
ipam:
driver: default
config:
- subnet: 172.100.0.0/24

bug: 上游菜单中的页面数据缺失

Current Behavior

点开上游的页面,就能发现只有15条数据,前端按照20条进行分页查询,但是后端只有15条返回,导致缺失5条

Expected Behavior

No response

Error Logs

No response

Steps to Reproduce

接口: /api/dynamic/upstream/list?page=1&pageSize=20&keyword=&cluster=%5B%5D&namespace=default
此带有dynamic 的请求在api.service.ts underline() 方法中,忽略了驼峰转下划线的转换
后端中,modules/dynamic/dynamic-controller./dynamic.go 获取getPage() 为 pageSize := ctx.Query("page_size"),全局搜索到,后端基本没有pageSize的query 参数获取了。

Environment

  • APINTO Dashboard version (run apinto dashboard version): v3.3.3
  • Operating system (run uname -a): 6.8.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 17 Apr 2024 15:20:28 +0000 x86_64 GNU/Linux

Run with docker compose which do not export mysql, redis(-cluster).

Description

Hi, I read the doc about running with docker-compose, but I noticed that some service like mysql, redis(-cluster) are exported to the host which I believe is not best practise due to port conflicts and also not required.

So, I tried to update my own version of docker-compose. But the following docker-compose.yml do not working.

It failed with the following errors, maybe redis(-cluster) or mysql problems.

version: '3'
services:
  mysql:
    image: mysql:5.7.34
    # image: mysql
    privileged: true
    restart: always
    container_name: mysql
    hostname: mysql
    command:
      - "--character-set-server=utf8mb4"
      - "--collation-server=utf8mb4_unicode_ci"
    ports:
      - 3306
    environment:
      - MYSQL_ROOT_PASSWORD=123456
      - MYSQL_DATABASE=apinto
    volumes:
      - ./mysql:/var/lib/mysql
    networks:
      - apinto
  apinto-gateway:
    image: eolinker/apinto-gateway
    container_name: apinto-gateway
    privileged: true
    restart: always
    networks:
      - apinto
    ports:
      - 8099:8099
      - 9400:9400
      - 9401:9401
    volumes:
      - ./apinto/data:/var/lib/apinto
      - ./apinto/log:/var/log/apinto
  apinto-dashboard:
    image: eolinker/apinto-dashboard
    container_name: apinto-dashboard
    privileged: true
    restart: always
    networks:
      - apinto
    ports:
      - 18088:8080
    depends_on:
      - mysql
      - cluster-redis
    environment:
      - MYSQL_USER_NAME=root
      - MYSQL_PWD=123456
      - MYSQL_IP=mysql
      - MYSQL_PORT=3306
      - MYSQL_DB=apinto
      - ERROR_DIR=/apinto-dashboard/work/logs
      - ERROR_FILE_NAME=error.log
      - ERROR_LOG_LEVEL=info
      - ERROR_EXPIRE=7d
      - ERROR_PERIOD=day
      - REDIS_ADDR=cluster-redis:7201,cluster-redis:7202,cluster-redis:7203,cluster-redis:7204,cluster-redis:7205,cluster-redis:7206
      - REDIS_PWD=123456
    volumes:
      - ./apinto-dashboard/work:/apinto-dashboard/work
  cluster-redis:
    container_name: cluster-redis
    image: eolinker/cluster-redis:6.2.7
    hostname: cluster-redis
    privileged: true
    restart: always
    networks:
      - apinto
    ports:
      - 7201
      - 7202
      - 7203
      - 7204
      - 7205
      - 7206
    environment:
      - REDIS_PWD=123456
      - PORT=7201
      - HOST=localhost
    volumes: 
      - ./redis-cluster/data:/usr/local/cluster_redis/data
networks:
  apinto:
    driver: bridge
    ipam:
      driver: default
      # config:
      #   - subnet: 172.100.0.0/24
[root@localhost apinto_dashboard]# docker compose up 
[+] Running 4/0
 ✔ Container mysql             Running                                                                                                    0.0s 
 ✔ Container cluster-redis     Running                                                                                                    0.0s 
 ✔ Container apinto-gateway    Created                                                                                                    0.0s 
 ✔ Container apinto-dashboard  Created                                                                                                    0.0s 
Attaching to apinto-dashboard, apinto-gateway, cluster-redis, mysql
apinto-dashboard  | mysql:
apinto-dashboard  |   user_name: root
apinto-dashboard  |   password: 123456
apinto-dashboard  |   ip: mysql
apinto-dashboard  |   port: 3306
apinto-dashboard  |   db: apinto
apinto-dashboard  | redis:
apinto-dashboard  |   user_name: 
apinto-dashboard  |   password: 123456
apinto-dashboard  |   addr: 
apinto-dashboard  |     - cluster-redis:7201
apinto-dashboard  |     - cluster-redis:7202
apinto-dashboard  |     - cluster-redis:7203
apinto-dashboard  |     - cluster-redis:7204
apinto-dashboard  |     - cluster-redis:7205
apinto-dashboard  |     - cluster-redis:7206
apinto-dashboard  | port: 8080
apinto-dashboard  | error_log:
apinto-dashboard  |   dir: /apinto-dashboard/work/logs
apinto-dashboard  |   file_name: error.log
apinto-dashboard  |   log_level: info
apinto-dashboard  |   log_expire: 7d
apinto-dashboard  |   log_period: day
apinto-dashboard  | 
apinto-dashboard  | 2023/12/01 00:27:27 /home/runner/go/pkg/mod/gorm.io/[email protected]/callbacks.go:134 Error 1062: Duplicate entry '1' for key 'PRIMARY'
apinto-dashboard  | [1.612ms] [rows:0] INSERT INTO `namespace` (`name`,`create_time`,`id`) VALUES ('default','2023-12-01 00:27:27.179',1)
apinto-dashboard  | [2023-12-01 00:27:27] [ERRO] get module config version:CLUSTERDOWN Hash slot not served
apinto-dashboard  | [2023-12-01 00:27:27] [WARN] lockKey=updateExtender_1701361647 error=CLUSTERDOWN Hash slot not served
apinto-gateway exited with code 0
apinto-gateway exited with code 0
apinto-gateway exited with code 0
apinto-gateway exited with code 0
apinto-gateway exited with code 0
apinto-gateway exited with code 0
apinto-dashboard  | [2023-12-01 00:27:37] [ERRO] get module config version:dial tcp :7201: connect: connection refused
apinto-gateway exited with code 0
apinto-gateway exited with code 0
apinto-dashboard  | [2023-12-01 00:27:47] [ERRO] get module config version:CLUSTERDOWN Hash slot not served
apinto-dashboard  | [2023-12-01 00:27:57] [ERRO] get module config version:CLUSTERDOWN Hash slot not served
apinto-gateway exited with code 0
apinto-dashboard  | [2023-12-01 00:28:00] [WARN] lockKey=updateExtender_1701361680 error=CLUSTERDOWN The cluster is down
apinto-dashboard  | [2023-12-01 00:28:07] [ERRO] get module config version:CLUSTERDOWN The cluster is down
apinto-dashboard  | [2023-12-01 00:28:17] [ERRO] get module config version:dial tcp :7201: connect: connection refused
^CGracefully stopping... (press Ctrl+C again to force)
Aborting on container exit...
[+] Running 4/4
 ✔ Container apinto-dashboard  Stopped                                                                                                   10.3s 
 ✔ Container apinto-gateway    Stopped                                                                                                    0.0s 
 ✔ Container cluster-redis     Stopped                                                                                                   10.7s 
 ✔ Container mysql             Stopped                                                                                                    1.4s 
canceled
[root@localhost apinto_dashboard]#

I do not familar with redis-cluster, could I replace the cluster version to normal redis service and how to do it?

help request:

Description

dashboard什么时候可以配置oauth2鉴权

Environment

  • APINTO Dashboard version: 3.3.3
  • Operating system (run uname -a): ubuntu22.04

help request: 前端编译失败

Description

编译时前端出现错误,编译命令:./scripts/build.sh ./out all

Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:62:3 - error NG8002: Can't bind to 'nzDraggable' since it isn't a known property of 'eo-ng-table'.
1. If 'eo-ng-table' is an Angular component and it has 'nzDraggable' input, then verify that it is part of this module.
2. If 'eo-ng-table' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component.

62   [nzDraggable]="nzDraggable"
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:63:3 - error NG8002: Can't bind to 'nzDragCheck' since it isn't a known property of 'eo-ng-table'.
1. If 'eo-ng-table' is an Angular component and it has 'nzDragCheck' input, then verify that it is part of this module.
2. If 'eo-ng-table' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component.

63   [nzDragCheck]="nzDragCheck"
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:66:3 - error NG8002: Can't bind to 'nzLoading' since it isn't a known property of 'eo-ng-table'.
1. If 'eo-ng-table' is an Angular component and it has 'nzLoading' input, then verify that it is part of this module.
2. If 'eo-ng-table' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component.

66   [nzLoading]="nzLoading"
     ~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:67:3 - error NG8002: Can't bind to 'nzLoadingIndicator' since it isn't a known property of 'eo-ng-table'.
1. If 'eo-ng-table' is an Angular component and it has 'nzLoadingIndicator' input, then verify that it is part of this module.
2. If 'eo-ng-table' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component.

67   [nzLoadingIndicator]="nzLoadingIndicator"
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:68:3 - error NG8002: Can't bind to 'nzVirtualMaxItems' since it isn't a known property of 'eo-ng-table'.
1. If 'eo-ng-table' is an Angular component and it has 'nzVirtualMaxItems' input, then verify that it is part of this module.
2. If 'eo-ng-table' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component.

68   [nzVirtualMaxItems]="nzVirtualMaxItems"
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:76:5 - error NG8002: Can't bind to 'nzTooltipTitle' since it isn't a known property of 'span'.

76     [nzTooltipTitle]="item.tooltip || ''"
       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:77:5 - error NG8002: Can't bind to 'nzTooltipTitleContext' since it isn't a known property of 'span'.

77     [nzTooltipTitleContext]="item"
       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:78:5 - error NG8002: Can't bind to 'nzTooltipVisible' since it isn't a known property of 'span'.

78     [nzTooltipVisible]="item.tooltipVisible || false"
       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:79:5 - error NG8002: Can't bind to 'nzTooltipTrigger' since it isn't a known property of 'span'.

79     [nzTooltipTrigger]="item.tooltip ? item.tooltipTrigger || 'hover' : null"
       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:92:7 - error NG8002: Can't bind to 'nzTooltipTitle' since it isn't a known property of 'span'.

 92       [nzTooltipTitle]="
          ~~~~~~~~~~~~~~~~~~
 93         rowItem.json
    ~~~~~~~~~~~~~~~~~~~~
... 
103               (rowItem.keySuffix || '')
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
104       "
    ~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:105:7 - error NG8002: Can't bind to 'nzTooltipTitleContext' since it isn't a known property of 'span'.

105       [nzTooltipTitleContext]="{ rowItem: rowItem, item: item }"
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:106:7 - error NG8002: Can't bind to 'nzTooltipVisible' since it isn't a known property of 'span'.

106       [nzTooltipVisible]="rowItem.tooltipVisible || false"
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:107:7 - error NG8002: Can't bind to 'nzTooltipTrigger' since it isn't a known property of 'span'.

107       [nzTooltipTrigger]="rowItem.tooltipTrigger || 'hover'"
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:108:7 - error NG8002: Can't bind to 'nzTooltipOverlayClassName' since it isn't a known property of 'span'.

108       [nzTooltipOverlayClassName]="rowItem.json ? 'tooltip-json' : ''"
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.


Error: projects/eo-ng-apinto-table/src/lib/table/table.component.html:122:7 - error NG8002: Can't bind to 'copyText' since it isn't a known property of 'span'.

122       [copyText]="
          ~~~~~~~~~~~~
123         (rowItem.keyPrefix || '') +
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
... 
125         (rowItem.keySuffix || '')
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
126       "
    ~~~~~~~

  projects/eo-ng-apinto-table/src/lib/table/table.component.ts:9:16
    9   templateUrl: './table.component.html',
                     ~~~~~~~~~~~~~~~~~~~~~~~~
    Error occurs in the template of component TableComponent.



 ELIFECYCLE  Command failed with exit code 1.

Environment

  • APINTO Dashboard version (run apinto dashboard version): 3.3.0
  • Operating system (run uname -a): Linux VM-87-153 5.4.32-1-linux4-0001 #1 SMP Tue Jul 21 14:24:37 CST 2020 x86_64 x86_64 x86_64 GNU/Linux

按文件安裝了apinto跟apinto-dashboard,但是無法操作路由

Description

您好:
我嘗試在一台CentOS7的VM上建立apinto跟apinto-dashboard,然後由另外的電腦去連dashboard,可以進到後台介面,但無法創建路由,創建畫面只會看到3個欄位,是否有解決方式或可參考文件呢?

錯誤訊息內容如下:
如果config.yaml的apinto設定是http://127.0.0.1:9400時會得到錯誤訊息connection refused:
[2022-07-06 06:28:59] [DEBU] [dashboard]request:/routers/create
[2022-07-06 06:29:00] [DEBU] [dashboard]request api:GET /profession/routers/
[2022-07-06 06:29:00] [ERRO] [dashboard]do request:Get "http://127.0.0.1:9400/profession/router/drivers": dial tcp 127.0.0.1:9400: connect: connection refused

如果把127.0.0.1換成該VM對外IP時則會得到timeout:
[2022-07-06 06:32:11] [DEBU] [dashboard]request api:GET /profession/routers/
[2022-07-06 06:32:31] [DEBU] [dashboard]request:/routers/create
[2022-07-06 06:32:41] [ERRO] [dashboard]do request:Get "http://35.187.144.130:9400/profession/router/drivers": dial tcp 35.187.144.130:9400: i/o timeout

Environment

  • APINTO Dashboard version (last):
  • Operating system (Linux ffmpeg-nogpu-qa 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux):

help request: 源码启动问题

Description

运行时候提示如下信息,怎么解决,有没有源码编译部署说明
[2023-12-29 00:55:37] [FATA] need:[github.com/eolinker/apinto-dashboard/modules/cluster/cluster-store.cluster_store.IClusterNodeStore github.com/eolinker/apinto-dashboard/modules/notice/notice-store.notice_store.INoticeChannelStatStore github.com/eolinker/apinto-dashboard/modules/variable/variable-store.variable_store.IClusterVariableStore github.com/eolinker/apinto-dashboard/modules/group/group-store.group_store.ICommonGroupStore github.com/eolinker/apinto-dashboard/modules/plugin/plugin-store.plugin_store.IPluginHistoryStore github.com/eolinker/apinto-dashboard/modules/api/store.api_store.IApiHistoryStore github.com/eolinker/apinto-dashboard/modules/api/store.api_store.IAPIStore github.com/eolinker/apinto-dashboard/modules/cluster/cluster-store.cluster_store.IClusterCertificateStore github.com/eolinker/apinto-dashboard/modules/dynamic/dynamic-store.dynamic_store.IDynamicPublishHistoryStore github.com/eolinker/apinto-dashboard/modules/plugin_template/plugin-template-store.plugin_template_store.IPluginTemplateHistoryStore github.com/eolinker/apinto-dashboard/modules/plugin_template/plugin-template-store.plugin_template_store.IPluginTemplateStore github.com/eolinker/apinto-dashboard/modules/base/quote-store.quote_store.IQuoteStore github.com/eolinker/apinto-dashboard/modules/plugin/plugin-store.plugin_store.IClusterPluginRuntimeStore github.com/eolinker/apinto-dashboard/modules/module-plugin/store.store.IModulePluginEnableStore github.com/eolinker/apinto-dashboard/modules/plugin/plugin-store.plugin_store.IClusterPluginPublishHistoryStore github.com/eolinker/apinto-dashboard/modules/module-plugin/store.store.IPluginResources github.com/eolinker/apinto-dashboard/modules/variable/variable-store.variable_store.IVariableRuntimeStore github.com/eolinker/apinto-dashboard/modules/variable/variable-store.variable_store.IVariablePublishVersionStore github.com/eolinker/apinto-dashboard/modules/variable/variable-store.variable_store.IVariableHistoryStore github.com/eolinker/apinto-dashboard/modules/openapp/openapp-store.openapp_store.IExternalApplicationStore github.com/eolinker/apinto-dashboard/modules/application/application-store.application_store.IApplicationHistoryStore github.com/eolinker/apinto-dashboard/modules/cluster/cluster-store.cluster_store.IClusterStore github.com/eolinker/apinto-dashboard/modules/plugin_template/plugin-template-store.plugin_template_store.IPluginTemplateVersionStore github.com/eolinker/apinto-dashboard/modules/dynamic/dynamic-store.dynamic_store.IDynamicQuoteStore github.com/eolinker/apinto-dashboard/modules/api/store.api_store.IAPIVersionStore github.com/eolinker/apinto-dashboard/modules/plugin/plugin-store.plugin_store.IClusterPluginStore github.com/eolinker/apinto-dashboard/modules/application/application-store.application_store.IApplicationStatStore github.com/eolinker/apinto-dashboard/modules/namespace/namespace-store.namespace_store.INamespaceStore github.com/eolinker/apinto-dashboard/modules/plugin/plugin-store.plugin_store.IPluginStore github.com/eolinker/apinto-dashboard/modules/plugin/plugin-store.plugin_store.IClusterPluginPublishVersionStore github.com/eolinker/apinto-dashboard/modules/application/application-store.application_store.IApplicationStore github.com/eolinker/apinto-dashboard/modules/plugin_template/plugin-template-store.plugin_template_store.IPluginTemplateStatStore github.com/eolinker/apinto-dashboard/modules/application/application-store.application_store.IApplicationVersionStore github.com/eolinker/apinto-dashboard/modules/audit/audit-store.audit_store.IAuditLogStore github.com/eolinker/apinto-dashboard/modules/plugin_template/plugin-template-store.plugin_template_store.IPluginTemplatePublishHistoryStore github.com/eolinker/apinto-dashboard/modules/user/user-store.user_store.IUserInfoStore github.com/eolinker/apinto-dashboard/modules/cluster/cluster-store.cluster_store.IClusterRuntimeStore github.com/eolinker/apinto-dashboard/modules/module-plugin/store.store.IModulePluginStore github.com/eolinker/apinto-dashboard/modules/application/application-store.application_store.IApplicationAuthStore github.com/eolinker/apinto-dashboard/modules/remote_storage/store.store.IRemoteStorage github.com/eolinker/apinto-dashboard/modules/dynamic/dynamic-store.dynamic_store.IDynamicStore github.com/eolinker/apinto-dashboard/modules/api/store.api_store.IAPIStatStore github.com/eolinker/apinto-dashboard/modules/plugin/plugin-store.plugin_store.IClusterPluginHistoryStore github.com/eolinker/apinto-dashboard/modules/notice/notice-store.notice_store.INoticeChannelStore github.com/eolinker/apinto-dashboard/modules/dynamic/dynamic-store.dynamic_store.IDynamicPublishVersionStore github.com/eolinker/apinto-dashboard/modules/variable/variable-store.variable_store.IVariablePublishHistoryStore github.com/eolinker/apinto-dashboard/modules/api/store.api_store.IApiPublishHistoryStore github.com/eolinker/apinto-dashboard/modules/application/application-store.application_store.IAppPublishHistoryStore github.com/eolinker/apinto-dashboard/modules/cluster/cluster-store.cluster_store.IClusterHistoryStore github.com/eolinker/apinto-dashboard/modules/notice/notice-store.notice_store.INoticeChannelVersionStore github.com/eolinker/apinto-dashboard/modules/variable/variable-store.variable_store.IGlobalVariableStore]

Environment

  • APINTO Dashboard version (V3):

日志检索中的追踪日志不可用

Current Behavior

追踪日志不能实时获取数据,连接IP似乎是没有取真实地址。

Expected Behavior

No response

Error Logs

image

Steps to Reproduce

  1. 进入后台打开“日志检索”
  2. 在浏览器中F12打开开发工具,选择“Console”
  3. 在“日志详情” 点击 “节点日志”,并观察“Console”中日志

Environment

  • APINTO Dashboard version (run apinto dashboard version):apserver_v3.2.1
  • Operating system (run uname -a):Linux test 3.10.0-1160.62.1.el7.x86_64 #1 SMP Tue Apr 5 16:57:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

日志检索报错:node addr http://172.18.0.2:9400 can not be connected

Current Behavior

日志检索异常:系统管理->日志检索,报错:

node addr http://172.18.0.2:9400 can not be connected

控制台network请求的一个API:api/log/files?cluster=cluster_2e34f6a8_509c_482b_9dd3_0d49d1060db6&node=5a399d0b6b9644b78a19e6f636825474&namespace=default,响应如下:

{"code":-1,"msg":"node addr http://172.18.0.2:9400 can not be connected"}

Expected Behavior

1,希望能解答一下,关于网关和节点中涉及到相关的访问地址及之间的关联;
2,日志检索能正常使用,以及该问题是否跟1相关;

Error Logs

/var/lib/apinto/error*.log 几个文件中,都是空的。

Steps to Reproduce

安装方式

1,dashboard 安装:https://help.eolink.com/tutorial/Apinto/c-1406 中 docker-compose ,修改项:密码和redis_cluster . environment . HOST 为 本地内网IP:172.17.0.5
2,节点安装:https://help.eolink.com/tutorial/Apinto/c-1378,单节点,Docker方式,直接复制文档中的配置,暂无任何修改;

问题:

1, dashboard 添加集群时,录入的是:172.17.0.5:9400,检测成功,录入之后,页面返回的管理地址和服务地址,ip 分别变成了 172.18.0.2,这是为啥?
2,第一条的内网变更,对功能没有任何影响,上游API及访问测试,无论通过 172.17.0.5:8099172.18.0.2:8099都可以;
3,日志检索异常:系统管理->日志检索,报错:

node addr http://172.18.0.2:9400 can not be connected

控制台network请求的一个API:api/log/files?cluster=cluster_2e34f6a8_509c_482b_9dd3_0d49d1060db6&node=5a399d0b6b9644b78a19e6f636825474&namespace=default,响应如下:

{"code":-1,"msg":"node addr http://172.18.0.2:9400 can not be connected"}

Environment

  1. uname -a: Linux sls-tc-sh 5.4.119-19-0009.11 #1 SMP Wed Oct 5 18:41:07 CST 2022 x86_64 x86_64 x86_64 GNU/Linux
  2. dashboard version:昨天基于 官方文档docker-composer 安装的最新。

bug: Dont Work Dashboard In Docker

Current Behavior

Hello,
I have currently installed on a cloud server:

However, I encounter an error when trying to access the following route.: http://localhost:18080/login

image

The YAML file for deployment is as follows:

version: '3' services: mysql: image: mysql:5.7.34 privileged: true restart: always container_name: apinto_mysql hostname: apinto_mysql ports: - "33306:3306" environment: - MYSQL_ROOT_PASSWORD=123456 - MYSQL_DATABASE=apinto volumes: - /var/lib/apinto/mysql:/var/lib/mysql networks: - apinto apinto-dashboard: image: eolinker/apinto-dashboard container_name: apinto-dashboard privileged: true restart: always networks: - apinto ports: - "18080:8080" depends_on: - mysql - redis_cluster environment: - MYSQL_USER_NAME=root - MYSQL_PWD=123456 - MYSQL_IP=apinto_mysql - MYSQL_PORT=3306 #mysql端口 - MYSQL_DB="apinto" - ERROR_DIR=/apinto-dashboard/work/logs # 日志放置目录 - ERROR_FILE_NAME=error.log # 错误日志文件名 - ERROR_LOG_LEVEL=info # 错误日志等级,可选:panic,fatal,error,warning,info,debug,trace 不填或者非法则为info - ERROR_EXPIRE=7d # 错误日志过期时间,默认单位为天,d|天,h|小时, 不合法配置默认为7d - ERROR_PERIOD=day # 错误日志切割周期,仅支持day、hour - REDIS_ADDR=172.100.0.1:7201,172.100.0.1:7202,172.100.0.1:7203,172.100.0.1:7204,172.100.0.1:7205,172.100.0.1:7206 #Redis集群地址 多个用,隔开 - REDIS_PWD=123456 # Redis密码 volumes: - /var/log/apinto/apinto-dashboard/work:/apinto-dashboard/work #挂载log到主机目录 redis_cluster: container_name: redis_cluster image: eolinker/cluster-redis:6.2.7 hostname: redis_cluster privileged: true restart: always environment: - REDIS_PWD=123456 - PORT=7201 - HOST=172.18.21.251 volumes: - /var/lib/apinto/redis-cluster/data:/usr/local/cluster_redis/data network_mode: host networks: apinto: driver: bridge ipam: driver: default config: - subnet: 172.100.0.0/24

I can't find where I should configure the Apinto services like the IP addresses of the clusters. What could be the issue?

Expected Behavior

I would expect to see what is shown in the image, which I extracted from this repository.

image

Error Logs

No response

Steps to Reproduce

  1. Install apinto by command line
  2. Install apinto-dashboard by docker-compose

Environment

  • APINTO Dashboard version (run apinto dashboard version):
  • Operating system (run uname -a):

sqlite支持库修改建议

Description

目前使用的包为 github.com/mattn/go-sqlite3 不支持跨平台编译
建议替换成 modernc.org/sqlite
仅供参考

help request: docker-compose启动mysql登陆不上

Description

image

version: '3'
services:
  mysql:
    image: mysql:5.7.21
    privileged: true
    restart: always
    container_name: apinto_mysql
    hostname: apinto_mysql
    ports:
      - "33306:3306"
    environment:
      - MYSQL_ROOT_PASSWORD=123456
      - MYSQL_DATABASE=apinto
    volumes:
      - /var/lib/apinto/mysql:/var/lib/mysql
    networks:
      - apinto
  apinto-dashboard:
    image: eolinker/apinto-dashboard
    container_name: apinto-dashboard
    privileged: true
    restart: always
    networks:
      - apinto
    ports:
      - "18080:8080"
    depends_on:
      - mysql
      - redis_cluster
    environment:
      - MYSQL_USER_NAME=root
      - MYSQL_PWD=123456
      - MYSQL_IP=apinto_mysql
      - MYSQL_PORT=3306                 #mysql端口
      - MYSQL_DB="apinto"
      - ERROR_DIR=/apinto-dashboard/work/logs  # 日志放置目录
      - ERROR_FILE_NAME=error.log          # 错误日志文件名
      - ERROR_LOG_LEVEL=info               # 错误日志等级,可选:panic,fatal,error,warning,info,debug,trace 不填或者非法则为info
      - ERROR_EXPIRE=7d                    # 错误日志过期时间,默认单位为天,d|天,h|小时, 不合法配置默认为7d
      - ERROR_PERIOD=day                  # 错误日志切割周期,仅支持day、hour
      - REDIS_ADDR=172.100.0.1:7201,172.100.0.1:7202,172.100.0.1:7203,172.100.0.1:7204,172.100.0.1:7205,172.100.0.1:7206 #Redis集群地址 多个用,隔开
      - REDIS_PWD=123456                         # Redis密码
    volumes:
      - /var/log/apinto/apinto-dashboard/work:/apinto-dashboard/work   #挂载log到主机目录
  redis_cluster:
    container_name: redis_cluster
    image: eolinker/cluster-redis:6.2.7
    hostname: redis_cluster
    privileged: true
    restart: always
    environment:
      - REDIS_PWD=123456
      - PORT=7201
      - HOST=55.235.31.218
    volumes: 
      - /var/lib/apinto/redis-cluster/data:/usr/local/cluster_redis/data
    network_mode: host
networks:
  apinto:
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: 172.100.0.0/24

Environment

  • APINTO Dashboard version (run apinto dashboard version):
  • Operating system (run uname -a):

Developer Portal 功能

Description

请问 apinto-dashboard / apinto 是否支持 Developer Portal 功能?类似 Tyk Developer PortalKong Dev Portal 这种,允许第三方开发者自助注册 app 并申请 API 访问权限。

demo 里找了一圈没找到。

Environment

(not applied)

build报错,找不到tpl模板

Current Behavior

image
如图,build.sh里面这句话找不到模板文件,修改为:cp -a ${BasePath}/internal/template/tpl ${OUTPATH}/
可以正常打包

Expected Behavior

修订问题

Error Logs

No response

Steps to Reproduce

按照官方打包教程打包就会报错

Environment

main分支

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.