From 5ea923cda8516623d8c6ba01edd6f3801355cd97 Mon Sep 17 00:00:00 2001 From: Odboy Date: Sat, 1 Nov 2025 23:12:00 +0800 Subject: [PATCH] =?UTF-8?q?fix:=20=E4=BF=AE=E5=A4=8D=E8=A7=92=E8=89=B2?= =?UTF-8?q?=E6=8E=88=E6=9D=83=E7=88=B6=E5=AD=90=E8=81=94=E5=8A=A8?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- cutejava-front/package.json | 6 +- .../src/views/system/role/index.vue | 2 +- .../src/main/resources/logback.xml | 2 +- .../codestyle/alibaba/eclipse-codestyle.xml | 603 ----- .../docs/codestyle/default/idea-codestyle.xml | 7 - .../docs/codestyle/project/P3C_CodeStyle.xml | 380 --- cutejava/docs/codestyle/readme.md | 5 - .../dockerenv/minio/docker-compose-minio.yml | 24 - cutejava/docs/dockerenv/minio/run.sh | 2 - cutejava/docs/dockerenv/minio/stop.sh | 2 - .../mysql8/docker-compose-mysql8.yml | 21 - cutejava/docs/dockerenv/mysql8/mysql/my.cnf | 22 - cutejava/docs/dockerenv/mysql8/run.sh | 2 - cutejava/docs/dockerenv/mysql8/stop.sh | 2 - .../dockerenv/redis7/docker-compose-redis.yml | 14 - .../dockerenv/redis7/redis/config/redis.conf | 2277 ----------------- cutejava/docs/dockerenv/redis7/run.sh | 2 - cutejava/docs/dockerenv/redis7/stop.sh | 2 - cutejava/docs/help/@Validated常用.txt | 34 - cutejava/docs/help/Controller命名规范.md | 8 - cutejava/docs/help/IDEA换行调整.jpg | Bin 69216 -> 0 bytes cutejava/docs/help/Service方法中使用this.txt | 131 - cutejava/docs/help/license.template | 13 - cutejava/docs/help/应用迭代定义.txt | 1 - cutejava/docs/help/注意事项.md | 3 - cutejava/docs/help/缓存注解使用.txt | 27 - cutejava/docs/mysql/cutejava.sql | 2015 --------------- cutejava/docs/mysql/readme.md | 3 - .../docs/nginx/cutejava-api.odboy.cn.conf | 28 - cutejava/docs/nginx/cutejava.odboy.cn.conf | 31 - 30 files changed, 5 insertions(+), 5664 deletions(-) delete mode 100644 cutejava/docs/codestyle/alibaba/eclipse-codestyle.xml delete mode 100644 cutejava/docs/codestyle/default/idea-codestyle.xml delete mode 100644 cutejava/docs/codestyle/project/P3C_CodeStyle.xml delete mode 100644 cutejava/docs/codestyle/readme.md delete mode 100644 cutejava/docs/dockerenv/minio/docker-compose-minio.yml delete mode 100644 cutejava/docs/dockerenv/minio/run.sh delete mode 100644 cutejava/docs/dockerenv/minio/stop.sh delete mode 100644 cutejava/docs/dockerenv/mysql8/docker-compose-mysql8.yml delete mode 100644 cutejava/docs/dockerenv/mysql8/mysql/my.cnf delete mode 100644 cutejava/docs/dockerenv/mysql8/run.sh delete mode 100644 cutejava/docs/dockerenv/mysql8/stop.sh delete mode 100644 cutejava/docs/dockerenv/redis7/docker-compose-redis.yml delete mode 100644 cutejava/docs/dockerenv/redis7/redis/config/redis.conf delete mode 100644 cutejava/docs/dockerenv/redis7/run.sh delete mode 100644 cutejava/docs/dockerenv/redis7/stop.sh delete mode 100644 cutejava/docs/help/@Validated常用.txt delete mode 100644 cutejava/docs/help/Controller命名规范.md delete mode 100644 cutejava/docs/help/IDEA换行调整.jpg delete mode 100644 cutejava/docs/help/Service方法中使用this.txt delete mode 100644 cutejava/docs/help/license.template delete mode 100644 cutejava/docs/help/应用迭代定义.txt delete mode 100644 cutejava/docs/help/注意事项.md delete mode 100644 cutejava/docs/help/缓存注解使用.txt delete mode 100644 cutejava/docs/mysql/cutejava.sql delete mode 100644 cutejava/docs/mysql/readme.md delete mode 100644 cutejava/docs/nginx/cutejava-api.odboy.cn.conf delete mode 100644 cutejava/docs/nginx/cutejava.odboy.cn.conf diff --git a/cutejava-front/package.json b/cutejava-front/package.json index 01ec023d..706b3bee 100644 --- a/cutejava-front/package.json +++ b/cutejava-front/package.json @@ -5,11 +5,11 @@ "author": "Odboy", "license": "Apache-2.0", "scripts": { - "dev-win1": "vue-cli-service serve", - "dev-win2": "set NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve", + "dev": "vue-cli-service serve", + "dev-win": "set NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve", "dev-linux": "export NODE_OPTIONS=--openssl-legacy-provider && vue-cli-service serve", - "build:prod": "vue-cli-service build", "build:stage": "vue-cli-service build --mode staging", + "build:prod": "vue-cli-service build", "preview": "node build/index.js --preview", "lint": "eslint --ext .js,.vue src", "test:unit": "jest --clearCache && vue-cli-service test:unit", diff --git a/cutejava-front/src/views/system/role/index.vue b/cutejava-front/src/views/system/role/index.vue index 35748b23..13fc7c0b 100644 --- a/cutejava-front/src/views/system/role/index.vue +++ b/cutejava-front/src/views/system/role/index.vue @@ -138,7 +138,7 @@ :default-checked-keys="menuIds" :load="getMenuDatas" :props="defaultProps" - check-strictly + :check-strictly="true" accordion show-checkbox node-key="id" diff --git a/cutejava/cutejava-starter/src/main/resources/logback.xml b/cutejava/cutejava-starter/src/main/resources/logback.xml index ce4a46c1..c01496a8 100644 --- a/cutejava/cutejava-starter/src/main/resources/logback.xml +++ b/cutejava/cutejava-starter/src/main/resources/logback.xml @@ -2,7 +2,7 @@ CuteJava - + diff --git a/cutejava/docs/codestyle/alibaba/eclipse-codestyle.xml b/cutejava/docs/codestyle/alibaba/eclipse-codestyle.xml deleted file mode 100644 index 292838dd..00000000 --- a/cutejava/docs/codestyle/alibaba/eclipse-codestyle.xml +++ /dev/null @@ -1,603 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/cutejava/docs/codestyle/default/idea-codestyle.xml b/cutejava/docs/codestyle/default/idea-codestyle.xml deleted file mode 100644 index 3357d198..00000000 --- a/cutejava/docs/codestyle/default/idea-codestyle.xml +++ /dev/null @@ -1,7 +0,0 @@ - - \ No newline at end of file diff --git a/cutejava/docs/codestyle/project/P3C_CodeStyle.xml b/cutejava/docs/codestyle/project/P3C_CodeStyle.xml deleted file mode 100644 index 6604d452..00000000 --- a/cutejava/docs/codestyle/project/P3C_CodeStyle.xml +++ /dev/null @@ -1,380 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/cutejava/docs/codestyle/readme.md b/cutejava/docs/codestyle/readme.md deleted file mode 100644 index 609700de..00000000 --- a/cutejava/docs/codestyle/readme.md +++ /dev/null @@ -1,5 +0,0 @@ -Settings -> Editor -> Code Style -> Java -> Scheme(右侧小齿轮) -> Import Scheme -> - -- alibaba: Eclipse Xml Profile -- project: Eclipse Xml Profile，当前项目风格 -- default: IDEA Xml Profile，默认的风格 diff --git a/cutejava/docs/dockerenv/minio/docker-compose-minio.yml b/cutejava/docs/dockerenv/minio/docker-compose-minio.yml deleted file mode 100644 index 9af223b5..00000000 --- a/cutejava/docs/dockerenv/minio/docker-compose-minio.yml +++ /dev/null @@ -1,24 +0,0 @@ -services: - minio: - # MinIO 社区版在 2025 年 5 月 24 日的更新中移除了 Web 管理控制台功能 - image: minio/minio:RELEASE.2025-04-22T22-12-26Z # 原镜像`minio/minio:latest` - restart: unless-stopped # 指定容器退出后的重启策略为始终重启，但是不考虑在Docker守护进程启动时就已经停止了的容器 - volumes: # 数据卷挂载路径设置,将本机目录映射到容器目录 - - "./minio/data:/data" - - "./minio/minio:/minio" - - "./minio/config:/root/.minio" - environment: # 设置环境变量,相当于docker run命令中的-e - TZ: Asia/Shanghai - LANG: en_US.UTF-8 - #MINIO_PROMETHEUS_AUTH_TYPE: "public" - MINIO_ACCESS_KEY: "root" # 登录账号 - MINIO_SECRET_KEY: "kd123456" # 登录密码 - command: server /data --console-address ":9001" - logging: - driver: "json-file" - options: - max-size: "50m" - ports: # 映射端口 - - "9000:9000" # 文件上传&预览端口 - - "9001:9001" # 控制台访问端口 - diff --git a/cutejava/docs/dockerenv/minio/run.sh b/cutejava/docs/dockerenv/minio/run.sh deleted file mode 100644 index e0a9925c..00000000 --- a/cutejava/docs/dockerenv/minio/run.sh +++ /dev/null @@ -1,2 +0,0 @@ -#!/bin/bash -docker-compose -f docker-compose-minio.yml -p minio20250422 up -d diff --git a/cutejava/docs/dockerenv/minio/stop.sh b/cutejava/docs/dockerenv/minio/stop.sh deleted file mode 100644 index cc69e037..00000000 --- a/cutejava/docs/dockerenv/minio/stop.sh +++ /dev/null @@ -1,2 +0,0 @@ -#!/bin/bash -docker-compose -f docker-compose-minio.yml -p minio20250422 down \ No newline at end of file diff --git a/cutejava/docs/dockerenv/mysql8/docker-compose-mysql8.yml b/cutejava/docs/dockerenv/mysql8/docker-compose-mysql8.yml deleted file mode 100644 index ddeeb0c1..00000000 --- a/cutejava/docs/dockerenv/mysql8/docker-compose-mysql8.yml +++ /dev/null @@ -1,21 +0,0 @@ -# 可参考： https://hub.docker.com/_/mysql -version: '3' -services: - mysql: - image: registry.cn-hangzhou.aliyuncs.com/zhengqing/mysql:8.0 # 原镜像`mysql:8.0` - container_name: mysql8 # 容器名为'mysql8' - restart: unless-stopped # 指定容器退出后的重启策略为始终重启，但是不考虑在Docker守护进程启动时就已经停止了的容器 - volumes: # 数据卷挂载路径设置,将本机目录映射到容器目录 - - "./mysql/my.cnf:/etc/mysql/my.cnf" - - "./mysql/data:/var/lib/mysql" - # - "./mysql/conf.d:/etc/mysql/conf.d" - - "./mysql/mysql-files:/var/lib/mysql-files" - environment: # 设置环境变量,相当于docker run命令中的-e - TZ: Asia/Shanghai - LANG: en_US.UTF-8 - MYSQL_ROOT_PASSWORD: kd123456 # 设置root用户密码 - MYSQL_DATABASE: demo # 初始化的数据库名称 - privileged: true - user: root - ports: # 映射端口 - - "23306:3306" diff --git a/cutejava/docs/dockerenv/mysql8/mysql/my.cnf b/cutejava/docs/dockerenv/mysql8/mysql/my.cnf deleted file mode 100644 index 24b63765..00000000 --- a/cutejava/docs/dockerenv/mysql8/mysql/my.cnf +++ /dev/null @@ -1,22 +0,0 @@ -# 服务端参数配置 -[mysqld] -user=mysql # MySQL启动用户 -default-storage-engine=INNODB # 创建新表时将使用的默认存储引擎 -character-set-server=utf8mb4 # 设置mysql服务端默认字符集 -collation-server=utf8mb4_0900_ai_ci # 数据库字符集对应一些排序等规则，注意要和character-set-server对应 -default-authentication-plugin=mysql_native_password - -max_connections=1000 # 允许最大连接数 -max_connect_errors=100 # 最大错误连接数 - -#sql_mode=ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION -sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION - -lower_case_table_names=1 # 表名不区分大小写 - -[mysql] -default-character-set=utf8mb4 - - -[client] -default-character-set=utf8mb4 # 设置mysql客户端默认字符集 diff --git a/cutejava/docs/dockerenv/mysql8/run.sh b/cutejava/docs/dockerenv/mysql8/run.sh deleted file mode 100644 index 5a4ca3ce..00000000 --- a/cutejava/docs/dockerenv/mysql8/run.sh +++ /dev/null @@ -1,2 +0,0 @@ -#!/bin/bash -docker-compose -f docker-compose-mysql8.yml -p mysql8 up -d diff --git a/cutejava/docs/dockerenv/mysql8/stop.sh b/cutejava/docs/dockerenv/mysql8/stop.sh deleted file mode 100644 index 7501b84b..00000000 --- a/cutejava/docs/dockerenv/mysql8/stop.sh +++ /dev/null @@ -1,2 +0,0 @@ -#!/bin/bash -docker-compose -f docker-compose-mysql8.yml -p mysql8 down \ No newline at end of file diff --git a/cutejava/docs/dockerenv/redis7/docker-compose-redis.yml b/cutejava/docs/dockerenv/redis7/docker-compose-redis.yml deleted file mode 100644 index 0b4a5e4a..00000000 --- a/cutejava/docs/dockerenv/redis7/docker-compose-redis.yml +++ /dev/null @@ -1,14 +0,0 @@ -version: '3' -services: - redis: - image: registry.cn-hangzhou.aliyuncs.com/zhengqing/redis:7.0.5 # 镜像'redis:7.0.5' - restart: unless-stopped # 指定容器退出后的重启策略为始终重启，但是不考虑在Docker守护进程启动时就已经停止了的容器 - command: redis-server /etc/redis/redis.conf # 启动redis服务并添加密码为：123456,默认不开启redis-aof方式持久化配置 - environment: # 设置环境变量,相当于docker run命令中的-e - TZ: Asia/Shanghai - LANG: en_US.UTF-8 - volumes: # 数据卷挂载路径设置,将本机目录映射到容器目录 - - "./redis/data:/data" - - "./redis/config/redis.conf:/etc/redis/redis.conf" # `redis.conf`文件内容`http://download.redis.io/redis-stable/redis.conf` - ports: # 映射端口 - - "26379:6379" diff --git a/cutejava/docs/dockerenv/redis7/redis/config/redis.conf b/cutejava/docs/dockerenv/redis7/redis/config/redis.conf deleted file mode 100644 index 94eccda1..00000000 --- a/cutejava/docs/dockerenv/redis7/redis/config/redis.conf +++ /dev/null @@ -1,2277 +0,0 @@ -# Redis configuration file example. -# -# Note that in order to read the configuration file, Redis must be -# started with the file path as first argument: -# -# ./redis-server /path/to/redis.conf - -# Note on units: when memory size is needed, it is possible to specify -# it in the usual form of 1k 5GB 4M and so forth: -# -# 1k => 1000 bytes -# 1kb => 1024 bytes -# 1m => 1000000 bytes -# 1mb => 1024*1024 bytes -# 1g => 1000000000 bytes -# 1gb => 1024*1024*1024 bytes -# -# units are case insensitive so 1GB 1Gb 1gB are all the same. - -################################## INCLUDES ################################### - -# Include one or more other config files here. This is useful if you -# have a standard template that goes to all Redis servers but also need -# to customize a few per-server settings. Include files can include -# other files, so use this wisely. -# -# Note that option "include" won't be rewritten by command "CONFIG REWRITE" -# from admin or Redis Sentinel. Since Redis always uses the last processed -# line as value of a configuration directive, you'd better put includes -# at the beginning of this file to avoid overwriting config change at runtime. -# -# If instead you are interested in using includes to override configuration -# options, it is better to use include as the last line. -# -# Included paths may contain wildcards. All files matching the wildcards will -# be included in alphabetical order. -# Note that if an include path contains a wildcards but no files match it when -# the server is started, the include statement will be ignored and no error will -# be emitted. It is safe, therefore, to include wildcard files from empty -# directories. -# -# include /path/to/local.conf -# include /path/to/other.conf -# include /path/to/fragments/*.conf -# - -################################## MODULES ##################################### - -# Load modules at startup. If the server is not able to load modules -# it will abort. It is possible to use multiple loadmodule directives. -# -# loadmodule /path/to/my_module.so -# loadmodule /path/to/other_module.so - -################################## NETWORK ##################################### - -# By default, if no "bind" configuration directive is specified, Redis listens -# for connections from all available network interfaces on the host machine. -# It is possible to listen to just one or multiple selected interfaces using -# the "bind" configuration directive, followed by one or more IP addresses. -# Each address can be prefixed by "-", which means that redis will not fail to -# start if the address is not available. Being not available only refers to -# addresses that does not correspond to any network interface. Addresses that -# are already in use will always fail, and unsupported protocols will always BE -# silently skipped. -# -# Examples: -# -# bind 192.168.1.100 10.0.0.1 # listens on two specific IPv4 addresses -# bind 127.0.0.1 ::1 # listens on loopback IPv4 and IPv6 -# bind * -::* # like the default, all available interfaces -# -# ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the -# internet, binding to all the interfaces is dangerous and will expose the -# instance to everybody on the internet. So by default we uncomment the -# following bind directive, that will force Redis to listen only on the -# IPv4 and IPv6 (if available) loopback interface addresses (this means Redis -# will only be able to accept client connections from the same host that it is -# running on). -# -# IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES -# COMMENT OUT THE FOLLOWING LINE. -# -# You will also need to set a password unless you explicitly disable protected -# mode. -# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -# 注释允许外部访问redis -# bind 127.0.0.1 -::1 - -# By default, outgoing connections (from replica to master, from Sentinel to -# instances, cluster bus, etc.) are not bound to a specific local address. In -# most cases, this means the operating system will handle that based on routing -# and the interface through which the connection goes out. -# -# Using bind-source-addr it is possible to configure a specific address to bind -# to, which may also affect how the connection gets routed. -# -# Example: -# -# bind-source-addr 10.0.0.1 - -# Protected mode is a layer of security protection, in order to avoid that -# Redis instances left open on the internet are accessed and exploited. -# -# When protected mode is on and the default user has no password, the server -# only accepts local connections from the IPv4 address (127.0.0.1), IPv6 address -# (::1) or Unix domain sockets. -# -# By default protected mode is enabled. You should disable it only if -# you are sure you want clients from other hosts to connect to Redis -# even if no authentication is configured. -protected-mode yes - -# Redis uses default hardened security configuration directives to reduce the -# attack surface on innocent users. Therefore, several sensitive configuration -# directives are immutable, and some potentially-dangerous commands are blocked. -# -# Configuration directives that control files that Redis writes to (e.g., 'dir' -# and 'dbfilename') and that aren't usually modified during runtime -# are protected by making them immutable. -# -# Commands that can increase the attack surface of Redis and that aren't usually -# called by users are blocked by default. -# -# These can be exposed to either all connections or just local ones by setting -# each of the configs listed below to either of these values: -# -# no - Block for any connection (remain immutable) -# yes - Allow for any connection (no protection) -# local - Allow only for local connections. Ones originating from the -# IPv4 address (127.0.0.1), IPv6 address (::1) or Unix domain sockets. -# -# enable-protected-configs no -# enable-debug-command no -# enable-module-command no - -# Accept connections on the specified port, default is 6379 (IANA #815344). -# If port 0 is specified Redis will not listen on a TCP socket. -port 6379 - -# TCP listen() backlog. -# -# In high requests-per-second environments you need a high backlog in order -# to avoid slow clients connection issues. Note that the Linux kernel -# will silently truncate it to the value of /proc/sys/net/core/somaxconn so -# make sure to raise both the value of somaxconn and tcp_max_syn_backlog -# in order to get the desired effect. -tcp-backlog 511 - -# Unix socket. -# -# Specify the path for the Unix socket that will be used to listen for -# incoming connections. There is no default, so Redis will not listen -# on a unix socket when not specified. -# -# unixsocket /run/redis.sock -# unixsocketperm 700 - -# Close the connection after a client is idle for N seconds (0 to disable) -timeout 0 - -# TCP keepalive. -# -# If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence -# of communication. This is useful for two reasons: -# -# 1) Detect dead peers. -# 2) Force network equipment in the middle to consider the connection to be -# alive. -# -# On Linux, the specified value (in seconds) is the period used to send ACKs. -# Note that to close the connection the double of the time is needed. -# On other kernels the period depends on the kernel configuration. -# -# A reasonable value for this option is 300 seconds, which is the new -# Redis default starting with Redis 3.2.1. -tcp-keepalive 300 - -# Apply OS-specific mechanism to mark the listening socket with the specified -# ID, to support advanced routing and filtering capabilities. -# -# On Linux, the ID represents a connection mark. -# On FreeBSD, the ID represents a socket cookie ID. -# On OpenBSD, the ID represents a route table ID. -# -# The default value is 0, which implies no marking is required. -# socket-mark-id 0 - -################################# TLS/SSL ##################################### - -# By default, TLS/SSL is disabled. To enable it, the "tls-port" configuration -# directive can be used to define TLS-listening ports. To enable TLS on the -# default port, use: -# -# port 0 -# tls-port 6379 - -# Configure a X.509 certificate and private key to use for authenticating the -# server to connected clients, masters or cluster peers. These files should be -# PEM formatted. -# -# tls-cert-file redis.crt -# tls-key-file redis.key -# -# If the key file is encrypted using a passphrase, it can be included here -# as well. -# -# tls-key-file-pass secret - -# Normally Redis uses the same certificate for both server functions (accepting -# connections) and client functions (replicating from a master, establishing -# cluster bus connections, etc.). -# -# Sometimes certificates are issued with attributes that designate them as -# client-only or server-only certificates. In that case it may be desired to use -# different certificates for incoming (server) and outgoing (client) -# connections. To do that, use the following directives: -# -# tls-client-cert-file client.crt -# tls-client-key-file client.key -# -# If the key file is encrypted using a passphrase, it can be included here -# as well. -# -# tls-client-key-file-pass secret - -# Configure a DH parameters file to enable Diffie-Hellman (DH) key exchange, -# required by older versions of OpenSSL (<3.0). Newer versions do not require -# this configuration and recommend against it. -# -# tls-dh-params-file redis.dh - -# Configure a CA certificate(s) bundle or directory to authenticate TLS/SSL -# clients and peers. Redis requires an explicit configuration of at least one -# of these, and will not implicitly use the system wide configuration. -# -# tls-ca-cert-file ca.crt -# tls-ca-cert-dir /etc/ssl/certs - -# By default, clients (including replica servers) on a TLS port are required -# to authenticate using valid client side certificates. -# -# If "no" is specified, client certificates are not required and not accepted. -# If "optional" is specified, client certificates are accepted and must be -# valid if provided, but are not required. -# -# tls-auth-clients no -# tls-auth-clients optional - -# By default, a Redis replica does not attempt to establish a TLS connection -# with its master. -# -# Use the following directive to enable TLS on replication links. -# -# tls-replication yes - -# By default, the Redis Cluster bus uses a plain TCP connection. To enable -# TLS for the bus protocol, use the following directive: -# -# tls-cluster yes - -# By default, only TLSv1.2 and TLSv1.3 are enabled and it is highly recommended -# that older formally deprecated versions are kept disabled to reduce the attack surface. -# You can explicitly specify TLS versions to support. -# Allowed values are case insensitive and include "TLSv1", "TLSv1.1", "TLSv1.2", -# "TLSv1.3" (OpenSSL >= 1.1.1) or any combination. -# To enable only TLSv1.2 and TLSv1.3, use: -# -# tls-protocols "TLSv1.2 TLSv1.3" - -# Configure allowed ciphers. See the ciphers(1ssl) manpage for more information -# about the syntax of this string. -# -# Note: this configuration applies only to <= TLSv1.2. -# -# tls-ciphers DEFAULT:!MEDIUM - -# Configure allowed TLSv1.3 ciphersuites. See the ciphers(1ssl) manpage for more -# information about the syntax of this string, and specifically for TLSv1.3 -# ciphersuites. -# -# tls-ciphersuites TLS_CHACHA20_POLY1305_SHA256 - -# When choosing a cipher, use the server's preference instead of the client -# preference. By default, the server follows the client's preference. -# -# tls-prefer-server-ciphers yes - -# By default, TLS session caching is enabled to allow faster and less expensive -# reconnections by clients that support it. Use the following directive to disable -# caching. -# -# tls-session-caching no - -# Change the default number of TLS sessions cached. A zero value sets the cache -# to unlimited size. The default size is 20480. -# -# tls-session-cache-size 5000 - -# Change the default timeout of cached TLS sessions. The default timeout is 300 -# seconds. -# -# tls-session-cache-timeout 60 - -################################# GENERAL ##################################### - -# By default Redis does not run as a daemon. Use 'yes' if you need it. -# Note that Redis will write a pid file in /var/run/redis.pid when daemonized. -# When Redis is supervised by upstart or systemd, this parameter has no impact. -daemonize no - -# If you run Redis from upstart or systemd, Redis can interact with your -# supervision tree. Options: -# supervised no - no supervision interaction -# supervised upstart - signal upstart by putting Redis into SIGSTOP mode -# requires "expect stop" in your upstart job config -# supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET -# on startup, and updating Redis status on a regular -# basis. -# supervised auto - detect upstart or systemd method based on -# UPSTART_JOB or NOTIFY_SOCKET environment variables -# Note: these supervision methods only signal "process is ready." -# They do not enable continuous pings back to your supervisor. -# -# The default is "no". To run under upstart/systemd, you can simply uncomment -# the line below: -# -# supervised auto - -# If a pid file is specified, Redis writes it where specified at startup -# and removes it at exit. -# -# When the server runs non daemonized, no pid file is created if none is -# specified in the configuration. When the server is daemonized, the pid file -# is used even if not specified, defaulting to "/var/run/redis.pid". -# -# Creating a pid file is best effort: if Redis is not able to create it -# nothing bad happens, the server will start and run normally. -# -# Note that on modern Linux systems "/run/redis.pid" is more conforming -# and should be used instead. -pidfile /var/run/redis_6379.pid - -# Specify the server verbosity level. -# This can be one of: -# debug (a lot of information, useful for development/testing) -# verbose (many rarely useful info, but not a mess like the debug level) -# notice (moderately verbose, what you want in production probably) -# warning (only very important / critical messages are logged) -loglevel notice - -# Specify the log file name. Also the empty string can be used to force -# Redis to log on the standard output. Note that if you use standard -# output for logging but daemonize, logs will be sent to /dev/null -logfile "" - -# To enable logging to the system logger, just set 'syslog-enabled' to yes, -# and optionally update the other syslog parameters to suit your needs. -# syslog-enabled no - -# Specify the syslog identity. -# syslog-ident redis - -# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7. -# syslog-facility local0 - -# To disable the built in crash log, which will possibly produce cleaner core -# dumps when they are needed, uncomment the following: -# -# crash-log-enabled no - -# To disable the fast memory check that's run as part of the crash log, which -# will possibly let redis terminate sooner, uncomment the following: -# -# crash-memcheck-enabled no - -# Set the number of databases. The default database is DB 0, you can select -# a different one on a per-connection basis using SELECT where -# dbid is a number between 0 and 'databases'-1 -databases 10 - -# By default Redis shows an ASCII art logo only when started to log to the -# standard output and if the standard output is a TTY and syslog logging is -# disabled. Basically this means that normally a logo is displayed only in -# interactive sessions. -# -# However it is possible to force the pre-4.0 behavior and always show a -# ASCII art logo in startup logs by setting the following option to yes. -always-show-logo no - -# By default, Redis modifies the process title (as seen in 'top' and 'ps') to -# provide some runtime information. It is possible to disable this and leave -# the process name as executed by setting the following to no. -set-proc-title yes - -# When changing the process title, Redis uses the following template to construct -# the modified title. -# -# Template variables are specified in curly brackets. The following variables are -# supported: -# -# {title} Name of process as executed if parent, or type of child process. -# {listen-addr} Bind address or '*' followed by TCP or TLS port listening on, or -# Unix socket if only that's available. -# {server-mode} Special mode, i.e. "[sentinel]" or "[cluster]". -# {port} TCP port listening on, or 0. -# {tls-port} TLS port listening on, or 0. -# {unixsocket} Unix domain socket listening on, or "". -# {config-file} Name of configuration file used. -# -proc-title-template "{title} {listen-addr} {server-mode}" - -################################ SNAPSHOTTING ################################ - -# Save the DB to disk. -# -# save [ ...] -# -# Redis will save the DB if the given number of seconds elapsed and it -# surpassed the given number of write operations against the DB. -# -# Snapshotting can be completely disabled with a single empty string argument -# as in following example: -# -# save "" -# -# Unless specified otherwise, by default Redis will save the DB: -# * After 3600 seconds (an hour) if at least 1 change was performed -# * After 300 seconds (5 minutes) if at least 100 changes were performed -# * After 60 seconds if at least 10000 changes were performed -# -# You can set these explicitly by uncommenting the following line. -# -# save 3600 1 300 100 60 10000 - -# By default Redis will stop accepting writes if RDB snapshots are enabled -# (at least one save point) and the latest background save failed. -# This will make the user aware (in a hard way) that data is not persisting -# on disk properly, otherwise chances are that no one will notice and some -# disaster will happen. -# -# If the background saving process will start working again Redis will -# automatically allow writes again. -# -# However if you have setup your proper monitoring of the Redis server -# and persistence, you may want to disable this feature so that Redis will -# continue to work as usual even if there are problems with disk, -# permissions, and so forth. -stop-writes-on-bgsave-error yes - -# Compress string objects using LZF when dump .rdb databases? -# By default compression is enabled as it's almost always a win. -# If you want to save some CPU in the saving child set it to 'no' but -# the dataset will likely be bigger if you have compressible values or keys. -rdbcompression yes - -# Since version 5 of RDB a CRC64 checksum is placed at the end of the file. -# This makes the format more resistant to corruption but there is a performance -# hit to pay (around 10%) when saving and loading RDB files, so you can disable it -# for maximum performances. -# -# RDB files created with checksum disabled have a checksum of zero that will -# tell the loading code to skip the check. -rdbchecksum yes - -# Enables or disables full sanitization checks for ziplist and listpack etc when -# loading an RDB or RESTORE payload. This reduces the chances of a assertion or -# crash later on while processing commands. -# Options: -# no - Never perform full sanitization -# yes - Always perform full sanitization -# clients - Perform full sanitization only for user connections. -# Excludes: RDB files, RESTORE commands received from the master -# connection, and client connections which have the -# skip-sanitize-payload ACL flag. -# The default should be 'clients' but since it currently affects cluster -# resharding via MIGRATE, it is temporarily set to 'no' by default. -# -# sanitize-dump-payload no - -# The filename where to dump the DB -dbfilename dump.rdb - -# Remove RDB files used by replication in instances without persistence -# enabled. By default this option is disabled, however there are environments -# where for regulations or other security concerns, RDB files persisted on -# disk by masters in order to feed replicas, or stored on disk by replicas -# in order to load them for the initial synchronization, should be deleted -# ASAP. Note that this option ONLY WORKS in instances that have both AOF -# and RDB persistence disabled, otherwise is completely ignored. -# -# An alternative (and sometimes better) way to obtain the same effect is -# to use diskless replication on both master and replicas instances. However -# in the case of replicas, diskless is not always an option. -rdb-del-sync-files no - -# The working directory. -# -# The DB will be written inside this directory, with the filename specified -# above using the 'dbfilename' configuration directive. -# -# The Append Only File will also be created inside this directory. -# -# Note that you must specify a directory here, not a file name. -dir ./ - -################################# REPLICATION ################################# - -# Master-Replica replication. Use replicaof to make a Redis instance a copy of -# another Redis server. A few things to understand ASAP about Redis replication. -# -# +------------------+ +---------------+ -# | Master | ---> | Replica | -# | (receive writes) | | (exact copy) | -# +------------------+ +---------------+ -# -# 1) Redis replication is asynchronous, but you can configure a master to -# stop accepting writes if it appears to be not connected with at least -# a given number of replicas. -# 2) Redis replicas are able to perform a partial resynchronization with the -# master if the replication link is lost for a relatively small amount of -# time. You may want to configure the replication backlog size (see the next -# sections of this file) with a sensible value depending on your needs. -# 3) Replication is automatic and does not need user intervention. After a -# network partition replicas automatically try to reconnect to masters -# and resynchronize with them. -# -# replicaof - -# If the master is password protected (using the "requirepass" configuration -# directive below) it is possible to tell the replica to authenticate before -# starting the replication synchronization process, otherwise the master will -# refuse the replica request. -# -# masterauth -# -# However this is not enough if you are using Redis ACLs (for Redis version -# 6 or greater), and the default user is not capable of running the PSYNC -# command and/or other commands needed for replication. In this case it's -# better to configure a special user to use with replication, and specify the -# masteruser configuration as such: -# -# masteruser -# -# When masteruser is specified, the replica will authenticate against its -# master using the new AUTH form: AUTH . - -# When a replica loses its connection with the master, or when the replication -# is still in progress, the replica can act in two different ways: -# -# 1) if replica-serve-stale-data is set to 'yes' (the default) the replica will -# still reply to client requests, possibly with out of date data, or the -# data set may just be empty if this is the first synchronization. -# -# 2) If replica-serve-stale-data is set to 'no' the replica will reply with error -# "MASTERDOWN Link with MASTER is down and replica-serve-stale-data is set to 'no'" -# to all data access commands, excluding commands such as: -# INFO, REPLICAOF, AUTH, SHUTDOWN, REPLCONF, ROLE, CONFIG, SUBSCRIBE, -# UNSUBSCRIBE, PSUBSCRIBE, PUNSUBSCRIBE, PUBLISH, PUBSUB, COMMAND, POST, -# HOST and LATENCY. -# -replica-serve-stale-data yes - -# You can configure a replica instance to accept writes or not. Writing against -# a replica instance may be useful to store some ephemeral data (because data -# written on a replica will be easily deleted after resync with the master) but -# may also cause problems if clients are writing to it because of a -# misconfiguration. -# -# Since Redis 2.6 by default replicas are read-only. -# -# Note: read only replicas are not designed to be exposed to untrusted clients -# on the internet. It's just a protection layer against misuse of the instance. -# Still a read only replica exports by default all the administrative commands -# such as CONFIG, DEBUG, and so forth. To a limited extent you can improve -# security of read only replicas using 'rename-command' to shadow all the -# administrative / dangerous commands. -replica-read-only yes - -# Replication SYNC strategy: disk or socket. -# -# New replicas and reconnecting replicas that are not able to continue the -# replication process just receiving differences, need to do what is called a -# "full synchronization". An RDB file is transmitted from the master to the -# replicas. -# -# The transmission can happen in two different ways: -# -# 1) Disk-backed: The Redis master creates a new process that writes the RDB -# file on disk. Later the file is transferred by the parent -# process to the replicas incrementally. -# 2) Diskless: The Redis master creates a new process that directly writes the -# RDB file to replica sockets, without touching the disk at all. -# -# With disk-backed replication, while the RDB file is generated, more replicas -# can be queued and served with the RDB file as soon as the current child -# producing the RDB file finishes its work. With diskless replication instead -# once the transfer starts, new replicas arriving will be queued and a new -# transfer will start when the current one terminates. -# -# When diskless replication is used, the master waits a configurable amount of -# time (in seconds) before starting the transfer in the hope that multiple -# replicas will arrive and the transfer can be parallelized. -# -# With slow disks and fast (large bandwidth) networks, diskless replication -# works better. -repl-diskless-sync yes - -# When diskless replication is enabled, it is possible to configure the delay -# the server waits in order to spawn the child that transfers the RDB via socket -# to the replicas. -# -# This is important since once the transfer starts, it is not possible to serve -# new replicas arriving, that will be queued for the next RDB transfer, so the -# server waits a delay in order to let more replicas arrive. -# -# The delay is specified in seconds, and by default is 5 seconds. To disable -# it entirely just set it to 0 seconds and the transfer will start ASAP. -repl-diskless-sync-delay 5 - -# When diskless replication is enabled with a delay, it is possible to let -# the replication start before the maximum delay is reached if the maximum -# number of replicas expected have connected. Default of 0 means that the -# maximum is not defined and Redis will wait the full delay. -repl-diskless-sync-max-replicas 0 - -# ----------------------------------------------------------------------------- -# WARNING: RDB diskless load is experimental. Since in this setup the replica -# does not immediately store an RDB on disk, it may cause data loss during -# failovers. RDB diskless load + Redis modules not handling I/O reads may also -# cause Redis to abort in case of I/O errors during the initial synchronization -# stage with the master. Use only if you know what you are doing. -# ----------------------------------------------------------------------------- -# -# Replica can load the RDB it reads from the replication link directly from the -# socket, or store the RDB to a file and read that file after it was completely -# received from the master. -# -# In many cases the disk is slower than the network, and storing and loading -# the RDB file may increase replication time (and even increase the master's -# Copy on Write memory and replica buffers). -# However, parsing the RDB file directly from the socket may mean that we have -# to flush the contents of the current database before the full rdb was -# received. For this reason we have the following options: -# -# "disabled" - Don't use diskless load (store the rdb file to the disk first) -# "on-empty-db" - Use diskless load only when it is completely safe. -# "swapdb" - Keep current db contents in RAM while parsing the data directly -# from the socket. Replicas in this mode can keep serving current -# data set while replication is in progress, except for cases where -# they can't recognize master as having a data set from same -# replication history. -# Note that this requires sufficient memory, if you don't have it, -# you risk an OOM kill. -repl-diskless-load disabled - -# Master send PINGs to its replicas in a predefined interval. It's possible to -# change this interval with the repl_ping_replica_period option. The default -# value is 10 seconds. -# -# repl-ping-replica-period 10 - -# The following option sets the replication timeout for: -# -# 1) Bulk transfer I/O during SYNC, from the point of view of replica. -# 2) Master timeout from the point of view of replicas (data, pings). -# 3) Replica timeout from the point of view of masters (REPLCONF ACK pings). -# -# It is important to make sure that this value is greater than the value -# specified for repl-ping-replica-period otherwise a timeout will be detected -# every time there is low traffic between the master and the replica. The default -# value is 60 seconds. -# -# repl-timeout 60 - -# Disable TCP_NODELAY on the replica socket after SYNC? -# -# If you select "yes" Redis will use a smaller number of TCP packets and -# less bandwidth to send data to replicas. But this can add a delay for -# the data to appear on the replica side, up to 40 milliseconds with -# Linux kernels using a default configuration. -# -# If you select "no" the delay for data to appear on the replica side will -# be reduced but more bandwidth will be used for replication. -# -# By default we optimize for low latency, but in very high traffic conditions -# or when the master and replicas are many hops away, turning this to "yes" may -# be a good idea. -repl-disable-tcp-nodelay no - -# Set the replication backlog size. The backlog is a buffer that accumulates -# replica data when replicas are disconnected for some time, so that when a -# replica wants to reconnect again, often a full resync is not needed, but a -# partial resync is enough, just passing the portion of data the replica -# missed while disconnected. -# -# The bigger the replication backlog, the longer the replica can endure the -# disconnect and later be able to perform a partial resynchronization. -# -# The backlog is only allocated if there is at least one replica connected. -# -# repl-backlog-size 1mb - -# After a master has no connected replicas for some time, the backlog will be -# freed. The following option configures the amount of seconds that need to -# elapse, starting from the time the last replica disconnected, for the backlog -# buffer to be freed. -# -# Note that replicas never free the backlog for timeout, since they may be -# promoted to masters later, and should be able to correctly "partially -# resynchronize" with other replicas: hence they should always accumulate backlog. -# -# A value of 0 means to never release the backlog. -# -# repl-backlog-ttl 3600 - -# The replica priority is an integer number published by Redis in the INFO -# output. It is used by Redis Sentinel in order to select a replica to promote -# into a master if the master is no longer working correctly. -# -# A replica with a low priority number is considered better for promotion, so -# for instance if there are three replicas with priority 10, 100, 25 Sentinel -# will pick the one with priority 10, that is the lowest. -# -# However a special priority of 0 marks the replica as not able to perform the -# role of master, so a replica with priority of 0 will never be selected by -# Redis Sentinel for promotion. -# -# By default the priority is 100. -replica-priority 100 - -# The propagation error behavior controls how Redis will behave when it is -# unable to handle a command being processed in the replication stream from a master -# or processed while reading from an AOF file. Errors that occur during propagation -# are unexpected, and can cause data inconsistency. However, there are edge cases -# in earlier versions of Redis where it was possible for the server to replicate or persist -# commands that would fail on future versions. For this reason the default behavior -# is to ignore such errors and continue processing commands. -# -# If an application wants to ensure there is no data divergence, this configuration -# should be set to 'panic' instead. The value can also be set to 'panic-on-replicas' -# to only panic when a replica encounters an error on the replication stream. One of -# these two panic values will become the default value in the future once there are -# sufficient safety mechanisms in place to prevent false positive crashes. -# -# propagation-error-behavior ignore - -# Replica ignore disk write errors controls the behavior of a replica when it is -# unable to persist a write command received from its master to disk. By default, -# this configuration is set to 'no' and will crash the replica in this condition. -# It is not recommended to change this default, however in order to be compatible -# with older versions of Redis this config can be toggled to 'yes' which will just -# log a warning and execute the write command it got from the master. -# -# replica-ignore-disk-write-errors no - -# ----------------------------------------------------------------------------- -# By default, Redis Sentinel includes all replicas in its reports. A replica -# can be excluded from Redis Sentinel's announcements. An unannounced replica -# will be ignored by the 'sentinel replicas ' command and won't be -# exposed to Redis Sentinel's clients. -# -# This option does not change the behavior of replica-priority. Even with -# replica-announced set to 'no', the replica can be promoted to master. To -# prevent this behavior, set replica-priority to 0. -# -# replica-announced yes - -# It is possible for a master to stop accepting writes if there are less than -# N replicas connected, having a lag less or equal than M seconds. -# -# The N replicas need to be in "online" state. -# -# The lag in seconds, that must be <= the specified value, is calculated from -# the last ping received from the replica, that is usually sent every second. -# -# This option does not GUARANTEE that N replicas will accept the write, but -# will limit the window of exposure for lost writes in case not enough replicas -# are available, to the specified number of seconds. -# -# For example to require at least 3 replicas with a lag <= 10 seconds use: -# -# min-replicas-to-write 3 -# min-replicas-max-lag 10 -# -# Setting one or the other to 0 disables the feature. -# -# By default min-replicas-to-write is set to 0 (feature disabled) and -# min-replicas-max-lag is set to 10. - -# A Redis master is able to list the address and port of the attached -# replicas in different ways. For example the "INFO replication" section -# offers this information, which is used, among other tools, by -# Redis Sentinel in order to discover replica instances. -# Another place where this info is available is in the output of the -# "ROLE" command of a master. -# -# The listed IP address and port normally reported by a replica is -# obtained in the following way: -# -# IP: The address is auto detected by checking the peer address -# of the socket used by the replica to connect with the master. -# -# Port: The port is communicated by the replica during the replication -# handshake, and is normally the port that the replica is using to -# listen for connections. -# -# However when port forwarding or Network Address Translation (NAT) is -# used, the replica may actually be reachable via different IP and port -# pairs. The following two options can be used by a replica in order to -# report to its master a specific set of IP and port, so that both INFO -# and ROLE will report those values. -# -# There is no need to use both the options if you need to override just -# the port or the IP address. -# -# replica-announce-ip 5.5.5.5 -# replica-announce-port 1234 - -############################### KEYS TRACKING ################################# - -# Redis implements server assisted support for client side caching of values. -# This is implemented using an invalidation table that remembers, using -# a radix key indexed by key name, what clients have which keys. In turn -# this is used in order to send invalidation messages to clients. Please -# check this page to understand more about the feature: -# -# https://redis.io/topics/client-side-caching -# -# When tracking is enabled for a client, all the read only queries are assumed -# to be cached: this will force Redis to store information in the invalidation -# table. When keys are modified, such information is flushed away, and -# invalidation messages are sent to the clients. However if the workload is -# heavily dominated by reads, Redis could use more and more memory in order -# to track the keys fetched by many clients. -# -# For this reason it is possible to configure a maximum fill value for the -# invalidation table. By default it is set to 1M of keys, and once this limit -# is reached, Redis will start to evict keys in the invalidation table -# even if they were not modified, just to reclaim memory: this will in turn -# force the clients to invalidate the cached values. Basically the table -# maximum size is a trade off between the memory you want to spend server -# side to track information about who cached what, and the ability of clients -# to retain cached objects in memory. -# -# If you set the value to 0, it means there are no limits, and Redis will -# retain as many keys as needed in the invalidation table. -# In the "stats" INFO section, you can find information about the number of -# keys in the invalidation table at every given moment. -# -# Note: when key tracking is used in broadcasting mode, no memory is used -# in the server side so this setting is useless. -# -# tracking-table-max-keys 1000000 - -################################## SECURITY ################################### - -# Warning: since Redis is pretty fast, an outside user can try up to -# 1 million passwords per second against a modern box. This means that you -# should use very strong passwords, otherwise they will be very easy to break. -# Note that because the password is really a shared secret between the client -# and the server, and should not be memorized by any human, the password -# can be easily a long string from /dev/urandom or whatever, so by using a -# long and unguessable password no brute force attack will be possible. - -# Redis ACL users are defined in the following format: -# -# user ... acl rules ... -# -# For example: -# -# user worker +@list +@connection ~jobs:* on >ffa9203c493aa99 -# -# The special username "default" is used for new connections. If this user -# has the "nopass" rule, then new connections will be immediately authenticated -# as the "default" user without the need of any password provided via the -# AUTH command. Otherwise if the "default" user is not flagged with "nopass" -# the connections will start in not authenticated state, and will require -# AUTH (or the HELLO command AUTH option) in order to be authenticated and -# start to work. -# -# The ACL rules that describe what a user can do are the following: -# -# on Enable the user: it is possible to authenticate as this user. -# off Disable the user: it's no longer possible to authenticate -# with this user, however the already authenticated connections -# will still work. -# skip-sanitize-payload RESTORE dump-payload sanitization is skipped. -# sanitize-payload RESTORE dump-payload is sanitized (default). -# + Allow the execution of that command. -# May be used with `|` for allowing subcommands (e.g "+config|get") -# - Disallow the execution of that command. -# May be used with `|` for blocking subcommands (e.g "-config|set") -# +@ Allow the execution of all the commands in such category -# with valid categories are like @admin, @set, @sortedset, ... -# and so forth, see the full list in the server.c file where -# the Redis command table is described and defined. -# The special category @all means all the commands, but currently -# present in the server, and that will be loaded in the future -# via modules. -# +|first-arg Allow a specific first argument of an otherwise -# disabled command. It is only supported on commands with -# no sub-commands, and is not allowed as negative form -# like -SELECT|1, only additive starting with "+". This -# feature is deprecated and may be removed in the future. -# allcommands Alias for +@all. Note that it implies the ability to execute -# all the future commands loaded via the modules system. -# nocommands Alias for -@all. -# ~ Add a pattern of keys that can be mentioned as part of -# commands. For instance ~* allows all the keys. The pattern -# is a glob-style pattern like the one of KEYS. -# It is possible to specify multiple patterns. -# %R~ Add key read pattern that specifies which keys can be read -# from. -# %W~ Add key write pattern that specifies which keys can be -# written to. -# allkeys Alias for ~* -# resetkeys Flush the list of allowed keys patterns. -# & Add a glob-style pattern of Pub/Sub channels that can be -# accessed by the user. It is possible to specify multiple channel -# patterns. -# allchannels Alias for &* -# resetchannels Flush the list of allowed channel patterns. -# > Add this password to the list of valid password for the user. -# For example >mypass will add "mypass" to the list. -# This directive clears the "nopass" flag (see later). -# < Remove this password from the list of valid passwords. -# nopass All the set passwords of the user are removed, and the user -# is flagged as requiring no password: it means that every -# password will work against this user. If this directive is -# used for the default user, every new connection will be -# immediately authenticated with the default user without -# any explicit AUTH command required. Note that the "resetpass" -# directive will clear this condition. -# resetpass Flush the list of allowed passwords. Moreover removes the -# "nopass" status. After "resetpass" the user has no associated -# passwords and there is no way to authenticate without adding -# some password (or setting it as "nopass" later). -# reset Performs the following actions: resetpass, resetkeys, off, -# -@all. The user returns to the same state it has immediately -# after its creation. -# () Create a new selector with the options specified within the -# parentheses and attach it to the user. Each option should be -# space separated. The first character must be ( and the last -# character must be ). -# clearselectors Remove all of the currently attached selectors. -# Note this does not change the "root" user permissions, -# which are the permissions directly applied onto the -# user (outside the parentheses). -# -# ACL rules can be specified in any order: for instance you can start with -# passwords, then flags, or key patterns. However note that the additive -# and subtractive rules will CHANGE MEANING depending on the ordering. -# For instance see the following example: -# -# user alice on +@all -DEBUG ~* >somepassword -# -# This will allow "alice" to use all the commands with the exception of the -# DEBUG command, since +@all added all the commands to the set of the commands -# alice can use, and later DEBUG was removed. However if we invert the order -# of two ACL rules the result will be different: -# -# user alice on -DEBUG +@all ~* >somepassword -# -# Now DEBUG was removed when alice had yet no commands in the set of allowed -# commands, later all the commands are added, so the user will be able to -# execute everything. -# -# Basically ACL rules are processed left-to-right. -# -# The following is a list of command categories and their meanings: -# * keyspace - Writing or reading from keys, databases, or their metadata -# in a type agnostic way. Includes DEL, RESTORE, DUMP, RENAME, EXISTS, DBSIZE, -# KEYS, EXPIRE, TTL, FLUSHALL, etc. Commands that may modify the keyspace, -# key or metadata will also have `write` category. Commands that only read -# the keyspace, key or metadata will have the `read` category. -# * read - Reading from keys (values or metadata). Note that commands that don't -# interact with keys, will not have either `read` or `write`. -# * write - Writing to keys (values or metadata) -# * admin - Administrative commands. Normal applications will never need to use -# these. Includes REPLICAOF, CONFIG, DEBUG, SAVE, MONITOR, ACL, SHUTDOWN, etc. -# * dangerous - Potentially dangerous (each should be considered with care for -# various reasons). This includes FLUSHALL, MIGRATE, RESTORE, SORT, KEYS, -# CLIENT, DEBUG, INFO, CONFIG, SAVE, REPLICAOF, etc. -# * connection - Commands affecting the connection or other connections. -# This includes AUTH, SELECT, COMMAND, CLIENT, ECHO, PING, etc. -# * blocking - Potentially blocking the connection until released by another -# command. -# * fast - Fast O(1) commands. May loop on the number of arguments, but not the -# number of elements in the key. -# * slow - All commands that are not Fast. -# * pubsub - PUBLISH / SUBSCRIBE related -# * transaction - WATCH / MULTI / EXEC related commands. -# * scripting - Scripting related. -# * set - Data type: sets related. -# * sortedset - Data type: zsets related. -# * list - Data type: lists related. -# * hash - Data type: hashes related. -# * string - Data type: strings related. -# * bitmap - Data type: bitmaps related. -# * hyperloglog - Data type: hyperloglog related. -# * geo - Data type: geo related. -# * stream - Data type: streams related. -# -# For more information about ACL configuration please refer to -# the Redis web site at https://redis.io/topics/acl - -# ACL LOG -# -# The ACL Log tracks failed commands and authentication events associated -# with ACLs. The ACL Log is useful to troubleshoot failed commands blocked -# by ACLs. The ACL Log is stored in memory. You can reclaim memory with -# ACL LOG RESET. Define the maximum entry length of the ACL Log below. -acllog-max-len 128 - -# Using an external ACL file -# -# Instead of configuring users here in this file, it is possible to use -# a stand-alone file just listing users. The two methods cannot be mixed: -# if you configure users here and at the same time you activate the external -# ACL file, the server will refuse to start. -# -# The format of the external ACL user file is exactly the same as the -# format that is used inside redis.conf to describe users. -# -# aclfile /etc/redis/users.acl - -# IMPORTANT NOTE: starting with Redis 6 "requirepass" is just a compatibility -# layer on top of the new ACL system. The option effect will be just setting -# the password for the default user. Clients will still authenticate using -# AUTH as usually, or more explicitly with AUTH default -# if they follow the new protocol: both will work. -# -# The requirepass is not compatible with aclfile option and the ACL LOAD -# command, these will cause requirepass to be ignored. -# -requirepass kd123456 - -# New users are initialized with restrictive permissions by default, via the -# equivalent of this ACL rule 'off resetkeys -@all'. Starting with Redis 6.2, it -# is possible to manage access to Pub/Sub channels with ACL rules as well. The -# default Pub/Sub channels permission if new users is controlled by the -# acl-pubsub-default configuration directive, which accepts one of these values: -# -# allchannels: grants access to all Pub/Sub channels -# resetchannels: revokes access to all Pub/Sub channels -# -# From Redis 7.0, acl-pubsub-default defaults to 'resetchannels' permission. -# -# acl-pubsub-default resetchannels - -# Command renaming (DEPRECATED). -# -# ------------------------------------------------------------------------ -# WARNING: avoid using this option if possible. Instead use ACLs to remove -# commands from the default user, and put them only in some admin user you -# create for administrative purposes. -# ------------------------------------------------------------------------ -# -# It is possible to change the name of dangerous commands in a shared -# environment. For instance the CONFIG command may be renamed into something -# hard to guess so that it will still be available for internal-use tools -# but not available for general clients. -# -# Example: -# -# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52 -# -# It is also possible to completely kill a command by renaming it into -# an empty string: -# -# rename-command CONFIG "" -# -# Please note that changing the name of commands that are logged into the -# AOF file or transmitted to replicas may cause problems. - -################################### CLIENTS #################################### - -# Set the max number of connected clients at the same time. By default -# this limit is set to 10000 clients, however if the Redis server is not -# able to configure the process file limit to allow for the specified limit -# the max number of allowed clients is set to the current file limit -# minus 32 (as Redis reserves a few file descriptors for internal uses). -# -# Once the limit is reached Redis will close all the new connections sending -# an error 'max number of clients reached'. -# -# IMPORTANT: When Redis Cluster is used, the max number of connections is also -# shared with the cluster bus: every node in the cluster will use two -# connections, one incoming and another outgoing. It is important to size the -# limit accordingly in case of very large clusters. -# -# maxclients 10000 - -############################## MEMORY MANAGEMENT ################################ - -# Set a memory usage limit to the specified amount of bytes. -# When the memory limit is reached Redis will try to remove keys -# according to the eviction policy selected (see maxmemory-policy). -# -# If Redis can't remove keys according to the policy, or if the policy is -# set to 'noeviction', Redis will start to reply with errors to commands -# that would use more memory, like SET, LPUSH, and so on, and will continue -# to reply to read-only commands like GET. -# -# This option is usually useful when using Redis as an LRU or LFU cache, or to -# set a hard memory limit for an instance (using the 'noeviction' policy). -# -# WARNING: If you have replicas attached to an instance with maxmemory on, -# the size of the output buffers needed to feed the replicas are subtracted -# from the used memory count, so that network problems / resyncs will -# not trigger a loop where keys are evicted, and in turn the output -# buffer of replicas is full with DELs of keys evicted triggering the deletion -# of more keys, and so forth until the database is completely emptied. -# -# In short... if you have replicas attached it is suggested that you set a lower -# limit for maxmemory so that there is some free RAM on the system for replica -# output buffers (but this is not needed if the policy is 'noeviction'). -# -# maxmemory - -# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory -# is reached. You can select one from the following behaviors: -# -# volatile-lru -> Evict using approximated LRU, only keys with an expire set. -# allkeys-lru -> Evict any key using approximated LRU. -# volatile-lfu -> Evict using approximated LFU, only keys with an expire set. -# allkeys-lfu -> Evict any key using approximated LFU. -# volatile-random -> Remove a random key having an expire set. -# allkeys-random -> Remove a random key, any key. -# volatile-ttl -> Remove the key with the nearest expire time (minor TTL) -# noeviction -> Don't evict anything, just return an error on write operations. -# -# LRU means Least Recently Used -# LFU means Least Frequently Used -# -# Both LRU, LFU and volatile-ttl are implemented using approximated -# randomized algorithms. -# -# Note: with any of the above policies, when there are no suitable keys for -# eviction, Redis will return an error on write operations that require -# more memory. These are usually commands that create new keys, add data or -# modify existing keys. A few examples are: SET, INCR, HSET, LPUSH, SUNIONSTORE, -# SORT (due to the STORE argument), and EXEC (if the transaction includes any -# command that requires memory). -# -# The default is: -# -# maxmemory-policy noeviction - -# LRU, LFU and minimal TTL algorithms are not precise algorithms but approximated -# algorithms (in order to save memory), so you can tune it for speed or -# accuracy. By default Redis will check five keys and pick the one that was -# used least recently, you can change the sample size using the following -# configuration directive. -# -# The default of 5 produces good enough results. 10 Approximates very closely -# true LRU but costs more CPU. 3 is faster but not very accurate. -# -# maxmemory-samples 5 - -# Eviction processing is designed to function well with the default setting. -# If there is an unusually large amount of write traffic, this value may need to -# be increased. Decreasing this value may reduce latency at the risk of -# eviction processing effectiveness -# 0 = minimum latency, 10 = default, 100 = process without regard to latency -# -# maxmemory-eviction-tenacity 10 - -# Starting from Redis 5, by default a replica will ignore its maxmemory setting -# (unless it is promoted to master after a failover or manually). It means -# that the eviction of keys will be just handled by the master, sending the -# DEL commands to the replica as keys evict in the master side. -# -# This behavior ensures that masters and replicas stay consistent, and is usually -# what you want, however if your replica is writable, or you want the replica -# to have a different memory setting, and you are sure all the writes performed -# to the replica are idempotent, then you may change this default (but be sure -# to understand what you are doing). -# -# Note that since the replica by default does not evict, it may end using more -# memory than the one set via maxmemory (there are certain buffers that may -# be larger on the replica, or data structures may sometimes take more memory -# and so forth). So make sure you monitor your replicas and make sure they -# have enough memory to never hit a real out-of-memory condition before the -# master hits the configured maxmemory setting. -# -# replica-ignore-maxmemory yes - -# Redis reclaims expired keys in two ways: upon access when those keys are -# found to be expired, and also in background, in what is called the -# "active expire key". The key space is slowly and interactively scanned -# looking for expired keys to reclaim, so that it is possible to free memory -# of keys that are expired and will never be accessed again in a short time. -# -# The default effort of the expire cycle will try to avoid having more than -# ten percent of expired keys still in memory, and will try to avoid consuming -# more than 25% of total memory and to add latency to the system. However -# it is possible to increase the expire "effort" that is normally set to -# "1", to a greater value, up to the value "10". At its maximum value the -# system will use more CPU, longer cycles (and technically may introduce -# more latency), and will tolerate less already expired keys still present -# in the system. It's a tradeoff between memory, CPU and latency. -# -# active-expire-effort 1 - -############################# LAZY FREEING #################################### - -# Redis has two primitives to delete keys. One is called DEL and is a blocking -# deletion of the object. It means that the server stops processing new commands -# in order to reclaim all the memory associated with an object in a synchronous -# way. If the key deleted is associated with a small object, the time needed -# in order to execute the DEL command is very small and comparable to most other -# O(1) or O(log_N) commands in Redis. However if the key is associated with an -# aggregated value containing millions of elements, the server can block for -# a long time (even seconds) in order to complete the operation. -# -# For the above reasons Redis also offers non blocking deletion primitives -# such as UNLINK (non blocking DEL) and the ASYNC option of FLUSHALL and -# FLUSHDB commands, in order to reclaim memory in background. Those commands -# are executed in constant time. Another thread will incrementally free the -# object in the background as fast as possible. -# -# DEL, UNLINK and ASYNC option of FLUSHALL and FLUSHDB are user-controlled. -# It's up to the design of the application to understand when it is a good -# idea to use one or the other. However the Redis server sometimes has to -# delete keys or flush the whole database as a side effect of other operations. -# Specifically Redis deletes objects independently of a user call in the -# following scenarios: -# -# 1) On eviction, because of the maxmemory and maxmemory policy configurations, -# in order to make room for new data, without going over the specified -# memory limit. -# 2) Because of expire: when a key with an associated time to live (see the -# EXPIRE command) must be deleted from memory. -# 3) Because of a side effect of a command that stores data on a key that may -# already exist. For example the RENAME command may delete the old key -# content when it is replaced with another one. Similarly SUNIONSTORE -# or SORT with STORE option may delete existing keys. The SET command -# itself removes any old content of the specified key in order to replace -# it with the specified string. -# 4) During replication, when a replica performs a full resynchronization with -# its master, the content of the whole database is removed in order to -# load the RDB file just transferred. -# -# In all the above cases the default is to delete objects in a blocking way, -# like if DEL was called. However you can configure each case specifically -# in order to instead release memory in a non-blocking way like if UNLINK -# was called, using the following configuration directives. - -lazyfree-lazy-eviction no -lazyfree-lazy-expire no -lazyfree-lazy-server-del no -replica-lazy-flush no - -# It is also possible, for the case when to replace the user code DEL calls -# with UNLINK calls is not easy, to modify the default behavior of the DEL -# command to act exactly like UNLINK, using the following configuration -# directive: - -lazyfree-lazy-user-del no - -# FLUSHDB, FLUSHALL, SCRIPT FLUSH and FUNCTION FLUSH support both asynchronous and synchronous -# deletion, which can be controlled by passing the [SYNC|ASYNC] flags into the -# commands. When neither flag is passed, this directive will be used to determine -# if the data should be deleted asynchronously. - -lazyfree-lazy-user-flush no - -################################ THREADED I/O ################################# - -# Redis is mostly single threaded, however there are certain threaded -# operations such as UNLINK, slow I/O accesses and other things that are -# performed on side threads. -# -# Now it is also possible to handle Redis clients socket reads and writes -# in different I/O threads. Since especially writing is so slow, normally -# Redis users use pipelining in order to speed up the Redis performances per -# core, and spawn multiple instances in order to scale more. Using I/O -# threads it is possible to easily speedup two times Redis without resorting -# to pipelining nor sharding of the instance. -# -# By default threading is disabled, we suggest enabling it only in machines -# that have at least 4 or more cores, leaving at least one spare core. -# Using more than 8 threads is unlikely to help much. We also recommend using -# threaded I/O only if you actually have performance problems, with Redis -# instances being able to use a quite big percentage of CPU time, otherwise -# there is no point in using this feature. -# -# So for instance if you have a four cores boxes, try to use 2 or 3 I/O -# threads, if you have a 8 cores, try to use 6 threads. In order to -# enable I/O threads use the following configuration directive: -# -# io-threads 4 -# -# Setting io-threads to 1 will just use the main thread as usual. -# When I/O threads are enabled, we only use threads for writes, that is -# to thread the write(2) syscall and transfer the client buffers to the -# socket. However it is also possible to enable threading of reads and -# protocol parsing using the following configuration directive, by setting -# it to yes: -# -# io-threads-do-reads no -# -# Usually threading reads doesn't help much. -# -# NOTE 1: This configuration directive cannot be changed at runtime via -# CONFIG SET. Also, this feature currently does not work when SSL is -# enabled. -# -# NOTE 2: If you want to test the Redis speedup using redis-benchmark, make -# sure you also run the benchmark itself in threaded mode, using the -# --threads option to match the number of Redis threads, otherwise you'll not -# be able to notice the improvements. - -############################ KERNEL OOM CONTROL ############################## - -# On Linux, it is possible to hint the kernel OOM killer on what processes -# should be killed first when out of memory. -# -# Enabling this feature makes Redis actively control the oom_score_adj value -# for all its processes, depending on their role. The default scores will -# attempt to have background child processes killed before all others, and -# replicas killed before masters. -# -# Redis supports these options: -# -# no: Don't make changes to oom-score-adj (default). -# yes: Alias to "relative" see below. -# absolute: Values in oom-score-adj-values are written as is to the kernel. -# relative: Values are used relative to the initial value of oom_score_adj when -# the server starts and are then clamped to a range of -1000 to 1000. -# Because typically the initial value is 0, they will often match the -# absolute values. -oom-score-adj no - -# When oom-score-adj is used, this directive controls the specific values used -# for master, replica and background child processes. Values range -2000 to -# 2000 (higher means more likely to be killed). -# -# Unprivileged processes (not root, and without CAP_SYS_RESOURCE capabilities) -# can freely increase their value, but not decrease it below its initial -# settings. This means that setting oom-score-adj to "relative" and setting the -# oom-score-adj-values to positive values will always succeed. -oom-score-adj-values 0 200 800 - - -#################### KERNEL transparent hugepage CONTROL ###################### - -# Usually the kernel Transparent Huge Pages control is set to "madvise" or -# or "never" by default (/sys/kernel/mm/transparent_hugepage/enabled), in which -# case this config has no effect. On systems in which it is set to "always", -# redis will attempt to disable it specifically for the redis process in order -# to avoid latency problems specifically with fork(2) and CoW. -# If for some reason you prefer to keep it enabled, you can set this config to -# "no" and the kernel global to "always". - -disable-thp yes - -############################## APPEND ONLY MODE ############################### - -# By default Redis asynchronously dumps the dataset on disk. This mode is -# good enough in many applications, but an issue with the Redis process or -# a power outage may result into a few minutes of writes lost (depending on -# the configured save points). -# -# The Append Only File is an alternative persistence mode that provides -# much better durability. For instance using the default data fsync policy -# (see later in the config file) Redis can lose just one second of writes in a -# dramatic event like a server power outage, or a single write if something -# wrong with the Redis process itself happens, but the operating system is -# still running correctly. -# -# AOF and RDB persistence can be enabled at the same time without problems. -# If the AOF is enabled on startup Redis will load the AOF, that is the file -# with the better durability guarantees. -# -# Please check https://redis.io/topics/persistence for more information. - -appendonly yes - -# The base name of the append only file. -# -# Redis 7 and newer use a set of append-only files to persist the dataset -# and changes applied to it. There are two basic types of files in use: -# -# - Base files, which are a snapshot representing the complete state of the -# dataset at the time the file was created. Base files can be either in -# the form of RDB (binary serialized) or AOF (textual commands). -# - Incremental files, which contain additional commands that were applied -# to the dataset following the previous file. -# -# In addition, manifest files are used to track the files and the order in -# which they were created and should be applied. -# -# Append-only file names are created by Redis following a specific pattern. -# The file name's prefix is based on the 'appendfilename' configuration -# parameter, followed by additional information about the sequence and type. -# -# For example, if appendfilename is set to appendonly.aof, the following file -# names could be derived: -# -# - appendonly.aof.1.base.rdb as a base file. -# - appendonly.aof.1.incr.aof, appendonly.aof.2.incr.aof as incremental files. -# - appendonly.aof.manifest as a manifest file. - -appendfilename "appendonly.aof" - -# For convenience, Redis stores all persistent append-only files in a dedicated -# directory. The name of the directory is determined by the appenddirname -# configuration parameter. - -appenddirname "appendonlydir" - -# The fsync() call tells the Operating System to actually write data on disk -# instead of waiting for more data in the output buffer. Some OS will really flush -# data on disk, some other OS will just try to do it ASAP. -# -# Redis supports three different modes: -# -# no: don't fsync, just let the OS flush the data when it wants. Faster. -# always: fsync after every write to the append only log. Slow, Safest. -# everysec: fsync only one time every second. Compromise. -# -# The default is "everysec", as that's usually the right compromise between -# speed and data safety. It's up to you to understand if you can relax this to -# "no" that will let the operating system flush the output buffer when -# it wants, for better performances (but if you can live with the idea of -# some data loss consider the default persistence mode that's snapshotting), -# or on the contrary, use "always" that's very slow but a bit safer than -# everysec. -# -# More details please check the following article: -# http://antirez.com/post/redis-persistence-demystified.html -# -# If unsure, use "everysec". - -# appendfsync always -appendfsync everysec -# appendfsync no - -# When the AOF fsync policy is set to always or everysec, and a background -# saving process (a background save or AOF log background rewriting) is -# performing a lot of I/O against the disk, in some Linux configurations -# Redis may block too long on the fsync() call. Note that there is no fix for -# this currently, as even performing fsync in a different thread will block -# our synchronous write(2) call. -# -# In order to mitigate this problem it's possible to use the following option -# that will prevent fsync() from being called in the main process while a -# BGSAVE or BGREWRITEAOF is in progress. -# -# This means that while another child is saving, the durability of Redis is -# the same as "appendfsync no". In practical terms, this means that it is -# possible to lose up to 30 seconds of log in the worst scenario (with the -# default Linux settings). -# -# If you have latency problems turn this to "yes". Otherwise leave it as -# "no" that is the safest pick from the point of view of durability. - -no-appendfsync-on-rewrite no - -# Automatic rewrite of the append only file. -# Redis is able to automatically rewrite the log file implicitly calling -# BGREWRITEAOF when the AOF log size grows by the specified percentage. -# -# This is how it works: Redis remembers the size of the AOF file after the -# latest rewrite (if no rewrite has happened since the restart, the size of -# the AOF at startup is used). -# -# This base size is compared to the current size. If the current size is -# bigger than the specified percentage, the rewrite is triggered. Also -# you need to specify a minimal size for the AOF file to be rewritten, this -# is useful to avoid rewriting the AOF file even if the percentage increase -# is reached but it is still pretty small. -# -# Specify a percentage of zero in order to disable the automatic AOF -# rewrite feature. - -auto-aof-rewrite-percentage 100 -auto-aof-rewrite-min-size 64mb - -# An AOF file may be found to be truncated at the end during the Redis -# startup process, when the AOF data gets loaded back into memory. -# This may happen when the system where Redis is running -# crashes, especially when an ext4 filesystem is mounted without the -# data=ordered option (however this can't happen when Redis itself -# crashes or aborts but the operating system still works correctly). -# -# Redis can either exit with an error when this happens, or load as much -# data as possible (the default now) and start if the AOF file is found -# to be truncated at the end. The following option controls this behavior. -# -# If aof-load-truncated is set to yes, a truncated AOF file is loaded and -# the Redis server starts emitting a log to inform the user of the event. -# Otherwise if the option is set to no, the server aborts with an error -# and refuses to start. When the option is set to no, the user requires -# to fix the AOF file using the "redis-check-aof" utility before to restart -# the server. -# -# Note that if the AOF file will be found to be corrupted in the middle -# the server will still exit with an error. This option only applies when -# Redis will try to read more data from the AOF file but not enough bytes -# will be found. -aof-load-truncated yes - -# Redis can create append-only base files in either RDB or AOF formats. Using -# the RDB format is always faster and more efficient, and disabling it is only -# supported for backward compatibility purposes. -aof-use-rdb-preamble yes - -# Redis supports recording timestamp annotations in the AOF to support restoring -# the data from a specific point-in-time. However, using this capability changes -# the AOF format in a way that may not be compatible with existing AOF parsers. -aof-timestamp-enabled no - -################################ SHUTDOWN ##################################### - -# Maximum time to wait for replicas when shutting down, in seconds. -# -# During shut down, a grace period allows any lagging replicas to catch up with -# the latest replication offset before the master exists. This period can -# prevent data loss, especially for deployments without configured disk backups. -# -# The 'shutdown-timeout' value is the grace period's duration in seconds. It is -# only applicable when the instance has replicas. To disable the feature, set -# the value to 0. -# -# shutdown-timeout 10 - -# When Redis receives a SIGINT or SIGTERM, shutdown is initiated and by default -# an RDB snapshot is written to disk in a blocking operation if save points are configured. -# The options used on signaled shutdown can include the following values: -# default: Saves RDB snapshot only if save points are configured. -# Waits for lagging replicas to catch up. -# save: Forces a DB saving operation even if no save points are configured. -# nosave: Prevents DB saving operation even if one or more save points are configured. -# now: Skips waiting for lagging replicas. -# force: Ignores any errors that would normally prevent the server from exiting. -# -# Any combination of values is allowed as long as "save" and "nosave" are not set simultaneously. -# Example: "nosave force now" -# -# shutdown-on-sigint default -# shutdown-on-sigterm default - -################ NON-DETERMINISTIC LONG BLOCKING COMMANDS ##################### - -# Maximum time in milliseconds for EVAL scripts, functions and in some cases -# modules' commands before Redis can start processing or rejecting other clients. -# -# If the maximum execution time is reached Redis will start to reply to most -# commands with a BUSY error. -# -# In this state Redis will only allow a handful of commands to be executed. -# For instance, SCRIPT KILL, FUNCTION KILL, SHUTDOWN NOSAVE and possibly some -# module specific 'allow-busy' commands. -# -# SCRIPT KILL and FUNCTION KILL will only be able to stop a script that did not -# yet call any write commands, so SHUTDOWN NOSAVE may be the only way to stop -# the server in the case a write command was already issued by the script when -# the user doesn't want to wait for the natural termination of the script. -# -# The default is 5 seconds. It is possible to set it to 0 or a negative value -# to disable this mechanism (uninterrupted execution). Note that in the past -# this config had a different name, which is now an alias, so both of these do -# the same: -# lua-time-limit 5000 -# busy-reply-threshold 5000 - -################################ REDIS CLUSTER ############################### - -# Normal Redis instances can't be part of a Redis Cluster; only nodes that are -# started as cluster nodes can. In order to start a Redis instance as a -# cluster node enable the cluster support uncommenting the following: -# -# cluster-enabled yes - -# Every cluster node has a cluster configuration file. This file is not -# intended to be edited by hand. It is created and updated by Redis nodes. -# Every Redis Cluster node requires a different cluster configuration file. -# Make sure that instances running in the same system do not have -# overlapping cluster configuration file names. -# -# cluster-config-file nodes-6379.conf - -# Cluster node timeout is the amount of milliseconds a node must be unreachable -# for it to be considered in failure state. -# Most other internal time limits are a multiple of the node timeout. -# -# cluster-node-timeout 15000 - -# The cluster port is the port that the cluster bus will listen for inbound connections on. When set -# to the default value, 0, it will be bound to the command port + 10000. Setting this value requires -# you to specify the cluster bus port when executing cluster meet. -# cluster-port 0 - -# A replica of a failing master will avoid to start a failover if its data -# looks too old. -# -# There is no simple way for a replica to actually have an exact measure of -# its "data age", so the following two checks are performed: -# -# 1) If there are multiple replicas able to failover, they exchange messages -# in order to try to give an advantage to the replica with the best -# replication offset (more data from the master processed). -# Replicas will try to get their rank by offset, and apply to the start -# of the failover a delay proportional to their rank. -# -# 2) Every single replica computes the time of the last interaction with -# its master. This can be the last ping or command received (if the master -# is still in the "connected" state), or the time that elapsed since the -# disconnection with the master (if the replication link is currently down). -# If the last interaction is too old, the replica will not try to failover -# at all. -# -# The point "2" can be tuned by user. Specifically a replica will not perform -# the failover if, since the last interaction with the master, the time -# elapsed is greater than: -# -# (node-timeout * cluster-replica-validity-factor) + repl-ping-replica-period -# -# So for example if node-timeout is 30 seconds, and the cluster-replica-validity-factor -# is 10, and assuming a default repl-ping-replica-period of 10 seconds, the -# replica will not try to failover if it was not able to talk with the master -# for longer than 310 seconds. -# -# A large cluster-replica-validity-factor may allow replicas with too old data to failover -# a master, while a too small value may prevent the cluster from being able to -# elect a replica at all. -# -# For maximum availability, it is possible to set the cluster-replica-validity-factor -# to a value of 0, which means, that replicas will always try to failover the -# master regardless of the last time they interacted with the master. -# (However they'll always try to apply a delay proportional to their -# offset rank). -# -# Zero is the only value able to guarantee that when all the partitions heal -# the cluster will always be able to continue. -# -# cluster-replica-validity-factor 10 - -# Cluster replicas are able to migrate to orphaned masters, that are masters -# that are left without working replicas. This improves the cluster ability -# to resist to failures as otherwise an orphaned master can't be failed over -# in case of failure if it has no working replicas. -# -# Replicas migrate to orphaned masters only if there are still at least a -# given number of other working replicas for their old master. This number -# is the "migration barrier". A migration barrier of 1 means that a replica -# will migrate only if there is at least 1 other working replica for its master -# and so forth. It usually reflects the number of replicas you want for every -# master in your cluster. -# -# Default is 1 (replicas migrate only if their masters remain with at least -# one replica). To disable migration just set it to a very large value or -# set cluster-allow-replica-migration to 'no'. -# A value of 0 can be set but is useful only for debugging and dangerous -# in production. -# -# cluster-migration-barrier 1 - -# Turning off this option allows to use less automatic cluster configuration. -# It both disables migration to orphaned masters and migration from masters -# that became empty. -# -# Default is 'yes' (allow automatic migrations). -# -# cluster-allow-replica-migration yes - -# By default Redis Cluster nodes stop accepting queries if they detect there -# is at least a hash slot uncovered (no available node is serving it). -# This way if the cluster is partially down (for example a range of hash slots -# are no longer covered) all the cluster becomes, eventually, unavailable. -# It automatically returns available as soon as all the slots are covered again. -# -# However sometimes you want the subset of the cluster which is working, -# to continue to accept queries for the part of the key space that is still -# covered. In order to do so, just set the cluster-require-full-coverage -# option to no. -# -# cluster-require-full-coverage yes - -# This option, when set to yes, prevents replicas from trying to failover its -# master during master failures. However the replica can still perform a -# manual failover, if forced to do so. -# -# This is useful in different scenarios, especially in the case of multiple -# data center operations, where we want one side to never be promoted if not -# in the case of a total DC failure. -# -# cluster-replica-no-failover no - -# This option, when set to yes, allows nodes to serve read traffic while the -# cluster is in a down state, as long as it believes it owns the slots. -# -# This is useful for two cases. The first case is for when an application -# doesn't require consistency of data during node failures or network partitions. -# One example of this is a cache, where as long as the node has the data it -# should be able to serve it. -# -# The second use case is for configurations that don't meet the recommended -# three shards but want to enable cluster mode and scale later. A -# master outage in a 1 or 2 shard configuration causes a read/write outage to the -# entire cluster without this option set, with it set there is only a write outage. -# Without a quorum of masters, slot ownership will not change automatically. -# -# cluster-allow-reads-when-down no - -# This option, when set to yes, allows nodes to serve pubsub shard traffic while -# the cluster is in a down state, as long as it believes it owns the slots. -# -# This is useful if the application would like to use the pubsub feature even when -# the cluster global stable state is not OK. If the application wants to make sure only -# one shard is serving a given channel, this feature should be kept as yes. -# -# cluster-allow-pubsubshard-when-down yes - -# Cluster link send buffer limit is the limit on the memory usage of an individual -# cluster bus link's send buffer in bytes. Cluster links would be freed if they exceed -# this limit. This is to primarily prevent send buffers from growing unbounded on links -# toward slow peers (E.g. PubSub messages being piled up). -# This limit is disabled by default. Enable this limit when 'mem_cluster_links' INFO field -# and/or 'send-buffer-allocated' entries in the 'CLUSTER LINKS` command output continuously increase. -# Minimum limit of 1gb is recommended so that cluster link buffer can fit in at least a single -# PubSub message by default. (client-query-buffer-limit default value is 1gb) -# -# cluster-link-sendbuf-limit 0 - -# Clusters can configure their announced hostname using this config. This is a common use case for -# applications that need to use TLS Server Name Indication (SNI) or dealing with DNS based -# routing. By default this value is only shown as additional metadata in the CLUSTER SLOTS -# command, but can be changed using 'cluster-preferred-endpoint-type' config. This value is -# communicated along the clusterbus to all nodes, setting it to an empty string will remove -# the hostname and also propagate the removal. -# -# cluster-announce-hostname "" - -# Clusters can advertise how clients should connect to them using either their IP address, -# a user defined hostname, or by declaring they have no endpoint. Which endpoint is -# shown as the preferred endpoint is set by using the cluster-preferred-endpoint-type -# config with values 'ip', 'hostname', or 'unknown-endpoint'. This value controls how -# the endpoint returned for MOVED/ASKING requests as well as the first field of CLUSTER SLOTS. -# If the preferred endpoint type is set to hostname, but no announced hostname is set, a '?' -# will be returned instead. -# -# When a cluster advertises itself as having an unknown endpoint, it's indicating that -# the server doesn't know how clients can reach the cluster. This can happen in certain -# networking situations where there are multiple possible routes to the node, and the -# server doesn't know which one the client took. In this case, the server is expecting -# the client to reach out on the same endpoint it used for making the last request, but use -# the port provided in the response. -# -# cluster-preferred-endpoint-type ip - -# In order to setup your cluster make sure to read the documentation -# available at https://redis.io web site. - -########################## CLUSTER DOCKER/NAT support ######################## - -# In certain deployments, Redis Cluster nodes address discovery fails, because -# addresses are NAT-ted or because ports are forwarded (the typical case is -# Docker and other containers). -# -# In order to make Redis Cluster working in such environments, a static -# configuration where each node knows its public address is needed. The -# following four options are used for this scope, and are: -# -# * cluster-announce-ip -# * cluster-announce-port -# * cluster-announce-tls-port -# * cluster-announce-bus-port -# -# Each instructs the node about its address, client ports (for connections -# without and with TLS) and cluster message bus port. The information is then -# published in the header of the bus packets so that other nodes will be able to -# correctly map the address of the node publishing the information. -# -# If cluster-tls is set to yes and cluster-announce-tls-port is omitted or set -# to zero, then cluster-announce-port refers to the TLS port. Note also that -# cluster-announce-tls-port has no effect if cluster-tls is set to no. -# -# If the above options are not used, the normal Redis Cluster auto-detection -# will be used instead. -# -# Note that when remapped, the bus port may not be at the fixed offset of -# clients port + 10000, so you can specify any port and bus-port depending -# on how they get remapped. If the bus-port is not set, a fixed offset of -# 10000 will be used as usual. -# -# Example: -# -# cluster-announce-ip 10.1.1.5 -# cluster-announce-tls-port 6379 -# cluster-announce-port 0 -# cluster-announce-bus-port 6380 - -################################## SLOW LOG ################################### - -# The Redis Slow Log is a system to log queries that exceeded a specified -# execution time. The execution time does not include the I/O operations -# like talking with the client, sending the reply and so forth, -# but just the time needed to actually execute the command (this is the only -# stage of command execution where the thread is blocked and can not serve -# other requests in the meantime). -# -# You can configure the slow log with two parameters: one tells Redis -# what is the execution time, in microseconds, to exceed in order for the -# command to get logged, and the other parameter is the length of the -# slow log. When a new command is logged the oldest one is removed from the -# queue of logged commands. - -# The following time is expressed in microseconds, so 1000000 is equivalent -# to one second. Note that a negative number disables the slow log, while -# a value of zero forces the logging of every command. -slowlog-log-slower-than 10000 - -# There is no limit to this length. Just be aware that it will consume memory. -# You can reclaim memory used by the slow log with SLOWLOG RESET. -slowlog-max-len 128 - -################################ LATENCY MONITOR ############################## - -# The Redis latency monitoring subsystem samples different operations -# at runtime in order to collect data related to possible sources of -# latency of a Redis instance. -# -# Via the LATENCY command this information is available to the user that can -# print graphs and obtain reports. -# -# The system only logs operations that were performed in a time equal or -# greater than the amount of milliseconds specified via the -# latency-monitor-threshold configuration directive. When its value is set -# to zero, the latency monitor is turned off. -# -# By default latency monitoring is disabled since it is mostly not needed -# if you don't have latency issues, and collecting data has a performance -# impact, that while very small, can be measured under big load. Latency -# monitoring can easily be enabled at runtime using the command -# "CONFIG SET latency-monitor-threshold " if needed. -latency-monitor-threshold 0 - -################################ LATENCY TRACKING ############################## - -# The Redis extended latency monitoring tracks the per command latencies and enables -# exporting the percentile distribution via the INFO latencystats command, -# and cumulative latency distributions (histograms) via the LATENCY command. -# -# By default, the extended latency monitoring is enabled since the overhead -# of keeping track of the command latency is very small. -# latency-tracking yes - -# By default the exported latency percentiles via the INFO latencystats command -# are the p50, p99, and p999. -# latency-tracking-info-percentiles 50 99 99.9 - -############################# EVENT NOTIFICATION ############################## - -# Redis can notify Pub/Sub clients about events happening in the key space. -# This feature is documented at https://redis.io/topics/notifications -# -# For instance if keyspace events notification is enabled, and a client -# performs a DEL operation on key "foo" stored in the Database 0, two -# messages will be published via Pub/Sub: -# -# PUBLISH __keyspace@0__:foo del -# PUBLISH __keyevent@0__:del foo -# -# It is possible to select the events that Redis will notify among a set -# of classes. Every class is identified by a single character: -# -# K Keyspace events, published with __keyspace@__ prefix. -# E Keyevent events, published with __keyevent@__ prefix. -# g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ... -# $ String commands -# l List commands -# s Set commands -# h Hash commands -# z Sorted set commands -# x Expired events (events generated every time a key expires) -# e Evicted events (events generated when a key is evicted for maxmemory) -# n New key events (Note: not included in the 'A' class) -# t Stream commands -# d Module key type events -# m Key-miss events (Note: It is not included in the 'A' class) -# A Alias for g$lshzxetd, so that the "AKE" string means all the events -# (Except key-miss events which are excluded from 'A' due to their -# unique nature). -# -# The "notify-keyspace-events" takes as argument a string that is composed -# of zero or multiple characters. The empty string means that notifications -# are disabled. -# -# Example: to enable list and generic events, from the point of view of the -# event name, use: -# -# notify-keyspace-events Elg -# -# Example 2: to get the stream of the expired keys subscribing to channel -# name __keyevent@0__:expired use: -# -# notify-keyspace-events Ex -# -# By default all notifications are disabled because most users don't need -# this feature and the feature has some overhead. Note that if you don't -# specify at least one of K or E, no events will be delivered. -notify-keyspace-events "" - -############################### ADVANCED CONFIG ############################### - -# Hashes are encoded using a memory efficient data structure when they have a -# small number of entries, and the biggest entry does not exceed a given -# threshold. These thresholds can be configured using the following directives. -hash-max-listpack-entries 512 -hash-max-listpack-value 64 - -# Lists are also encoded in a special way to save a lot of space. -# The number of entries allowed per internal list node can be specified -# as a fixed maximum size or a maximum number of elements. -# For a fixed maximum size, use -5 through -1, meaning: -# -5: max size: 64 Kb <-- not recommended for normal workloads -# -4: max size: 32 Kb <-- not recommended -# -3: max size: 16 Kb <-- probably not recommended -# -2: max size: 8 Kb <-- good -# -1: max size: 4 Kb <-- good -# Positive numbers mean store up to _exactly_ that number of elements -# per list node. -# The highest performing option is usually -2 (8 Kb size) or -1 (4 Kb size), -# but if your use case is unique, adjust the settings as necessary. -list-max-listpack-size -2 - -# Lists may also be compressed. -# Compress depth is the number of quicklist ziplist nodes from *each* side of -# the list to *exclude* from compression. The head and tail of the list -# are always uncompressed for fast push/pop operations. Settings are: -# 0: disable all list compression -# 1: depth 1 means "don't start compressing until after 1 node into the list, -# going from either the head or tail" -# So: [head]->node->node->...->node->[tail] -# [head], [tail] will always be uncompressed; inner nodes will compress. -# 2: [head]->[next]->node->node->...->node->[prev]->[tail] -# 2 here means: don't compress head or head->next or tail->prev or tail, -# but compress all nodes between them. -# 3: [head]->[next]->[next]->node->node->...->node->[prev]->[prev]->[tail] -# etc. -list-compress-depth 0 - -# Sets have a special encoding in just one case: when a set is composed -# of just strings that happen to be integers in radix 10 in the range -# of 64 bit signed integers. -# The following configuration setting sets the limit in the size of the -# set in order to use this special memory saving encoding. -set-max-intset-entries 512 - -# Similarly to hashes and lists, sorted sets are also specially encoded in -# order to save a lot of space. This encoding is only used when the length and -# elements of a sorted set are below the following limits: -zset-max-listpack-entries 128 -zset-max-listpack-value 64 - -# HyperLogLog sparse representation bytes limit. The limit includes the -# 16 bytes header. When an HyperLogLog using the sparse representation crosses -# this limit, it is converted into the dense representation. -# -# A value greater than 16000 is totally useless, since at that point the -# dense representation is more memory efficient. -# -# The suggested value is ~ 3000 in order to have the benefits of -# the space efficient encoding without slowing down too much PFADD, -# which is O(N) with the sparse encoding. The value can be raised to -# ~ 10000 when CPU is not a concern, but space is, and the data set is -# composed of many HyperLogLogs with cardinality in the 0 - 15000 range. -hll-sparse-max-bytes 3000 - -# Streams macro node max size / items. The stream data structure is a radix -# tree of big nodes that encode multiple items inside. Using this configuration -# it is possible to configure how big a single node can be in bytes, and the -# maximum number of items it may contain before switching to a new node when -# appending new stream entries. If any of the following settings are set to -# zero, the limit is ignored, so for instance it is possible to set just a -# max entries limit by setting max-bytes to 0 and max-entries to the desired -# value. -stream-node-max-bytes 4096 -stream-node-max-entries 100 - -# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in -# order to help rehashing the main Redis hash table (the one mapping top-level -# keys to values). The hash table implementation Redis uses (see dict.c) -# performs a lazy rehashing: the more operation you run into a hash table -# that is rehashing, the more rehashing "steps" are performed, so if the -# server is idle the rehashing is never complete and some more memory is used -# by the hash table. -# -# The default is to use this millisecond 10 times every second in order to -# actively rehash the main dictionaries, freeing memory when possible. -# -# If unsure: -# use "activerehashing no" if you have hard latency requirements and it is -# not a good thing in your environment that Redis can reply from time to time -# to queries with 2 milliseconds delay. -# -# use "activerehashing yes" if you don't have such hard requirements but -# want to free memory asap when possible. -activerehashing yes - -# The client output buffer limits can be used to force disconnection of clients -# that are not reading data from the server fast enough for some reason (a -# common reason is that a Pub/Sub client can't consume messages as fast as the -# publisher can produce them). -# -# The limit can be set differently for the three different classes of clients: -# -# normal -> normal clients including MONITOR clients -# replica -> replica clients -# pubsub -> clients subscribed to at least one pubsub channel or pattern -# -# The syntax of every client-output-buffer-limit directive is the following: -# -# client-output-buffer-limit -# -# A client is immediately disconnected once the hard limit is reached, or if -# the soft limit is reached and remains reached for the specified number of -# seconds (continuously). -# So for instance if the hard limit is 32 megabytes and the soft limit is -# 16 megabytes / 10 seconds, the client will get disconnected immediately -# if the size of the output buffers reach 32 megabytes, but will also get -# disconnected if the client reaches 16 megabytes and continuously overcomes -# the limit for 10 seconds. -# -# By default normal clients are not limited because they don't receive data -# without asking (in a push way), but just after a request, so only -# asynchronous clients may create a scenario where data is requested faster -# than it can read. -# -# Instead there is a default limit for pubsub and replica clients, since -# subscribers and replicas receive data in a push fashion. -# -# Note that it doesn't make sense to set the replica clients output buffer -# limit lower than the repl-backlog-size config (partial sync will succeed -# and then replica will get disconnected). -# Such a configuration is ignored (the size of repl-backlog-size will be used). -# This doesn't have memory consumption implications since the replica client -# will share the backlog buffers memory. -# -# Both the hard or the soft limit can be disabled by setting them to zero. -client-output-buffer-limit normal 0 0 0 -client-output-buffer-limit replica 256mb 64mb 60 -client-output-buffer-limit pubsub 32mb 8mb 60 - -# Client query buffers accumulate new commands. They are limited to a fixed -# amount by default in order to avoid that a protocol desynchronization (for -# instance due to a bug in the client) will lead to unbound memory usage in -# the query buffer. However you can configure it here if you have very special -# needs, such us huge multi/exec requests or alike. -# -# client-query-buffer-limit 1gb - -# In some scenarios client connections can hog up memory leading to OOM -# errors or data eviction. To avoid this we can cap the accumulated memory -# used by all client connections (all pubsub and normal clients). Once we -# reach that limit connections will be dropped by the server freeing up -# memory. The server will attempt to drop the connections using the most -# memory first. We call this mechanism "client eviction". -# -# Client eviction is configured using the maxmemory-clients setting as follows: -# 0 - client eviction is disabled (default) -# -# A memory value can be used for the client eviction threshold, -# for example: -# maxmemory-clients 1g -# -# A percentage value (between 1% and 100%) means the client eviction threshold -# is based on a percentage of the maxmemory setting. For example to set client -# eviction at 5% of maxmemory: -# maxmemory-clients 5% - -# In the Redis protocol, bulk requests, that are, elements representing single -# strings, are normally limited to 512 mb. However you can change this limit -# here, but must be 1mb or greater -# -# proto-max-bulk-len 512mb - -# Redis calls an internal function to perform many background tasks, like -# closing connections of clients in timeout, purging expired keys that are -# never requested, and so forth. -# -# Not all tasks are performed with the same frequency, but Redis checks for -# tasks to perform according to the specified "hz" value. -# -# By default "hz" is set to 10. Raising the value will use more CPU when -# Redis is idle, but at the same time will make Redis more responsive when -# there are many keys expiring at the same time, and timeouts may be -# handled with more precision. -# -# The range is between 1 and 500, however a value over 100 is usually not -# a good idea. Most users should use the default of 10 and raise this up to -# 100 only in environments where very low latency is required. -hz 10 - -# Normally it is useful to have an HZ value which is proportional to the -# number of clients connected. This is useful in order, for instance, to -# avoid too many clients are processed for each background task invocation -# in order to avoid latency spikes. -# -# Since the default HZ value by default is conservatively set to 10, Redis -# offers, and enables by default, the ability to use an adaptive HZ value -# which will temporarily raise when there are many connected clients. -# -# When dynamic HZ is enabled, the actual configured HZ will be used -# as a baseline, but multiples of the configured HZ value will be actually -# used as needed once more clients are connected. In this way an idle -# instance will use very little CPU time while a busy instance will be -# more responsive. -dynamic-hz yes - -# When a child rewrites the AOF file, if the following option is enabled -# the file will be fsync-ed every 4 MB of data generated. This is useful -# in order to commit the file to the disk more incrementally and avoid -# big latency spikes. -aof-rewrite-incremental-fsync yes - -# When redis saves RDB file, if the following option is enabled -# the file will be fsync-ed every 4 MB of data generated. This is useful -# in order to commit the file to the disk more incrementally and avoid -# big latency spikes. -rdb-save-incremental-fsync yes - -# Redis LFU eviction (see maxmemory setting) can be tuned. However it is a good -# idea to start with the default settings and only change them after investigating -# how to improve the performances and how the keys LFU change over time, which -# is possible to inspect via the OBJECT FREQ command. -# -# There are two tunable parameters in the Redis LFU implementation: the -# counter logarithm factor and the counter decay time. It is important to -# understand what the two parameters mean before changing them. -# -# The LFU counter is just 8 bits per key, it's maximum value is 255, so Redis -# uses a probabilistic increment with logarithmic behavior. Given the value -# of the old counter, when a key is accessed, the counter is incremented in -# this way: -# -# 1. A random number R between 0 and 1 is extracted. -# 2. A probability P is calculated as 1/(old_value*lfu_log_factor+1). -# 3. The counter is incremented only if R < P. -# -# The default lfu-log-factor is 10. This is a table of how the frequency -# counter changes with a different number of accesses with different -# logarithmic factors: -# -# +--------+------------+------------+------------+------------+------------+ -# | factor | 100 hits | 1000 hits | 100K hits | 1M hits | 10M hits | -# +--------+------------+------------+------------+------------+------------+ -# | 0 | 104 | 255 | 255 | 255 | 255 | -# +--------+------------+------------+------------+------------+------------+ -# | 1 | 18 | 49 | 255 | 255 | 255 | -# +--------+------------+------------+------------+------------+------------+ -# | 10 | 10 | 18 | 142 | 255 | 255 | -# +--------+------------+------------+------------+------------+------------+ -# | 100 | 8 | 11 | 49 | 143 | 255 | -# +--------+------------+------------+------------+------------+------------+ -# -# NOTE: The above table was obtained by running the following commands: -# -# redis-benchmark -n 1000000 incr foo -# redis-cli object freq foo -# -# NOTE 2: The counter initial value is 5 in order to give new objects a chance -# to accumulate hits. -# -# The counter decay time is the time, in minutes, that must elapse in order -# for the key counter to be divided by two (or decremented if it has a value -# less <= 10). -# -# The default value for the lfu-decay-time is 1. A special value of 0 means to -# decay the counter every time it happens to be scanned. -# -# lfu-log-factor 10 -# lfu-decay-time 1 - -########################### ACTIVE DEFRAGMENTATION ####################### -# -# What is active defragmentation? -# ------------------------------- -# -# Active (online) defragmentation allows a Redis server to compact the -# spaces left between small allocations and deallocations of data in memory, -# thus allowing to reclaim back memory. -# -# Fragmentation is a natural process that happens with every allocator (but -# less so with Jemalloc, fortunately) and certain workloads. Normally a server -# restart is needed in order to lower the fragmentation, or at least to flush -# away all the data and create it again. However thanks to this feature -# implemented by Oran Agra for Redis 4.0 this process can happen at runtime -# in a "hot" way, while the server is running. -# -# Basically when the fragmentation is over a certain level (see the -# configuration options below) Redis will start to create new copies of the -# values in contiguous memory regions by exploiting certain specific Jemalloc -# features (in order to understand if an allocation is causing fragmentation -# and to allocate it in a better place), and at the same time, will release the -# old copies of the data. This process, repeated incrementally for all the keys -# will cause the fragmentation to drop back to normal values. -# -# Important things to understand: -# -# 1. This feature is disabled by default, and only works if you compiled Redis -# to use the copy of Jemalloc we ship with the source code of Redis. -# This is the default with Linux builds. -# -# 2. You never need to enable this feature if you don't have fragmentation -# issues. -# -# 3. Once you experience fragmentation, you can enable this feature when -# needed with the command "CONFIG SET activedefrag yes". -# -# The configuration parameters are able to fine tune the behavior of the -# defragmentation process. If you are not sure about what they mean it is -# a good idea to leave the defaults untouched. - -# Active defragmentation is disabled by default -# activedefrag no - -# Minimum amount of fragmentation waste to start active defrag -# active-defrag-ignore-bytes 100mb - -# Minimum percentage of fragmentation to start active defrag -# active-defrag-threshold-lower 10 - -# Maximum percentage of fragmentation at which we use maximum effort -# active-defrag-threshold-upper 100 - -# Minimal effort for defrag in CPU percentage, to be used when the lower -# threshold is reached -# active-defrag-cycle-min 1 - -# Maximal effort for defrag in CPU percentage, to be used when the upper -# threshold is reached -# active-defrag-cycle-max 25 - -# Maximum number of set/hash/zset/list fields that will be processed from -# the main dictionary scan -# active-defrag-max-scan-fields 1000 - -# Jemalloc background thread for purging will be enabled by default -jemalloc-bg-thread yes - -# It is possible to pin different threads and processes of Redis to specific -# CPUs in your system, in order to maximize the performances of the server. -# This is useful both in order to pin different Redis threads in different -# CPUs, but also in order to make sure that multiple Redis instances running -# in the same host will be pinned to different CPUs. -# -# Normally you can do this using the "taskset" command, however it is also -# possible to this via Redis configuration directly, both in Linux and FreeBSD. -# -# You can pin the server/IO threads, bio threads, aof rewrite child process, and -# the bgsave child process. The syntax to specify the cpu list is the same as -# the taskset command: -# -# Set redis server/io threads to cpu affinity 0,2,4,6: -# server_cpulist 0-7:2 -# -# Set bio threads to cpu affinity 1,3: -# bio_cpulist 1,3 -# -# Set aof rewrite child process to cpu affinity 8,9,10,11: -# aof_rewrite_cpulist 8-11 -# -# Set bgsave child process to cpu affinity 1,10,11 -# bgsave_cpulist 1,10-11 - -# In some cases redis will emit warnings and even refuse to start if it detects -# that the system is in bad state, it is possible to suppress these warnings -# by setting the following config which takes a space delimited list of warnings -# to suppress -# -# ignore-warnings ARM64-COW-BUG diff --git a/cutejava/docs/dockerenv/redis7/run.sh b/cutejava/docs/dockerenv/redis7/run.sh deleted file mode 100644 index 1f80b94b..00000000 --- a/cutejava/docs/dockerenv/redis7/run.sh +++ /dev/null @@ -1,2 +0,0 @@ -#!/bin/bash -docker-compose -f docker-compose-redis.yml -p redis7 up -d diff --git a/cutejava/docs/dockerenv/redis7/stop.sh b/cutejava/docs/dockerenv/redis7/stop.sh deleted file mode 100644 index d2ea1ecc..00000000 --- a/cutejava/docs/dockerenv/redis7/stop.sh +++ /dev/null @@ -1,2 +0,0 @@ -#!/bin/bash -docker-compose -f docker-compose-redis.yml -p redis7 down \ No newline at end of file diff --git a/cutejava/docs/help/@Validated常用.txt b/cutejava/docs/help/@Validated常用.txt deleted file mode 100644 index d340a6ca..00000000 --- a/cutejava/docs/help/@Validated常用.txt +++ /dev/null @@ -1,34 +0,0 @@ -空检查 -@Null 验证对象是否为null -@NotNull 验证对象是否不为null, 无法查检长度为0的字符串 -@NotBlank 检查约束字符串是不是Null还有被Trim的长度是否大于0,只对字符串,且会去掉前后空格. -@NotEmpty 检查约束元素是否为NULL或者是EMPTY. - -Booelan检查 -@AssertTrue 验证 Boolean 对象是否为 true -@AssertFalse 验证 Boolean 对象是否为 false - -长度检查 -@Size(min=, max=) 验证对象（Array,Collection,Map,String）长度是否在给定的范围之内 -@Length(min=, max=) 验证注解的元素值长度在min和max区间内 - -日期检查 -@Past 验证 Date 和 Calendar 对象是否在当前时间之前 -@Future 验证 Date 和 Calendar 对象是否在当前时间之后 -@Pattern 验证 String 对象是否符合正则表达式的规则 - -数值检查, 建议使用在Stirng,Integer类型, 不建议使用在int类型上, 因为表单值为“”时无法转换为int, 但可以转换为Stirng为"",Integer为null -@Min 验证 Number 和 String 对象是否大等于指定的值 -@Max 验证 Number 和 String 对象是否小等于指定的值 -@DecimalMax 被标注的值必须不大于约束中指定的最大值. 这个约束的参数是一个通过BigDecimal定义的最大值的字符串表示.小数存在精度 -@DecimalMin 被标注的值必须不小于约束中指定的最小值. 这个约束的参数是一个通过BigDecimal定义的最小值的字符串表示.小数存在精度 -@Digits 验证 Number 和 String 的构成是否合法 -@Digits(integer=,fraction=) 验证字符串是否是符合指定格式的数字, interger指定整数精度, fraction指定小数精度。 -@Range(min=, max=) 验证注解的元素值在最小值和最大值之间 -@Range(min=10000,max=50000,message="range.bean.wage") -private BigDecimal wage; -@Valid 递归的对关联对象进行校验, 如果关联对象是个集合或者数组,那么对其中的元素进行递归校验,如果是一个map,则对其中的值部分进行校验.(是否进行递归验证) -@CreditCardNumber信用卡验证 -@Email 验证是否是邮件地址, 如果为null,不进行验证, 算通过验证。 -@ScriptAssert(lang= ,script=, alias=) -@URL(protocol=,host=, port=,regexp=, flags=) 地址校验 \ No newline at end of file diff --git a/cutejava/docs/help/Controller命名规范.md b/cutejava/docs/help/Controller命名规范.md deleted file mode 100644 index 24f338e7..00000000 --- a/cutejava/docs/help/Controller命名规范.md +++ /dev/null @@ -1,8 +0,0 @@ - 操作类型 | 示例方法名 | 请求路径 | 说明 | -|--------|-------------------|--------------------|------------------| -| 查询单个 | findTemplate | /template/find | 替换原来的 getXxxById - 查询列表 | listTemplates | /template/list | 分页查询或条件查询 - 新增 | createTemplate | /template/create | 替换原来的 saveXxx - 更新 | updateTemplate | /template/update | 替换原来的 modifyXxx - 删除 | deleteTemplate | /template/delete | 替换原来的 removeXxx - 特殊操作 | exportTemplate | /template/export | 如导出、下载等 \ No newline at end of file diff --git a/cutejava/docs/help/IDEA换行调整.jpg b/cutejava/docs/help/IDEA换行调整.jpg deleted file mode 100644 index bb6b19145ef55fc3e98c742b0990177b533ad578..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 69216 zcmeFZ2UwKNmM+>PQIH%Y3X(H|B=05k%+;h(qln-syS5+%~t5&^hRU>~Qmq7RmGV(GY6ci9h4)_5f zmqAaZ-7U>QASERb8wdot3qlF91fc_e0bM{8Km~zNzoP#6KWHOg(f<4!we?pcvKd5h z7qt~_1Pz4_gi3&dMu38B2hjk}W1##|es%g)P*Bm(G45dAy@!Pjbg0A!p`xInp`xQ< zV4wrjq4)spAanu@!bd!kcZgKqVA44d^L~iVxJ&=6tc65vVFAH8i!fb#(PiOwG(K-db8YIlH*JxqEo}e+&o=`V<@z z6Z<(XJ|QtFIWy~9c1~_ye!-9Oipr|$n%cV7w)T$BuI`@R(XsJ~$*G^yGs`QhYwH`E zTiZLwC#PrU7niWB>tA%CfYAO%7Vz)CNf!Y?7b-eB8an1Lx=>Kvei2T9j`4`+4xywf z<{JkhI^GX=iJwJhl(pQWf1-9oV(d7AMasap%y|5Zv_B~OUn9)#{}yF`C+r_|&4Q#r zsDBhRR8%w!G&D4fI~YK@bN9}#au@6F9|h}wmivDc++PLn?*$1Af&z?zj*gBA{NiKZ z!^Zy)7vwykToT9`(0w!%K$*}8KwuF3QdEAfQB(^F3Ouv5=rk1kafBCSCnox>f8k-% zRCdEL%6Pj?ve%q=>!Yzrt-1JNzV~GBACcK{Y3ip_vuy@>E3Ks8g})l(x4&!okZjUE z`zYWxwqs>Li<7Qh-)L@b=2hZm%F8j$oVRA~t@o0uMC)?YJ-w1_ZojY(Fw8_G$lul! zCtI8JceEutugsSFP#T$Clx?^o_>L=wS_h<7_B@&1^ZAJCl@EXWlq$8)v~e-BvLmQ@ zdg1Yg^9v6b8P6+L^ysZX=Z1>0bBqAaf%EXVFs6tL1& zFqymC@aC%o%9Z2A2WN}?kM2wwiBW$1@X%38_K89kW#Zk4nUjY-*GQ1!(DkWk zR=v^G&^25owRo?To7B9*PrjqUTvvhh4b|)S24y3Xw5G@1#X4f*?ned#UJQB;m6eJW z5qpV-8^Yw8&#`0=@8Q&#_d@Uo6-q%3AtzTVHWy?2CN zk-C9YZozP`;2jdg1+RP01J^CK^t|}MkI3SRW{0#2n^5P*#PbX$M9=ASY_GSHJ~w;W zqWK<0(1y}YqgYR|6bZ6Lg1So^YB~=Vr>2o0!AlxGRU>6%C?bei*t}+ zYvJTZ^6^P;bYuUDObCWKsE0O~A*uka){kBQv-jH)g^QDNS&GIuXT_{}FjIZpBbl_f z`ztu~7`ip?@V}nkCb&n=L3VWM#R&SJL|Y1 zKf%2IQ4#^bxHqkkqhLsD_ zw=_>DvrGgM@?LFMa}o_$vbXM|kIX&S6JUGc*gixRB6np#9v8$WM?1`$O04=c5;+XN zq-H%$(Qgmn$C2oS&1OUh)cvTcae3B%Bh^PKAozsJf}E*ZV$1;v5;sCz^R+oSrJn;@ z>_c((y(VP*+dO$qbxwG(sO6T!WQKBP#VW)=*=x^}`xaCY2`8C`94A+c9lqPy%lkk; zuNh9trxE^)u7DORLj%|ZUu%`llt4BMk)TDH$jVnp(2zC~)D&)SL>^rDP@(cw{Dp0$ z?=@7wLJ>y>FBxC{iosY_A7WLD1f~740*MKyzpaYDYcFY}KTLt$eqS4WI)MZoX373z zWYe}Ja@T4>Qf(eXJ-Oi_w4&&`FT8bM3Q)rMHT}5m-x>1Xf2y={4!0b9d-nFm zpbLIsf3r1q!SSlQBeSY$>X+100IBWXnUjtNPfX21~5c&yZ(fs{?H~cqC{#zOT`!)CvSOze11O{!p(5mKD z5uZ6!be^w1VnFznLM$z*D>?x4l7Iw-k4sP^L6JU+h?;7|`*VTMQIaMeg^E~n;^op* zZ&z6;47$8`1P zN0Ff8I&eir`t=>|+cPNKu9!WiHg~><1HaAbExk(&gN|n0ya`K-Ywj^BE~ZqBm-){1 z!`zG)@z>uJiDS6VRq2Fhf5O9l4%wWSXs4`*mexX|t1nz04jn=^bpGii-`{56mVG*C zT1QAB2C}Aa58(rc`<%>(521j$&Ap&-lq@lejijUm(p33}fJ54ug2Ex%d3 zN=cv51K*-Pf=?kqp8zG01(e`9I2lk-{-kIkJ&sTxinF)w$99*cHpUo+L%-xo;s zo_ZV4P3$DkU{CS!&O4K28l7Z6)OvjA#6=n=I zG<4*)-rd2F<;{pNNm{bBc&HH!ye3q*usC(@v~kV83!#KF9w8E(RuyrW}heKD~Hp)8-1P8FzZ&&iH{edZ!UHVLklah&8Xf6 ztks%@*@RC+T>^}?W1AUNcpIU`rB`@yGf2>66%xef-68E&=Q||9pYSS0Ch+D(Jn>_5Vmwybo6-E-o3Qb~OGn4ai4EU7P8{ur9ea91 zGs}8_lXE+*b9hk}T;@xctW>_JlAPN5Lp+39#qerLo)!|9^%f+tLs3POE(Q!R` zW|C!_!T7MuW@|m%>|A}l9kqEJx*5clq*q=C8vcEry%uJ&s}QFi6gh_Y@GD=RMo7=a z>q>1zqYvJl%%)VB;t?(q^lHKx$D~uHmy=z!HVwQt8=6xMt&Lc8>>ZJ**ZKJ7^iA7q zqA(M&)P&}A5^Fua1-kFGWBc@p^F1ae4lX|~PAH#wcly!cF4fR)ymlXYb}vbu6A3Ea zJ@W|(qeL`9`cA||LN365ND%H>_4+)o4RBVq69KPsLa^bFB% z=8|`xQPTMNVjnXY@-z*f2UomxCVPGIdWum|G0(z=-1ny+cbrH8NvA#<-;RWVku|&$ z33?>yB+7MhwT-aobJi}W@k?W@oH(#KI4BCwjz}W?e)&w^cZjj*n+-vALQQ>a1x{9! z$D!ee)$|Y8UdK<`>ty}cz8@V1Rq*{-bjUYoa6RsEA|#3Ihw${(lhQixN5^3_QW!%0 zt2cA=vWk(QlEqDk)Os?zQ+pHjIGnlE$lYF7lKLQ>U7A*Fu9g}rdYr&dyb$-ZX>uK< zlIY{i5Y|usrKj#vEtvdKp(ZT9v?|?_w)*>zpO>*~cF&F95ypzQgnLR35N34VdN{L)K05%#RAql0hd8FiK1q`t3z z&>R3J59^A** zme)3o?iQpkaSEhSjgq-5=C4^1u71O7!Ifs}81@*B1ZD8&xu^iTJQV5+U^89pTV^u+ zd1DHeLW^FPP?NUJIFWKYoLt*RaV2(p0^Jm^aDh|h5K+nxF;z=Np>&%jL5}UKLM=iq zV%i)h^6YkTp;4e7VIee-FWLva#hEm~uSh3_&mut)s<-*ei&w|?15nud>yx2tFPcUq zC^~n_2!4~Wj43)y!B7*5yG+;+PC77z*gQZ0XWv1 zbAb2o@2y4kHVz3=F}Z}E;FW@}F1c$VN#W8qNYGyg{Od$!kg=bDBjW#m+`^ZLMiZ<( zwaO;E#YA-FB$9ryJ$y$J^1A-Jz=-@RI{~Lm_$q*Awlq~Ux4UwFSybhj08zI z`aaLhsHOE`okOkO_EV@l795ELQ5EPl{Yd`k zFgx36;wK?TJ6hF>G5-wXR6RqdFwrMJBdJ5VFtV`xwToTs7Gs zZo5P_6v!Xor?R&>UP7K#SIta#oAov-zq{9AERbq*bB0YHdcFx6GE&X8g_dr=^+8)% zjDQ|}Zd+vu{KyGj=JZzzTCbhsgq9CFV#W&wo%QaY^XCihqvRM^)2r7XeN=19+lEYg z_TRa9$-Sy69X{fRSjrg`2<&Dc`ttayAS90D)|3B==M=oVj!-<1@E=Er$~xBtrslvr z`1UE3a1C%fN4V0YtYRO##$`KmvXfFjZZP@cr!w?eRhA8Smy2iNvqYZy*VEiR^iEP! zhu&hBvD+FfsWb$ zv++(OD$b8jKbK5PdqHGio~x=5#zN@1FQUoIZ$$t4?CfOrKqBR+YoEk6Tl(vQduVI4 zwdZ1x;p$#B5@a1S_o+njfjVK~Bb%}|fv42O53MRA_i-E^_^AYNpVjBoR!0DMeZ9Ee zPV=+!n4XQ6JA@{bf*5u0QK;pCnUW;=&DBzrk)WybTW8r!xWI8*=u)_`t-9{;tR4;- z{+0HR?NdpX*UzJe?((vBYP^?`+#GFWTV1_vDlCP?0RHVmGR0f&c2a?hJ7fDlzC~x} z_rJIlvWPCf3xBUa}HeUWX|1aai5A&_3dBiNtYdZzt%&`&5aO z=E)Jv0G-w<7n|(e3wVG3@FeW)l?%Ei8Q8KXC`3%Q$Y6`NDrJS{N4?(cj+5@t{mHT- z$@qhLg5K{myi2%Wj+{=4i5H5iC!n2+YfYY8_of-@^{?TLeB%qp$~6m&$D|o0-{Ua$ z2I#(B;0mS^jJ4YXc57oSmdyA6RaFGHNX3>{Qsl*P@H47?yP#b~7Z?7u0f%?9sZd&R%u4OQkq1VO!6cIBEhmb< zZpYUR7T-zofRH98P{vs#(y$s~zIK$@DSu76Rok#x`O3LoC?k1e=XlIhzXglb!fdXVy!ocB z*e>qkiCq`Av}f^Q%OXW2m9-(p@ZPLuRc@pl}BvoB)=M z+sGYABN=<6Oled__WXO*>-loW?~bLXRBz<%tv(I#CGVEmaT;}>6tIso!nltmXh@`& z^7+UiRm>mf7$jFrPh>IrGx{YZ$$H)lVya=Nj8b8x%)_lm*(PQXV?2! zk#;I*%puSc_ybtVa@FXR-tfZWjk){2tx76(;Q*HaJ+JUxeKC9X#o^^sPH^$XO-ly? z5{Lx3srTiT${l02(gZ(zP+kt5JY)SD^s?rLfl`;zl9}QC2YPdxGWF^(LCtQuN-ke? zxK737p0}{Xdn9OvBFs_gzBM22{dcQgqD2Appzq|4wG1dd9a!>vfcZj#I3+u>y0?lC z31KFNN4{keA6E1Q%AnPqu%G^I_x;G_wa}euqYaA-;6!PCtyOyG5d~Z&rHE$Q;0&GO z15;=>f!-XsN(#esPT=?Oh z-npnoOfsLJcVYds%^msf<2Ci&TLFfH_rbZlq+-C+K<`?A**M;DyIfc4N!mrLjJ+7z zhr|{`8L}7@Wrd#0SzyoOMEIapH<^`{}?a0#b>RyVvBa$~6N#WJJw;j>Kr91--crU%=) z+yTpm_74PLBAM9VPOqP7X9BSQy(Zc%L6Ow7(r^3~GtvbMbA^fovv&Ixa^Hjrxejm# zeu`0PeSzR`pB>)Yo$2~iv0HPnSL}S#r|oC0jw7Kuc?rG?#_7$tLyR$qb_4CN`l=EY(XIAjPJV>zH z^|f72UG%tM%MhHt@0VPPo>s{=*3N-BA)ZbmLE3=-JQHii;NhBY%^9~k(=X}X+@l`d zJ@ii8TA~h*7}D*yia-Gn1gx&g%DSeyz~0^mH8nLZ5kjkKg9lw$1z9ojODL1IGq%$t zWriW!Vv@_^_HB2#_f3Or`nO8$oiIi*BPmDH7UW3`9C?eRK$2bjhEq=)8ix7t2-=TB zZ3V2|8Pt?drs$pp$UJ^}65%LoWAVj2xw6X~*fWXSf0-zf4Er~m`YHJq5eu9hD6tN6 z&8ScB7P+HaM4YGV0e(?8#T256`4=ei_00vg(e*uj0P=bQIj)mv0WcLwcF4_!Jwnjn zL68JBtgEAnI}Zj?xzTKJBui@e8H)>Icr&l^Ow_n`-$Z)C8w_DeDw=7`9yd_!6xxpR zd@Qu&C%I=`Qf2TdSDD{RJtnNmmM=Z4GHF1CT*k?Hm2a(Dd&09Y_@B?K|B&=3Fk_{v zL7D=-_6DO-v2gnLhzoT%#-+aClzYa{P?TMrnhF)i4scgc`)F7QVNZs< z29B*?vg1_**JyPfyA)up8=76i{@{DE1QjKw`7VF6v!%E$}ee=vkkWZmbfAk#0 zm_x~hL*<0!3+oH}nJ&@yOTJ&ma{UX1M5042A+ZoYrRzs3M9RD`W6L2M2^*tViQs>4 zq9lDS1kHqLzQeqzW%OiEp*7)F$ z(TS-VgbKZseYCIF0-NbEle2u@NTjm_E@!&FspnCm>WlbN@uHc=W+RHo$8QSZrv=2` z`WNALk>B+I=_)KDu2KN_cG8TvdF%$G^cEd3Vuwjk*gVZ|%P;C>K~wpSSI)nUR?hMj z2mITJBfpW*pZT5-@mI}}{mBX0Vzftsya#^asJtPd|Jd{{#1|48;I|>}2lV#|LhLAY z{GL9VP!R&hsTK=C*Kk~rAR~Op7U3uwZwULCH`-BbCzJqn9_HKJm)qqSfBNddbDbW_ z#N|YyN)I8-Jn9afhi1|~B*)AbF2^b#8SBRzM8b>SlEyE-^=cdmeAys}b*E=`>b-l< zp7o|4YKt`SOO*eliisSDNmN#lpD7yXVW;EIDtefZZn)DqP%1PNe$t0&RG|@czgqpG zrNm!1^~+JHUoj%I@@1be(we{uVk_&SGO>BtM%F4#fdpaEF5$JW#aNFZDBubs2x@mX zqv>qvLTk^iSi9(j=5n1-X~u7aD0JmdzIfMk_1+UN?0j2X$0w_wZVyvj!3#hDyYc0x zQs=88yGKU>6D7qsncsMbgU4Ab8Rz`hzkpWJK#r_p)T_|D?(wU7qZOh0FgW+}&|QNW zJmJ*`qn(4{>}GB<#Sz4g4bGq?Zz*XDHu=So+rtzicv1p+rM)H$FgzzL*ONo5U4DG~ zYKv0kWA;NIi_c8H1toFjj!RgaQb=$yl=O;^Cb3JtVBP0*m?xLFfh& z^v#Ff!@!n&nR8yutYH#O|+oy3uZJd@6cYh8G zIeay)T%7-NQM{UA})EPzn`pK@^0EI$(FWsqv*Wc5$;{1U7sn%dxwx+ zmEE!08B5QD)NgR9@5iFA46FoPlfxdwC~~lp^k*>WGBEM5=NUUiF5r7b&u(+NU4$Hk z;o8AP?Tf9S%vl{-y+|G}OSC0@z-3aQVR6!eo_9vJwn}n5z+aGwAelv=-Qs6oq(flr z=N3~#$E(d365J!_sbp3IIr=I-ZZ7tmX(=cV9z0GQSrI5C;<<`ArH^@v8N>eZ2-=PW zq0MfkkqpC4a^|hxZIxR&s@&9=zqG$&>^^GFN>A^oB|RIPo|5f-E-f^wc<^1g`W9j^ zlz)yF?t8E1*e=e&{tbZr+&%N;>#>cwV8NlTgVxB;0?JOiMiQ!;WQ+xf$_;q?x{o**n|s8k zYkYwjHnOBRt3qfkLGyirsNIk!WP$RmE{60+wcJI*2^QjbsISuPL(5QKcy5;j8?0%l zD@}YtOg;DB?oU4{3#L5^Lw5cJ@X9;AyS(5jTs@e>Cgs zJzkdXysfYISh{o4{8FA0n*QBAIRf9}6!vxLo#Wv`x+!K6m;i)V$)uqoaV!fD;sP(x zT!ZrdFLTW_nplvasP!&58WQxBWN1o!pFKihr)wlQ8-|64Z>g7)i<^{dl>o7s&+UTX zW_$}C#kXbjppTIxRuOLN;3yI5Bl)zF-?id3ga@;4Uz}0Ocx6pEx2;d>ha=%-o5$rA z7l<~Q5(wr?M$fSO(($ZdH zI9gt0fGR;vxAPLyCa=xr%{$d^YG`(pPp?`-ltuKfXBLlqBozUilM)GPKC3p_j>KJr zQL3dVPM!mvmVu)Wh0k|-9m|WH3(+pg4UX@P-yA95#1VE>)`$sfm2h_n>M6}PRWe1J zWNmMi>u{8HIp7RTC(1HiRC&2)`1dm3z6(b8s@m@^rOf=Y3fUb*f{r8(TFCXUPpZ#% zZUQX(02tER=o*#|Fgm21-JHdDI=c&9t@B44UznCWsaR3Sd;C}LJ=D|Q8p{^ItUBA; z!PsU;$CDNNyhm0!tG4I8ZHet{wP@&RDpV%^1D?34D~DKuA;uMD28)Y3gzx;1UxJf-7<_rSxzX30isqh8tKT8jLAoVj9Qv>#bRP zFJ||-(#-|RzPKC4I5@bLtC)>Q+e2li3MD=rD-C|2hKBKr+PbzL-nc3WynPgC(@Q9< z?RriNlHt`Le7gR=*sGMRDETsCkIx8SR}Z^p->f28m;S_Hl0m+z_C8r0rNfZ8a1YI6 zi0M4UcM%CfeS-w8Z2gsEqv;eHGx+OzdyAU<&|4@(!%vI{TTiWNHhU}%ULYk}27miMA9<=nl;3{W9IC!OF$O)agJjITRiCkR z6ETlvQ1?8ZcrM`zgR-{;~ykMVRd;IhydG(7YWQ&gjO%|Z4m8u0&q`@+#wFu(mhYk}*7P{CLyJKusG&n(=XHa~C)j>ca_ z@|zN8E}KmFvU(ejH$BR(O0^}@v5aODZL4RJFY7TDDM%ysWlqD4lm7Mgm0rXAfwwRI zH*HhoFftiqtd3i?WJ+dw8N-pz#_lKo?CDKwU~^Y#fdqVCrLFYn&CwO>R0B?#f{QwTz<1@^R6 z{l+`je1Q)nW4|*PwPzUF8F6+qtbPUKPi1>cz-m_)1AXc3iQSFVT^iz_5VsneN0`!s zKI9S^h+rJ^ zR&`ps<>gtyQSK3ZC7aDqZK!x3Q>GQI_8v+%hNRG-BYSdeTiT-l+cX2NZPE)ZKh$9% z!v65GtQV0<6E$qYnEnGkCQFM{-fTw^*((Fga>w+#KX*rG7iMmoc6!$F`_W z_l#%Y?N&`VBy<;P!av?fU6F4vSrPZhY^pd4%({h|aXfCoA9xfYNAgU;VDQA>g>h&4OzB=)mKt%bXHhX&oNa#Iu6Q7Nq9ViBaRn%;trLqXU>#PmeBe&4lmo=kC z&ztmj<>1?21xAC7LnBki?A8rs8BC%z_zj43hq=M!=eyY90$VKhY#YphO2xzb?{M)< zLT-lSkD&o@l@%rB8_8qz4!%XqdHp#n9x2E2XWJ6q6AuW*`ZcImdCMV{Y3Y1$>*M&K z6|Yh}%Q~h)!B5&!-$_rc5(pX`=X?8gVt#nT4E^1NhnVw&RJV$uS3O2YMji^-+CI=; z5nt{DF@+G8Z?u^qETEi9k>rV&b1!U(RrT?Ip&)1F5#PkwME*$AcGzOA zSRGb>iz55GljPyPYnZV-bcLo5X-0z11itkKZ!Y}q2T86(Ug5riG=tAjUfnt=Is)n6 z`Ji8O|8G>$kdrV`x@2Wb)@NlH?}eyUvON_9gt-`r>-Fv6)U};n=JloMaK7W}cC7}Z zJKNBiJ8f@LE{8kH`{%1~t#h0z&W0Mb6C()gx{ilJ7F&5>_&d0KEE`Wk%`{$`G7Fny zQ3rao@qm_AX*I3Wv33O>vI1G!qH4jmF8sCnva;`bW9l*1v*zxipJ?+p7Quxl_;l^| zHpV%)__3ALZ&;?Kg#~#P!-CZWG?@r}4K`^6$+DeCcOj=ng;M28SCE!lBC+d`u}Nni z*|zKAh2X-rHN&6XBT5g~eM*AR?bI|@#|hbaKaOcX9aHXyngDyn>ly=r6KhE~BFV>r zGLZwpO=tEM;k^#MX*jCXmMl5LL2IhfFEX>DN&3NbVIgM3jaUtSzGMCJzQeZacu=!)OqJ z<4LMwHyt!5R5d{25o8Os_IgW96-cn?i-ch!-m|BdSlYc*l_sJ6o7!rTj&ARpHp&?k zFPq9nv9grX8ix!FlVY`_O<_{wfVBTN(Ka;X6pX8`6w5uw9>?HC%xpFy$=8p4R@gnl zy*#>m-9Uw9HBKyo7mr=qGl+Z^R^H)SSM>O;#KTGv`=C9t3er6(MTU=Wa#Ncr*WYwy zM#jlJNw>aDt2E#pYHJc0D>>w2;W~_O)^A%OC$TXaUjtyO(e3`aHP`xE5y$SMlxV|5LLr>-**H3BZ;40xA0a#z@ZnfFh4dXrCT86c;x0%&X?5@89%7L#cO$_>%Rb4Mt$qFR` zu!2!%d0W3M7E0IGoUuqrrLP#jE9=DiYO!Zf5O@v87C3DG0e7=8r@Ln%q!MV3@NPlc zU<1q$@R~4?{|*9LF`Ui^ID5q>7d0A>5`x6oxk3vT-60ASOKFPpQi_p+gbNI#j{;@~ z-q(bqyN7k726CZr4(>s);gt3+d2_I-SC2L(OU`PP8XRZg7wc|9feVAjir_@7=KD`k z-fx1r1GjuRjfRfx9QAI zue@u=5V=o2=sjN~xan{+z2jqLQE2OduvUqwJF9-vWeP1$hlAmFJX1^GH{f5p##)^& z4&_^G>BWs}^E5cj%Gj9J5X7Rjo4#Rd<;Bi;<`h3TyzjKU`GHRb=W&X@+tiqH^*BiK z-7$0qRV4Q_M?>WcIbx-YAJ`~ylvSnSIc0^C@BrXG9mPil| z5`=ju?)LHs&#&0qtl;fC&dUpnAQN7r`8h)=tmPU0X9Ba`-6ZKW3{DL}WY2qM+^1Tv z-Tcq+NZuyDICL=Qt{`9Wcmg#WNF8q`RO5AklJjJUE95VEa3+MnRdaTJ>?XUGd06Kw zWA(U@vYm{b65-z;4j@Z+9uafl~zSDQn6l#D*`BsMcetYR=zpE0a!Mm=)T9;XSu?g z{@ZVM-X{-w$Zc@iioM&kO6={q^#mKzb0`TywoDhs-IDewnf{w({x;9-u7IamtKk6g5bu0FmkBHSGggzkiuCs|!Cvca z{9^n^3!+8@R%0E7;%Of|EKT#O1$H^xUW^4rm3{aqMQ}&6JyBS#>z&zYu}Y`!}=2q6~F%VGY@z)Q$DBjekC0IcIUd z&FOWTj7om?!vsVV%}K)In!44{H6TE=1Mx0xnC@5ci|nuNri*h{6arol z16P@$cj-)dRyUL4nvPkAT|8+%NKkFh3yaDHERKGA~ zAFNj2FlOtVbdDJ@{{@1 zohOPFx~lmcqkMeoH7>Zoe9V>W<^ajJnsRf~cJLrlPma(z^OElGEdU^UN-e;M9DrjO@+hRT*%Y{e~vB4ZnnTDyOYOUbPp@)U0A%rS@uQYG7d!MXr^IietfdNc$t3xfdCuh6IsHr@@06H^Gjur@m+Pl z89@M7HHtFQhZs%mcx>cmTO~8@CEJyo@dvEwEaJ4=5{K5@A(sV(`Q7c_)_AgSq`2LL zax}ZE74O-UQdrzB@?>5rV}9f0aPUUI(?lmrfRNo$p$q% zamt0s%8yobFC4a46Fq9EuZb7b89mMnLm_`Vl5}UvHU>9E`&}PP#f-r|tT5(G*#M7z z%z1WSZ@rig_VGuN`U~wx5I1yNjv$Vw%fw$?gqnL+^44y&Cz8`Y^4a4JeY0|(Eb&{*?4!D2VsuYnBngX@go z(UBL=p__07kjvMd2E7eGazgl5LoeGPC*m|e7cs$Gq5xR$ErM7y?^={HLwLW0Wfa#*6%BC@B^-K05PDaB0TaHW=O`-dRhjRA#qLe^>913m_NFF?GGq#SLb6-x7}B_ zBm<%St6EecVe}iZ(3R9i!RZYd8MdWD+%A7PSJ%dnUzbDvCC^{{8nl4p=xvR{w{ z5cvV0Q2q^*zMr|b z*DG8R&o!(KYv{3ev31V2-YZNSRQxr(6&qZY9SFs7`70$&5qD4A(G<@^)3}Ay8=9|2 zGAe$l_YEx*TgJ14!i?y=8&1B|8h?o|VAt9&NhUyoUc0}1=Taj3l^F6Grh@P{%67t+ zG@%YzFyx3KXLvhd@;dP+ag4kc;;6ZUIVB4+RNRF?2U40Sil9G$H*)wz6A%Q9o<%g8 zrJpfp0Raz9BxpTI_11qGe2wG#`OiTe5q9A~E_gK!3_l%i6)7kK&E}EqlVLv;EaMz{lo~K%$X` zN1Y)2dJeMm402om{@ZF0z-po(r5+Zy_qJ}&Ay;q4|6BphPYEJm3!2(~1^p`-Spy@` z&B;|D^aQkqtKP;MA^a>ZW#Rs}UVY##71_f=B&ZMf&lRvBT8`3h??4sS;q#OTA3N~T zBQR{@;cv9<0XxhY5x5S#Mzg!1iv&IM1p62vbX@+v0ND#XVEJ48*V^10TZ^Z=!1?|I zKxk*)@62?G_w~!!1;Hn1E$PJMFchZ*k=PJP8y#Y~3mX6j!e>G1l}+~ zZ_$SiBCjy7FXJJ@X_1TCNKicW-&gUctm68v{=!eOztBfB4H)PxCWtd|H*cz;9P#lC z_(BBu_np5_|945182!%9-|0j20CJUla+8ISL^Q7d(wEDL|1@pU6fg2r+V9tLXc1Ep zEnp{)Yvy=&@1fqB#X{sik(hJvvH|Ydm5BNGQsJ9|X78@CJaD{q#5mtgG1vCqA(3hD z6~RycIf|TnYUIjy*9Z&_LtZUxc}nC8KB(DQw71641&a?ky5_+aurl&QaAeUtpD`D%of zz~TK&q8_0KHN8nD<{?kMyeq)npq6omTdTY@5VY3aooezKH^qqOv*(d=3hYMtY$5I_ zswEK1JiXs1n=ffIN|VI!v0FyOsVr#C+FGY6=w-~ChsAcZQFx!5-QHmydwA@KTd$UB zSe(}{XdM<$6ldPfj`|}#nODz|kJoJdKPO!-$&&KT0*?A?$X5HJbD{hPIN%$Dp0chli%D#x^ zahGiE>3M;9_{8X#kDigo!Mh>CHzx11K3w;PWs&7lbM^^7VD3Lt=J`@mIf-L8JWoey z9gY&OeImEg+o^w5J`ie-+~Ue$hA4E#WhLOn*yVFXK>qGGqG zrbk;S?^x!+ZOBDGvppZP7FXY?iYR6(nuz!kB-Wb|Kialp#jvjY_y#-q(vCakUFFJ* za+X6_Hn~7{f4ol^Pxu}A?~_pi=&{i?eN2aO#1IG1YNs&GxOmDj@~E!8$p$-TDfWj72o3H9lZw@ zla-qMrQMXM8$vZ=IM*HM@=tSLzms$bxSJ*Bzr9eJX%#awg#W!-!w=sWXRVfy6r+0w zWUNAlmct&UB)|A9W>ELXh$2BSo*88it&iM*fmfk0M`>wj2XXcH0SaE7GfhQ34w@EK6x^qe*X8 z7D+5U!v{-qtOctQF6$d^KG`uuSh`UUG*0*n=*Px5dgNQ4ja^T8EE;$kJ&QfO^?=vY zNW!vOnh3|el}dLP7#k9l$DC^_yxuOw%hM(DUC3$lF$g4hDSYaUUVGo~d$NkNb}f^V zYf1Bfuknd|t#zNMt>FY+yxan_84)*-ZLLEvye>=swM1_SK&r;h$@xQZ?5<}JrUc^c z+PvQeDBhz!DZImm`W{7S$rGzH;^ct6a-1%8bel@yM6B5Q3ilIB4Q1~I$S9&dt#8Gaxy{kCx*X<6IY6_ApcpI3 zeqI~a<+M3q^TAwaIn-^DV=XWnmdl4JvyKynPsx-;T*TcoNz?v1u zH6uM&mMNndl>_1evUq+DVutpu7!eHQc6}Qt04_Nbn-hP?jcPB8*Ji;_&2VF@0(CwW zf11NppD#X_pnXZW5E>lg^*LVmZjE~nZMW1N<`_YXcRek4DpfC=Y!QO+k|uNQOU@|- zs!?+7+-?)~QK7rQZu>P(PPPeSPVU1rlg4D>IDct|uxUBtN1YQG!m~TGfs0(FFOL)2 zgBw(`WHX*~FVKkFF(jyuQ>xaOhwIWmccM~=&T|ue7Ncld4Z`Ej_w!urJ25KmjVmg? zwF16P4G8*aJ^d3u{9g&F$Vo&ZL0J?H4K9C!V`#6zh%l=cd1;W9^eddXU$JD263@DS zfvyaR_nBV?RMh)8wO`AGy7osI&9~UoKSF6$q|0EFqZbl0rI@K2Sq^|}qI>F&XN}Rl zj^#tBR&?|`aCFFsjXIUvfkRz|N+4}B)fc$XoZU3-^xIS?oUVj=J0ys;ZGYZBY?ZvF zE8BIdiT`Ltx|Hifmcb14(`z1OJNvAfyNi|~OT6e+L6P%uEzEhst9NWt!Y?L~paAI0 z!0XG%jl*m5>!CJ0sx4;ojGPUlitH?D^rN}{1j5a}@Rfl1;T}JA$MDs-0h8SY{3&n2 z``RL3-c=BZ%KVr$kaQ!9260k~H^i{jpi>t~nS3#>kAu~E*sd5Dbx`>DwE;MLRb3`~ zw}G+10KJC=R<^%KA_ECMmD3naS2{kIm}&gQu0X-$aD897`UJ!HC%0x)@gBm=ye04K z2xXlxl+<;zMFi@t{jJ?ZY3Vr>j+P3!XYKHo2NvVvN68wv^)W%~c!=%r9{~=$N3#U(G0e1-=_}^KIv;s=m?D7~)=vYp9RS5Z8n+wR@XP zh_Jm)boE?uk{lOpO^j&5;7_xN2W}x!{sB>}3ANUm&(uD zE>(LccblFQO3~+>zak8%b`)B(C~k!LFBj9R*H#aEOE6W`OsHMl+H=Jph*nm)vJxvi zl9mg01wa0rp1|?+QRxm1h1P)&$(Tw*nmE}GhQxdxb`sWN^Y=Y19Xh$yP;!mu*b%^Y z8m1B1v1uWSpz0oytU`;>T_E6bJ^P^y=CIPJd|*v2!LA>i=|H9dt&ng|k@9fe9Be;8 zA=jz?&VY(StCii=3dP4^Z_~cEZi6_iNJnK?s5g&3S55S8G2X$o?=`LV%SIRsy#x9a%h-uH3*C1qD4`#ClE5PC`b9J^Z#wY!0+*@^!}*p303;Mvm)D~-TWcs`HW(D?+&AlGAaL>g;j{eeg_5HC zpHOIRnd#A~BJfPKZG7o1J&9*rph3>TU&n0pPP9TcjxCaP4`~I~`}6NBkUXH&ko~gB z;V7`_zGAKN-BN31@d2H9r|o89?|UK(Wn5*?(~zSlcMy$%)t6B2-Rt37(Ev5zy3rHJ z%?IFmJI(p+tN%gUTZhH9ZQFwoAcSCn;7-t>!5u;f9^5G;!QI`8Kp?nF@C0{LX=9puy0hnhDPsP2D65xPI>SI-` z43J{dv^RZVr;#lO4X~_)FqI~&e&u~9j%0<@C%gs0AC~_`LHLVb+U(2Rok>9=6``~9PG~EWOrMXOOpp4JUYfM+|x^>q)j&63YQ)SC^;dMZuNGz-OO#U88bIi5i_+Xs!gd<8EU4oP)S8ke=Gbngj z@zIcYFF#e-4s=DwW8|omd(WD`f^NKXbEeGhpxh{Cjv<9J^j+c_R(Rj5Z;fP5T$#cW zxe{yYCnEJxkp*S5^BJP6N}{~_-%{z_#2aOMNfVae@*c{bXUMO~Es7@Kwx4>O=Z#Nb zUVdgXVJ-rp`-W*gisN7H*1&nNwn4Nfxy0n_3af>^8b~SG`H6rHMAMfkSBAsmRm0!h zv9OGR>Sl)^ZiAMWu11m1n{_ao3g6YnQz2GDJ>Kh5;s`%S{Se>bmd&`<)G|7{x$z~# z&Nxmw^DVhaXj#Gf&i`hYf;GO6sdH0OD267kgVqE|7b5lqK63x% zCj#z0)b7UtxBW%q+@&GS)slP0qV&QVX&Vp~rB6KZnrt_$<&Ag59M#>K9MRWaEGrvD zesrHsD8&4QPFRYmvpbUZY0M5rVFVCL{9pG0*F*{>JX_YxO_;6x@j6P}C&mQO1PYQ*LR+_JvhZ$d9u zhWV*Iy|@XMdY(mkZLLPYx5#vSo*GqB(1C}}qLpPHu);ddVrccDgQoHEgQ_U)0Y;?Y z0iyiH^np6~0hsdI?}EGh#^>N_=NjBWdIsYg_2DV7Cd{M-Vk%nt?5gofnfe@SQ9}Gb z*alKQ#P;f&vES9vQ@O=%n!ws@R}`?=pIiql$)~DeR^bkC`}+)_wAixbVx zTumIW<3=-egYaHG;8}Ur61w81PIUMF3gz-aKG}jhWX=8z&1vQqPI zgZ7TdJLJb-wKq>A(&TCw<2W^6lJc)TG(_{LcyqkbEbh&;DEht_WYy&MbvGFsFD$;Z zT+PMEqMe^Dhe8|Ki@Dy(VRSjxyN>UkizqXrKxS`3iw# zr{KI6Rt`HqdkO>VgO@$6?kH6IHNq;tk&(#7=}=f2SYqk)8Tk&==X~*u(rm5=(!|tg zFBkZh4WPx>u09&pWjkUsk;I94mifwIP!F*~59S|H-7Pt?lF|A#l8#iMPhU-kh)~HQ z{2hG1a>wkYc9OilMdpj6&v1Pxx_?1=dcTbTE z#i&4r!KpS)c9~ONa}p(1Nsy@*Al8bMM|Viy%c~XXh!&}Z9_KiJLwFa_sH6WAL38P_ zN{(;twr$CCJwYqiNBReh`O9z)L$GOsqig=`{2PW3l1WKCw#%XU8>jN@h+Ypm3ev_D zuTE`!huZ5yuVn9UgYZ<|i2u7(Km{vTp2COx=Y_ixKsL?;z_6$Q;I0U;0sZm*cF;dP znQWEl$T~$11OVV$jv~%%U=<1juk-zbJVnsByX~U}FaewYU;@?+YYAVm0?jH@W&ami zX@zX+xCd0CE~#tk;1YeK#bnK)TTIWyZI^kl*n*9rK1RV7aPH4dX(_*JrKG&21I4-I z4e&P?H0_U_n$H}6d^+;g+lQAkxwd06EMheyFQ>(n(A-jTw>;IWpe^Gy310}6|Exlu zZ}y9>uMSJhPY|hcp06WjdIO!Sx-h&&VA$gOi9lY&O$x>L_^28!Up}wZk@0-mG`H9i259Z z{U%yZGe5G(`nLA0RZ5W>M}FYh?Md@~P#vHbW*GuugdH(K)|8(JV^G*9u{D6k zRS4YB5{NkOLeCMDhU@|LluJH{U^c>@VW?>mu|y;BJ@jT{cg}&@V_jrlXV;qxF~1$3|rDL+FL*h z2v{_4M*hbhC@Qdnf+j(}n9mZiGx{8WQip*y&E0l(4ge(# zc5XiZ1xx%N{zL?FmVaCBMP%VxZ?@X(2z#I;>xt<4MW&> zfl_*uNRJtfmfGb!nIpz*mbFD50}=b3KvHF9wVnLz7phm<-USPkUi)ZNfWi?mCztkn z86c3GC;MURjftKH?w-+oeZl;RMfsgnK_571133JP zPnkZ(FcRr+)JHu;F~WUGi;=1;;g4p7aFzc7IU|J(QUG`e{+ z0UU5xev7t#{#S-(xnE;JBe3zP`~RDFi8$i{R{c@iN~$6lFd#CqCiz$zIe<_*;U)@h zEdA`XKagnHU}90aSbL#kmDT#y_)mmt%#*5=JV*L%1~Av4!ihALc572|oy-BPCtMnN z%)CD`i`*>$oTw{PC$kc_fNL72n)l=3<1W7)nlIgoBFqBgkr!SWE)K4Fr0tj$()XSe z%>*_03vE!}{N1H@37De1AgQ5rwapGH>HtP}V*sTA)NhbCx1Mo1K*ioR$0kC9p0^+$BDc7gO3a(_tSuZyN>t9#jCc53u;Y06HMeir8Qen_pc;|TX{JG2>dt_* zl(X$iXp`TNq4Oy~KPo;pYq*uLa$8gNePO7}ZB1qQDpcaR>Y}pQPQwGlZeO(Wi0inX zeT%;0=>4v$Q^hD%J>r(?56kRv&g@4%?RR%;4i8!e_O-Ik+Li8>M=qI%Z&n!Yk1hLa zDQ6AA6*uu@P+aK7eB0IrTv~j^*TN#aL@^oD)|n?I3{~0PGgy0WgUTltg_e(qCNN#g zy}+YKL8rVtX#B-40Pfl~H{9vkS*!s=ww9S~(+1a5t4G-1x=*wVIBf{i0=y_phUp5i ztq)mO-}3jq-RIIJ8)?CsljmX3-V1p!i6v?NczFPNGpNXKm`sH;H%6ZmEd&E(-(T^K zc2mh}RamwNG*}|VZ8=lMy}cGN`|>e|b~lj3jFMjCb*4AQ{G6!++4W&u8C@O}AOW|g zN45eXg^Cf1Vdph{!82{^=0PdhHGMUOOx_roxwjClvq!zOC}un3@iEvusvTXkuF1j1 z)wSN*VUmJ+pzmx0dNLc8cSf!dpCXkMhXF{0f8Dx^nq!mo?d&&Vo?q$Q5>u`vtkUh1 zNfm|34Ui|fZk617kBg}>M!TNfSkr^U7^tgdm1TLh5>ymt>zTJ>fNAvqTRi4}8`A+Y z>Xa#FgJ2giaEDsv#v?)zK^D~iSzv@+7#zu~yz%-ideqXMC?X2-pr&1SYyl{yIIeq_w<<~lE7Qb$GxAt! z{p};sX$G|pUAJ({l~(y~!G)|#K#m|_XmKQCEodWy*6EDfCJs+BVnrn(iG~G%y1_dw zEqpH2o}JEeDkG`DVJltdnPg` zmK=@W#8o&(R#jYdKp$K&_Hq|^_0VPOxozGyCc@Nv=roKqPuElB`&pkOT|+~%ka3WP zc>`Ud{M)0sU^;&$<}cx2y&`l0Rp%aC%*z7jB8weUZb`X8{B^B2k$6#f#WD{#79d2V zUzuKRmBBoIpbzlG*U_uAjY)^Y zeKj%jGkP5x)Lqa^FJZTnZlcQR;`JwY;cx9|ljuBM#?BOAS99|CBUks}fs@8}aMFcA z7PM?@LBHx~Z_E#)y0v$#n+--)#KPOgbVR`&-Q*s7{acAA4@0p+i|Ye!KM+DVOx{ce zEf_n<)q2KpYcffzvlIw(lxHi2KsbhNc_VWyZv{KNF=4T@rFU%f@57}xJ;!8TJ!kz8 zkqzsKA|zwo*uMfGTYmLSOA593rvdA6FPwY0)mnkAp$rOwmEzWAK+Aw=gQuO>RfG?T z9evH1F!{=KUgdcC8f3Ii9#oKF2RT$u#yI7c<)GqX)PAEaG-ZhbT8T#9E@BTo-{Hw% zR+Fjq)H6VCI4#p>J4k5TVePP+OZOBXaM7P3-lDmV_BF+9@^F@``jIPN$j%TqVkYWS z-}$L8%F-khkH98ZCd4_i;W3Ill&l|+#*)w5ArO?aN~+eCOBxVRu9l0d3FNM>-|znX zKn{UlS(eVJf6xmqx5T_;?Or|Y=x%ul*{T?ttgleO3YWj;SZy^_Zmz9PMNb3qmu>PT zo#-#T+HogJA}_K>j^9Y8-K2W>LQw`!{MgzM)W}lDd`Hf^cK6DbjoEV@%xm2c$EU7P z_!8GM(9-C$V?)48en%g1=&4E7gv$WA=C|eA51@Ip3H2F4Not2NE4K5@YG@-8;jrPmt&v-m&O^rFq=x!^O0N$p_ROyh zH?4JjXir%0;VI_Xdb7LG**HD%G$lce`piL%L)Z7fXUO9O0Hs*UUiY2gDUq1S#D*iAlANG2(_7nAc+kw?5gP1Vx7Rb(%D7+#pvU4X%==^ZOto zWrS#N#igm0xeBM+satq0r$u&H^)J`+kH7z(n}&;(pe(5J62;5@S1OPF1sD*9_+B#R zBk&6n1_PeQwym7x>$9WZ6sxxO{(cC_0}dgU7PI=@jV06D^$|rPu#>s&A(@w_l`pmZ z6*)b>@)V#3)u9JXWzdFTV@q$&n?Sw`pF{4K2Kwfg&!V`N!jcOv=D^b< zITZZSYe)z5INX{+=1zLH%HCS^K22bh}+&bV?`|2hB$hEO_ zwDx$X7AnDUQJmroQoZl+j?Qd%Y~eOZMt5|Hj+L6zT{z7BteKtyb3Jd-ECQ1)7c294#^$nOd?kLR`&}N5orzWgJ*4~$ zwMI8a$)@<(vNq!Pt!tD=bKs@kU&;B97UTOn`@0(e3no;X_t4+3{ZvPKAT_zTyMe21 zLpo$#WE8VPW)qsN+_8zcuF2d>#GHW%{wkRKao@Zp^>p%J-!y9R7Tw(~X~7wC_Xnh$TjYS>L+)W80S$<9w=l8F z7h-3dVh-R=%~hpaA`O7uHZuaY_vpF1T)H~_CC_khMD!EEZw?NZ0EmQBLXwozM3gsY zlnr95%#IBA7=JXe4gLM0q%W@`z);(t2w-YJP+>14J9-}j8+H>tPkDmh5DyQ=2Osmg z1H-J9&YvA@IuNR4m6M?fZOww#~uv?ou z{zbR-W7w-NcsKU0ey!(qqrRkbRXe7B`0AY#McCH;IeZTf2(2XroSg={g!-S;FMm7Kz!*37nnj*{z8l-FKu!-f+BzI6>j$(#RX{cIg zJWjN@3MdXd!W9G(2ein`z`bTa5#Vh=`0mG`_a_#m`ut*$^O*s4zv!2Uq7SV%wk4X| znSIb^^Bx_HvEp$Yw76Bz<`ee`=(rOXlmp zFhXb^NZPY#W>!8UevpJ$aOD%yOFYJMh+Ep+n?U$o767)5lLWOUq=FW{StX51ay!Bz z)?c_fIk%?eFOH)OnT0KV>;U*4R%=}x!nW4duK2kj=$^%AG))|&Zu>$+=5Ee&tuD9F z4$3Fnx`zdyt(-v;qVdM}U$~BpDU<6IyQrP?Y91ZGB)uLI$W{c%9=e9747@HZfMlJ&!-{~v{9#ePoSK;ihCz&avwD0Y+! z3|vM4((=p(AV}}%yB#q=HjA-h8~Xx`0`P-lZ;~(bX>Mk|0Ts+zM!;LGJ@@BXFiFbe z3U0%jBLK_wW%!AJqrYKeDablhcNwy;PqK-3M({u>g^|)jN)R_E-JI6tVNFr&GF4-q z0q>^1Pzz@!IlIMoH9K7Z+*TLyLF60&5YKZ_@VKbF^W)b(Z}Sp{3VdX9oESjbMW0T7zVqxUoiOpE7| zxdy*gf^aVws;^tvf?x92U{L?oMYU_zn!5VtxJ7D~ zldgu~RsQco7!eQo^&m7NQXa|Dp|b*bIbWy(UWk*6<)>j{6EH&9t@wRW2;9x#zYqP^ z--f=YB;_BSrh<=mf`$0S{(i3a>FdBm7=Z}<&7oJ%?TDSFEs6}a2k zzuqVQoCO8?=$Kq6a?Lwk@vGz-$Q=)ls~{mPkOnv!8Qv33e2eZqj+IYJ6+CW?bX(XQ zPHv;MjIlIeOkG?^Nz93CGeYYl+DFZEaNU6tK-V4O;SF7|NY6w+h19VKj;9eCapp7c z=rZ{#1}Ar|A^N4mY2iUFsA= zNmF>%F5)C2g~@CefWZ4h8m9mzo~8!I>GjdR zeOTq_j8i?Hb-;x3!S=beOzNZn?RzvAhmiMJ^JH($zcLm%0^#?m4j{v?qBD<~nH>=G zfHmce!D+9nF^yMgGnq!%XJN(DO$(gdHfQ3x3Z#1PncC24 zVG6rC(-3{f5(6|%8Be`cx;Pe&8`+N=!VxftBm-$r@-4hP{z3+?4th}lL$8n;{%mw| znC!cXjiIw>JvM7GtC?&k=DI0K<`u#F{r!@O;$7g%n?6#Rl4#c837Q|tUAOijKH{Fm zJGu)ke3NbXsiYZFw5@Uc<(kKM@xIe>2bW*o$hZq0t3UW6-IHjxczHT#29jO(*OM|z zpuxwLlA$9dSC7HMCVT9x1>=U*`N49~omouJdbx}VNn54|tF))zkBQAlx_Jg{-RY}ggG;6aw zZLzE{>LY|+RQ@>?a64%+cvu^Jln-pj){Kq>kL3=F4V0wM-t2aHNOmR^^Gl-$2}&*{!s%UOgL?&}f)cWhH0aD%9yQEK_j7pDd`sy?_Dh z3xqtMO2ep|3Sbu>;kWj1`eIKwO7oq?{oZ)HD83^=fg1)KX@Aj40VZbP;P!zJi2h{) zq5CDk5}hM}FJM;$tW)oRjV2AK7gcZ%eGjZVBX>Wbt9U2u_vpKT6Na%~SPuCgT8ut` zVZ-3ji-B-zC0yVD*;WBZ7?KOy1Fv9Ch;5aMU5$ZHxU-IfceBn$Dercm*Qthc*OWK+ zl&z?+SDC<(^NX(`3^B$-2`+&SUjs9JYXVBSrGS_0xAY@hG)3{Hvy_`64CL~R4L`j< ze2Kiagx^g#)aTrO`Qd&5D=ht>5fvw+v2S5lC=*5G+o{=6$nqgbfzgW;dw|Cxo{Q*RC82c5k?dBoRuxjaM+|Pn5@530hq! z@R^NO*DvN3^*PWqKpL4y9ZstPiD_aUkrf?i9Cd0n)pba7GI8OOhdu^V>!j5l-9D1| zhpO@RLIL>4E6P8VvNa@Ff@oValN4A9HM8u1nIiJ0MwGMDSPx#`n6QCX=V?#WFR0)A z+}SEIu3ANwHgc&Bl=Z|nS4Q~rk~aiBtkJrBroC{eIw=rQYC`};F3wMxpB#0x(e`hq z`Q57JUNe{^u__r0anXH-XKe*#{wG45?HU<2d@Op!iaDcusXi6*00l10@oaHV!d^Y~ zM_o3E-!$5hpLUHkQ})m+bsBWX7&$pm_t5%d%-dclJC#$hv!2<35Io=sFn)iDf%91| zoj>{br-bzQMDII6$AafV%$Jjg_swa`ElOSQPBa`{3fs>%#z4|ZWMO@>zL~dfQbUa* zt>ZC+7<`jFkZGyBBdBfxIVXZAfJah~v#8;o&B2@^2F63Tw8!T<@?$d}M@` z3Oj5|nXSC-a-Wkg#CO@Q#eb=-W~7p52#1nz*GprqpH)$uen^Nktibu)(T^<=g!4c7= zsnyzZGX09Jdq2|KEO}_BFQ3MBWa*xoN0hv^yhYj_aYlLBfyP1(7WRy>^{2o>qfH#r zUJrA`G!eStFdJ9*lc^9N_EpAOv0BVWn6k#rl21!nY7*bZEj)L}68_FrueeG5X{tBT zOlYpx)~q_r6L)brM;^BdjXGLLo^d&`uiMLHwIKO5wCs?-f9ed#hlEQzo}e0x)-4eN zrK@LUW)mE{Z1KAWo`)}`s2z-xE*Xma zQ*tA3_|Wb@x#v(%pOm%GKbpw?jx|>krSWNMs8*wEcG0lnqQEW*%hn#C`RQKmIWM-+ z_(<2E*!Z#3_^KS0(M_-(a(`MNqjiYpmm6Vb#IeH&>gm@z6&K*4{NP7txJ`jlIcDqH zr@AIP0Ux{nbl_mzTo^NR7?@_ui2Y>(tl3asPHg8MY{l|kGC%|i{d z)AB<$>Nr^)V=Y&Y(^%ZFq5KyENe>!Yy?aQ=Cu55&r<%sBQ){+kb^40%((ZX33nd-! zxQnY_gi&dIPgKunAVV4cAYHior1g8OzFee7X?&vFLvnWI7PC0Q^~VGJNt#%nN{ z|G=K=cg#Rv4YM!Y75vyf(09R(mxWI_^%h4DzY!7t?Wa#2`qHEu?hlNWRroN-sw&bG zQ?xnLaRAy952WlmtuvD@?zxY2iT-W{0yC-pFzp83>8ljtO6)rMfb|Un!;kF1foS9Q zF>Yk?F%JMPlnKDp5dv-vz65;5K7cml4wnKT zM&>KM?_?Ek(ju#&Mj)I*N~Dd#R#6Xe9zL#lL>~ z3)cYrT;(HJB!FM3`luzhiWID{pQ6MYfs;=RH@!CQ?+=UIS>a!}lpKNLd}MLpVe#48 z^GKt`{@JZJ<7EmPK{L`Wvcg3KGFLVpOV<8Ut5_QEQS%+7Lw@h#-`ml2T76U36FaOV z%i4?u!PpoYY4wIB@>}nq%SSIT?W^^KdPoYfI{X(36 z;JUi|lsQ98b!$oDyKp~amrZc(b_oZKf1FN{QV!}FzdJ)x=RkE(?jnb z&tYe7xTLvkS>MP5r8i9*`by-)!bIf4PM5BA4F56(<8@-z&7T%(f=-sA!eB5uxRls* zL)JP>>n1Zt(i8meZAiJNi3Ioa1J1cr@UBh(OId|}zj*vV%?n`A=~hynogF9Np#F1G zs2BhQJah*5m!%uhp9qyXZ~~=!3Fs+sntvyKJK+zU!LvR0%i ziYfS?6TD0t`{w3a9w-4!_!O2E22`vYFRTC-mfz+p0AKv}B==Td!NbGthU=7n8S{(2 zVh~`iUSNw({w3_=!S^rIHe)_r6$!JfDjn$|J&Z}T{7S>t^F?>H$C2%^tkXD*@`hYn zuK$t20*v+s|ygU`)}(VZjbPft^U|}5w|$8MET3P;hQ6d`%7zUrGQ?`P)D9>C7Qu! z8#CPxil023G&~}yg8Xs{e8jHCmtaoSiTr$SQN z47F_mT)I>6l38^9B6!$S?5IYcU_l7}9*BG_sew=Wd4KQ3ei7j4Vjr+b!|sz8hujY! zS!at%cl)Eib^7x6>woX`AMHYGt0>Pd4ZQ`V0NJxB*N0MSD(ywNz=(iOXv67L^iqKBdq}L6yQUzCEWP0ZLuoT1g{`QE!w-xnPK#;lgw=PNjZW)39b=!%7 z#S-Lg1@88b=E&4!iUpUMpP+KnKZ^ut*#8W4{}u55Kk$hS2($ghZ2T2r*oJX^2DeMP zyIXJFXYJQ(xu?uQ-Dloex*5}u)~|^)EuWV=HQPV7_Tu|kT4z1;{d6~3GkyltSykxI zI_hap({JdeA^#59oPqL19(&N7w~*JIQYXRQgyHBd{GptOQkUw^-viU8s3T5zRfz}7zkLht0fYjts(3ib2|`D$Sg`e0ip3_(h&7m$~`Qsr$-JR6^0Gh zA6FQCNDH@9h23B1?-CHW-C^buM*(tY?rv?CnX9iwb*9r)o^BxW_p*!9U4zu7xbM;i zNJI9??aGfP@W^K~_C@vLSgcw6OsI-id1Kul^n1|aK->YA6&RZ%FAqpV*gfza?mcPM zlA7d3A1l~P;@X+AKq9g;vdBejM9%Sd@OISkH*T{YZKL&o$erlTGLE)%E3ozKM;%$( z8<$jAXq2RSr_y8}ClwWJw=sM=~gQ3Z$%C(-?_}!S)VOnGw*L$-7axnu>I=4xx z1y6y`pnc?InJ58!?MugrY&jzL>xYBfnn@!{_~qstnP=k9#soe2=@m ztp}~TXD`Z4M_n6SOw}Q7mJ!`=Y0-$?dr$pVOP*$8Nej0a@SKp5aHrxu?IN%3S6Q%K z1_cs3Qb!+93*V;&yV=hjgv~ZxSF8=xpvx9M6XsJfv=5t{W$-RULQc|(;;}Tu5N89q z`Pq!;*#a(G095`SE>#m}3pJcvDwy|@%<32bqguJ?)+OcIFOS#W`{Bm1pmB4~?EvMz zLEhnsYN4q8L*-Z!RBNIlEB2UkdpRm?<3}VNZ$??Wy1rL+Z4Cswh7$0HcN3>9NPpi& z=wtB5oLdTkv$cUN)*Aze$_RFhq85i{XSoThJo$)Zj3fsNkk@Dmzioa#7KNgIth2OZ zD=(-CSVeumNNT~Z9!zzRG`U`?M%}YurpHT0R{kj7?x+sRcN?alL$_oIg+(Q6UfaL3 z%vUP4Ozkkx&5tE0BlfnZn=x%6$W&whw4&qO5Tk8kOH5?^L;U!t6G=X;eO9qN8mq|r z%fn!qS2Xg4y0VU>wJGi@k63aUh0fAV5Vhg-*F|8*vN;0}%gZ@k%f5WbY#D2qUME@q zqG{#~>j)pDj|k%l)AG7mBj_k3lXINS;BZUznI%JQBRiR6=j(c$Ph~T1Ob4ewVtAJ+ z3K;Ol7F?h!gW&#!y1Nd0kRPvM+1;U6#>XITefzKG9R`ml%*NSxC~>Ce2wUqwv{Ek= zi*Ixa`pM#CXFDj}W3?gB$HF4^MLYGC*X_M?3w^>)wei}Xu{Rtki0GK-BewCRPX@RR zMG?OWlyj+EC$F(85-lg4GFz-R$!`$2)n9rvMGFBDX6Y!gMV}tlaUeo$gbt;=PQ6lw zjBk0Xur|g9NWZfr!y3boF@66GM^5`KM=Vh~#yL@jz5CR;te<6YQuPkF3v&AfPIKIy z@>w*;mS@kRpWA!9mQ!Ao`mC8W+GggFF zlT&4OqpxGS@Qn9E`X0TG#FHv4eX0Jq<&;Y=0|#ojcMESuF8i^w{~JyWs+6`g&+jSJ z1C@;@;|e|#cpFv~M4J&&D$Cl#k2F<}pA38d1z3JUq34fE6vx!OJxE5ijhi5>(1Bz( zq&3p_Qktk_6b{}|37?u$RV{H0J+(Ahl1Ai_6!&PztM+{(5H~^&Q5hf%B?m2H=%q)F z-cKSxDcP|;gB8KE;6SnG%K?ZxQP1nWMsKFL3~0SY``?9;@g+xo{XisuR5awA>6~d* zIAw;r4r-@5jd+GYCWRBVHgs^qIwWs?yc&P{tN5WmkL}V01cvJ!$!3{rX-Ba*#Ap=A zhJ;N28bu0UCp>oGt+BvmVe-p#&m)oVFS<~Z@48tulHSU39;nJtd6~E)rE^=ybGSAH zFo)!7Cv>j_Y~nvEeO&q0aS9ccAu191wyvvFt-U`i{?ia1Wz6fx*%cxPBB#D*sYtIb zvV!f8>By7x1qQ0%LFUv#m)qKz6;Wcs4BV$_Kx`&5S0*8@TGg8^f6 zlsNNT2Q$m&3Lk2_jAI;v1GdsCDtQUk>aKjqa_H9w3y;}^0=~oGES3+0tQfOXsQ+E= z(_i1|+~#uXSzoywM-H=o56j7y7kE(1%&ZG=+5xZY-UmP*zoa&~wKXHP)`~nc{3u9u z!gVdTWRN7kz&C8Gs#!B6m8qS)VHEbO_uUw1xX57J0^8W6h~_c1RAz)E{Ot~cZ@ zebc!zII;sTP>HwscVB)c6-Z^0HHt$sKugGtt~`bLMi*%30F6 zEyr2#{dY^OVVt9UQv3)FNI?^IIYJTVCXD(%C!H{etbi!z$r zUG!Y~CL5RPjZ%H5NVvU z#MOQx*jtI6_rPI5M5j|Dl0mw*rMh{7hdG6{jFp6cx&u3l+SA?kM!x%tLji5&76MWx zb>PbhSF~IO+)-aeS~rcjM<#E-ISxHocMzvK<$R7|e|ZT^fj8izPBDNQG&lPvLk@_h zoZ#bUhL`SAcvMz4G~Th_E-^8H*(;W2u@*m8e94}Yny@=CRDo1Aqz*j|rH`UFdGj_# z`@!essQgsfz()4}eAh|&<{^0ssdFmNa5jUIAoNOSX*`7Aa{9ND>-`S!fUs zI(j6t0;HzV_SNmwkhfc8#FwkyN00D$c?j|UC|bdAKVGkYu`$LCB`*RhRm#{mw-J4j zq=KRl+N4W)Qe!edt3FzjhwefNxt^xPh|vritI>P6cV9Q5kUGj+V}NG@L{C>4;fsIJ zRIdTnXh?xos?bjT&cK({z*g9u`8A*+jm+3k@2tN!-Y)k%z- zxSppimbE5_ZyynnrDrD4r#8&GSN#v;PTSHeO{YGam7X^Yk;~I|!(Y2_z?iI(ro!O) zWU6Qx7&tseCR{xMVGPhZ*5tm$*!c7SmF(@}HG&(+|lXqL}f(B6UKSKa@3$JldBFXoN{ z+5GvuY31&x=%Ej)5Xc*b(5R52^3(1E%Y9Q<&+Y`b_Ag6SErpY3NGnkEtAc16xN9+` z|28Z%P0nN;xs#ugkIHp@I`1=%^C%OsSNf>X9Q+8Kv(MI+V_sY+KZy3-SF#5^6ca6( z_*KE6-0=&vX9S|J-cUo%a-S+?B|MKsRPQD}6}3UY5@)3rDR<=7^2$W758K(V6L}*} z3#rzgBU(Gtl%=8KYMjrb8DQ+i@DyXm?-)i-8tb!tF-QAG<>ME%falK{D(7Vi%Y(Nh z0TDq%_(y@k0%9|SGE791p9B6+kdwN|KELw_;-!FU%T}A5-K1v^h21dtiC##&?`9q z@^YlZ@QUVa2RBp zc{_dw?k*bDdL6#i9oceOSNVlJKq`IrtAJhrGh zW9MbYN>jEbnPYFN>f(BPTp$!S93LFe0{f^aoHtJeox41P@Y&Fnl2^R_uogqHxU5fL zw%{(qiJJKq%C$1Vo^MTNp%uGM3dZ@?vhJdZ)G2FCHKIC$f8 zd0R5JIG%L|OR?5-6R8t#7xN=HJXa5hvjzkNY=0v3`F4Dmbw7Yx!=kf=dDiSPEoT#& z2J0JG*mJ5!4yFeADm$KmW?9@Bb-R%F2cG#Cnncm_o3TAuT^R0+#*~}VtSIKb#e{@z zKuL6TI{Cb8;+Tu2v6h&vDlIXb@Q8&?;te@Q)F&2zbhWX2F;2B=$VH7|yhy<+Br?8p z@={aGu4+OTEici$4nFGs`Yl34Uy;lZVz*Djlu>L{0=_6-hjexWCXn z^~PPMI-OttoRyqk1K<9)h{CTZ1G!kRE6A2fCok!C_uD+mcN}SlIO?J8jWFp*9VK#E zvbRM;((hOg-+Qk#+A;76>VKH+tnR@tW@+e@4PqLVdWg6j;C7BgE}R`kd2v;6iwQP# zHZ0oXfQi>+4JVoKa^5$Aru%h41_Yca%Pq@9^LUgk%FgMD0O{Db+|sK)%jD|FA-VqX zc9m4f+nAOz2B3sbf(_*R1M+FIh?B07SDJNA;0`2rXv&W2b*h5AO3bz2q9=R7B&9Os z<@-=oepS3U(6|%FVwI1rqmgT1zU52Sq*M$Je|OBT@LuO1u>F@bg%28TnLIVKre1#> zgkDV4j9`bJJF|HGu+AH&sk$Son+~44SBj0LzyHPyyAy6}ByAkjOzUzx6)q*vlo~xK z)zE&>ymA`ayKsdjMFSNP;AvOU01oa`hG$05iz{%P2w|5W2W0Z#FsWbK@BmHIGMm?} z@&j`mV(JT%WaQ&PNYv-}t_rl-zS12{w{Vmrn7nzH_bH`v}*AT^fD*O!}{PwXNYtO>PbM{s#f1&Fr2FUbq z@?w(3EZP03Y4|Gm2A%FRvSoI9i(BZq`{txw6{t1%SaKqTfGLXLd+ac}G z8l*!*KN)mgT_m^F+kNNs{-*Tggu=ZaluEIgEhlu#JcVZ;sNW)W?P=HfSjvUSWW1eA zRxD6wjqQ3Nm8bih$w9z5UWAZTU+4=(B_t{@!s^>n){&=H{-%|k^QUCHxhoY2R(@}T z>sP5>LIq;|QH>yEb`+e`_fD3N_y+{DhaAQYW$fHVQg8Nff*fM-;Tv?gZ%T(Y{mq+9Cpzf0#$H1$JT3J+hqg#Z0fQ9mvs7%#l2tUvESQkq)C(`^N}7(O3y$})b!*)o zP0(Z+fwW2}?tX|&imNH%W}2zc7{C+Sb%1KC_wS44|LS|cKbbfICD@)b4m!k_KH%s; z5$qB$FoLh>Iq~!H8 zBSYDDwE2m8lLptseI;{$ey38q_1-I?WJ`a=nKHy0&su%7+(;`w!ou#!9gnt!Z$MSH zmZh%Pl-_3%aC^IQwm)QmwnR&N_#Me+*H39kzGC@K$`x({D@ zR3FmP6{Md=6%5LO*fAmx*-{g;lYauV3b-%qR;FL56+r$7|As(+?I!lFm{ugZy1y_j z6yZs{!ViS1e4fA}3?G`!o}w;A@q3We?oVp#Um`odd?#{NJbYzW>3)h>3j2BvPKkim zb1)eL*r9B;qg=}h4t_Mjq_8B~Hj4Jw{_$sYtjY5w4s5;bYqcb~7EO`RAsClx2#xnO;Y!JrY)N4Z1xH9kmgC6J zfwz2A@-@G37CR;{RZ@oFwbWKOx0^BCi3W$hohRZGM-)>^@Z!zR8(+CVD>C}yFy0I$ z9OXrJ_EnP=IFs3wIv~*hdtgmno0hy+lra#gI}6X zmd`zXwwtDid+~nM3_WjBl(+4>GaA-cA`fcR6&qDauKDl*+BH6$?K*q-pxZfpe54)( zNahb8JZ#*b5(2bp!t#y!jGlNjR^#U8sd&YN;&Me8=x+#CS-SoqSGK!?;6eVVY`nCYKBih0_>I z?n34vf%Dqr|82ddx5(G{`3Jv}M=_6A7N%W-G-a>y$H4lHG(&z;gb%~^5_GXxW|IHc4Jb^E?X;7kE|*Fz9H*ndyxifQ6Imzp+(TKK$`q z=eHwhG~e~?X_o#+hZ)whWaB~ksrhdRlQ@P8>p8({@HR2V(@)Q@O;)Bvr4;h*yIm5F zz`4|ClNsB_vpzK}-OgoA$W6fmgTxMY{2%Y!Eud-_b*%GRD|2V>_|Y4NRFQ}`ILf&y5Xz3gR`*41 z;9#u-PWtPEiR5L4~@f)G| zI%XLt3p^i@#n4Zbb2lp#>e~5sm>3WUaVUF7w=Q)KjkDDdkZWzfclLHAp%&I%OI9iZ z3;b<%PLV!)314)az9Rb`?EONb%1dSxa`z|SKcXHJ4o--!=TI12LliqEm2)5^3r32_ z$At6Q2+6B%$*WDtY+ZJYkfXP2hhv8A*BMnt`&@va7mjW`XEBeUVc%(;*{_SX`dIE^ zid1EkdI=;v0((j0%t9Y^SqW`+??kj8j zau0qD*Rwc<=a@f+^Rx|m?KvgIRP(HeeQ9UxSXm7PRxrHE^2|W&BRc7pNC;<|Xod^@ z@)YyX0&ks}^AaBTz~uSC-2>&)!txSmM@Mzb8uLA9h@8n1S~!{J=3UO&v~kbBAv}Qz z!6?_0A?&eDXQoYkCBv$oFGtHar`5xPoAh4J1WT&59WZ%Y^G&(O@GgUKT#KKGY}3o+yFEn8tcoG7?6ESSk0JV5pNy$BA)>ned%ET>s@SGV{B zqT%}W1;i{*x8n4NQyF1Nc86r^iAR~Q+b-4{c9c#TtS>0JFU~0ijVBL->MLq|N_j$A z$Anr2QxF|!TQfOR;^swd6sy98iauY(Y+$kX=5%BDWC3>8t_a5;(2umh{E(h9wAOn!kp+)HEe z0x=;7bAaUCsDx-k;fZ3uo^L)?yh!u0T}ArNIL^x*^vYgX!|Py{P}&4f%xdhiB;;J1 zUlZ8Z!FN4+H8z(D6y-$nTj83^1e0$IK~Xc$U0bSAk#T39OVH(4Uk7>R?W@^5l1%+{ zR;)$~UQyIcZU4fm*rvi$!{zbh<>>aHdcA8nr0~(V<&oUu2&bY$PKCH9%TFUv@uVoz zxivZE-3*=Lhn&lXTQ8`=o6=A?qAR*Kc(86 zJL~64>dKu2TJ!(FVIxlH(r)OZrKH?HwIiy zlx!`!uevt6Pubvy@Bm#YeprtmK#WnpHZDKVyUcfT^UC{CGf}>@rwW#}2q$ifFg`n+ zr1h!JT4NE^q$H`7wdWBJ@@%NNg%&Ip2B-Ozzrqk!EKXG9rb`|D&_@tgdZdNqRmL}6 zudM9?o(OBXxXi^aWF_j>aY?K1BBX{bT5u&xr!bCC>2!@Bb#fj4=s-O^@;7Ob?c9K5 z33+8<6%gMD+tFCI8d7>@`x+5P9;WfnQgmB*+>!{-(M0XNgdg}IW7KNRopn=o zhDzv_tVcX>fQQMb9Zk)X8_rfkouzHVPWQrIkZ_BN>J)1?*kzFSP?XN&@P4d}iC)}2 zGUUaZ>_~?Ry?H8;Ic>$5H}dQ98`Ht*l}I7D7}cKS!quIlB;#C-k(TMxau9%p9+d|T1Cc330lXp z>=UD&bUxsjhQ^;At63ctE>mnRz~y+#cv|Jp0!&9JQyc8DAvvewkvVxD7 zd;}ay)t+Iqb2QQ18W5>%LN{npEsv9eY}4I|vQkgMant@qfgsSc{PYkCegX?Wh=0cFcc0lY7$aDyT6KuWuSl zs6gdXa4$7eH^RizYzyT$zpkLKiCvasMKFb9m>nXMuqk2XV7lz-CN_i8~yH)=N~2}lBHQ>%ZuYbq0mXeK4KAtAsa0= z4D>o4zzQ&w&TK8o38gv{Y8}`*9TM!i5pK@vcdrcDn=_PWc_JX>U=}tth;BL)VOPY@ z@B^}3OA|>v%D$0TREm~@3mw-9pZDVorAw`o`Av@BJx-C&!Is~C)tp60M2s#a2*H%t zev@qtx$$)X5cl9iAMpz61Jle?xsc9v;#srFl}GZu^}&>(=pBxi67pOv%hE`}Btth2 z6Z%^?MyKNb&?BB>oV|3u!UFhry&tFh+VircrdE*^fvnTyenOITEd{DYXJ~iff?~QG z6C|tdjdwyU5mvSp&KZ8SU`eF62NYfrrarw1^0F!j9R&8Do=r7eN0s&P$Zm{JolQFb zIB%}7P{8CTI;9-ifx6i5uW`CBqtTc~2Gl#$0`O5jU}wFD1W7-D_?De_-g7zP1T7Yh zO|x~B6nErY63?i=<9^dH1@5B>SIf=A3zh>BSoLIj=hkF2PvE#qYo1z$C3HVhviONa zF)WzsVp<6JTO=~8@O*x!gOxEM5frLk;&6(go^Z&ysH>-|J5k(_L0Qhi9F9gM`6_iZ zULmjjoHXNwEguF1D=(|P-!PJ7Jy31*ga-YTof{pu~XY9k>_=Qrwe;tQl$+{86%J-GU1$`x`wS`^fZqiP$LLRK4`$fE99JxbK zA_5#W^;5F`7gZ@0fOK6Ee^=!vtfOt5IL$*t{qix=+QF6k9!ml>A~iP(== zS=`Ot@gM2th0UiRAb!fUB%#R`YKLragnA2m6S*<9O2sAs)mYhSU~~dOr@azsv+V3%&k!Wt6M4wGniH8|H#?!geK76fFUX$QdMljec($n@q83ny-&Gt`g~gR(tSW5!;7jg10HypDxtH( zAf@>E=?APCbpuou*Q@^?Pl-|yu-nU4S1d7%99`_AwW z-3iS@p^3vQh^^6xTIJ90<3zmd_5wp)o9Ro9-<p+(rkMELkmGpUpq$}As=mMWIg7h_;o)4=eLj2skhAhmFTm1Usl?UQmyNTP06gz&me!)t^=mzYRXG|4v z4vgy*wW&(pF=6@EmTB87^rO50xd66LuV8T+rEAZXRS%dJU@r7$ zApujB>WS0Jp6~PdHpTU`$pa$wMOiyq{RwMprj*fih67S|T#QOIR67Z$xSy*R@Y^%& z29cKVtFkO4`BT8$3?xQ7cfsa3e}@fKu!v`>I5x9lA8QKNwr1zIL`Ek~Ej?WOh~`vx zjN&fjwB9OQ=A*QG>Lpm8PMXKLkgxoWwj~w4*?ssZ1tP^Mf#6coDc5;V)G2r6iB&K%B$f^dP{cE-i;QQ=KnN2H#1|@0UN>4k z#5ZvTa3#bTbn=4rCoF}Qz<`mUfB@>}ugFwrbOBg4e%;a~o{|8|_nY4-VTOd^JVW}f zQhigC6R2is`Bg1N?JL&T@hWOco}C}-Q05=;ZWPwXw0o6^Y6US0#ri*HSOxEiPgZgl zf9ZaJ^uTz@TOR_p6U#joKSz*7UI<8_D5LVq23HYNUEWVWpb}d%1ASwLPW9Eg80>3> zIwNdrw?(oczly!|!rrSWkpmueJ<*9oQ;CfiF-)k~k!U{%wz8t6*Bc^?PdfgFpwTu( zB`P)EJ$#EL1#05^<&&qQ3D{=6eUTI}>=*||NJSX#rCjBiRK9K8y=}aOZ}Ci7p95hV zVqdQF*E4jh+Kd2g1li+IW24S?^_-!?*R~eRNDr3gd%)$`FPW*QpO}3Bf?vWB*hXFo zSz(^5H(+GJ@gFgRsZ{fF=mEN?$b4KA>$(O21PId>rak89@aaeU0GBk!>^&FDRVcFdM^$CGCm29d#IN7Oz&YyI z19H>RIao*4>(}L$lipm`_UT><_H@BUheqtLZAW&!hmS~guh=)ZNf3FwE!UeaU_eTj zPW_4Ffl#SvnV$79%ymh3l-%b!TJYmE!f5I+*ux?NIZ;{kat^%FOjR^MRt-@TKilSJciSzhq<&}1mW22ZRab^zqSh>1AB?zzZ zDq1=t&W%V8YOEeYSE#C|p=yg8-{W8=ra`__@x#St*z_wCJKPCby|G<6sCg+I z7XX|bc(6mUcwcejmy&z#syTVgD$B@sa5RhGP_;9cHR7ZR>kWCKAs|xb|3SNR{QC55yosY+`~-)J1bgA8RPM< zwS?c<_0K-T7CW^g?q9);Q99wBt1WRCe#8}hL#aislj1Xf%$Cla+Axv^Vr0#~3Vimx z+dp_BL~n_=a8z6V^C3oAP#jY3OQ&EhWKPkqfVs7SR^uiquK_&|ITrhb%=AYq4$FQ3cb(Er zw6*UMeTrvH+-P+@u)tc#*&&Nj4{w6;G9g7K66Qg+Xe?r0*ozj#mD5s=qiT-gUwGX) zK!tVE`H}5N53ZOkV9LER;p8aY{WCS%WpH0Y29r=$XFcpjC|sGXsHz2Wtkrq(>84&8 z&hxmF)rs@&|4lOYzj_%K|J(eZFTdZWE}+`4+hf!wVGLhdBZL_mrOCh1QK^d?{rs zx_eh%Z3pf^N-3#Z<=iUS7p>t)ifB2)Kp7Uc5Z|JUf9176yL%g&Kh4gNc0S3Ob(pO7 z*@#>bL7K_2lL=Z7d0nr6#65ZMZV0oW8c8VOXwBa@e{Bu;|sXmRI`DoyB?C*hxm^Yd*z^<5Z9J z!NOU0eXN%TmjSR3MRW)t9fU&oJmoUB9!fQ1e3#*F6qcll0% z!ESY-GeS zdKTVVymysevE@pHdy_DdmH$Ex35XCxKtPU{M{tBp#e}i?_D80FejEi;gMMt&f6W+S zQbxRC>6-M|fH0-i=egH|J;|zo@o10^yb|u#H>e68q=2FJI8yR?2nK30y2&ZAzUy);^uK zsWvowQ^LwQthK!GY~U4o96Hk$=d+4PJZuTnPmQNC^@ZCXTaqhzy++L28P3b6pt|pw z2?Wy!zr%*U8kDsLj%cim+yW84n~fI_enxZ?=b|q~^>)mfQsHp8H0Z3QICY(lx;rQl zPXPh3%WGCi7K7Z&pDN24M#~h{)^GA6P15|O!d-FXE-ESEj|N|XbYWvB_A;S;oFWzE z_~3+5>$W*7X@Tuf^&UKXfx$8)gN7`a#Z>*PLVXhFAAOfYUA%DlJR(}1y<}NF_akuE>jAfS2CB+K zE9=n>tqO==#)J9z5~H6!85%LSfPQjTR`w9&Ws>_ytnDcCI6svq$}bs5Cm?#6?;$s- zqv2%jG$LU& zqEcwfQHMJ-!z$HP6DESc!e)I;%SS%klzyQlNxeDV9HX7KdQ5_KzmQc~vy`%{V!RT;Y?a+07629=82p zuap4p3La`}=#7a4hwB*2Atg785H_Q6x_$~00&y5;@3zDPT<>Rzpo+z)+n;A2icC5t)(gwu-_FoC0ZPV|8k{57Z9Y6YB+Rj<5V zSXzAqd44^2OC8)_acAHTMozJR&yBW8B3Mxt5k;&sbyU8p89W56kVov=alht~zh78k|f$H@EXBaf5)d36j7%)*oVNG+B!D{8)Xs7AOHT=2S2-mw#dcT3& zZ?lCDo`B=Vc0zxg5=eEp_9fSoX?rcCrX|8JK3!sYc@+m385kURl5U?vk1J@KwNr-Q z%F&_>!O35GcZ6$Te@AT9X_HV_Z}D2i=UrZ!JEO07ga?CVEw#F^1LQ|On=|kTJ95f1 z5;VL9Yk8PM_C1X*ZONQhU}=|k4h~UG3u%;m7lLgs2qmFzB{j`oPRL?eCzEzeRgUUAXqF9#A6&>g4j-TJwC=;A*?R66+wp)x=nOu-~+ISV$d4|i9Nlq zSwjtEziE>oM(o))G>FJMI_T-mWj(}|t?U_EW?Twpvt7emO>r~LHU;+5k1H=Eytx<0 z#(MPkEyt#&yc>`6mUr4dHDN0EpN&fh>sY3*)}I!|K*fsravWeV&|>5j_OFPqm#Gwi zB!~;Ke4MMTsZVcOBI|+PsF6!2mfw27>iorS?)tg5;`*V6j(Zrdj1`+lY)PEiSw4FK z&IRL`zU4NP8}nC6mT%?vs(A}GWCh83$#)}hc3QW$;JGD2`DEVoB{_#i2ZPo`MB*LN zXI6yuB9(Bt85nJ2_9Eq;i$FuYrr~O0% zG;5u=w%$7rw0mYX#-P1U;?=4F`+yJGV5m7{3U+;NXfwnJX0NzgF}E%l(nYk3zxu(P z#L6xga&y#UN42yEn;JAi9&8YOjT@02qJ8zrlsXS4#ec~#RUPa;%AYQ>%$AGDb8JNK zY`%*Z)nx@m?z7hnULIdYmU!UmNw&QDBD59t)e|2~oIbMG(vZSCUP7J07aw}%7!jJ) zIR4WB6!v!TXIohfW!LsRri}XZEkJpqReS6>{v{$CJ~OvfpP|#1-0xxc$wR-OHfw4S z{chZzTSY$>{Rs8VNI}-@*D}t$aOTke85r|ldCy->ATFp;exxf`t#uM8d|qC(t^tn~ z-?+Is3~z`YvTv&+tIPARSz-i6tGqee|9?)yvhw16utU2V!SE55IF;+EU{q1!(5jy^ zZiqfIHKsUS3YoExr8|s8Cv3P6YAAb;fQ|531XnC-BLfE?aCFkOHpXpOJh)Ahg+!;?R%N-uv8wuW-(0AS_ z=_%jWy7k#f!GuFyP{S3bZL$v0O+o|)znXrF+)YlDWpr+-B_(Io>uYjg`m&NEd_=8!x&uFZnFQPAnttLr!tz&P>zwfsS_Ib?rVF)XU58N&%eME=C z2(INf-i78{t-V}(a$epp*WbZ3d&Dc;uKZAGF-IFr-smDVHSk25gb_xX8lsc&vCJcv zpi<3Bg(G;!E3ihfmK!W3TbRZxY{jcMy#cag<@-nC{Y> zTwCNigrDdT7Z|LDHdwT5uxz9+y8Ls(L8O=i6lw7NHd&CN>|gulKmRBHmFLv|Kvr8N ze-iUC_mm?@M8*XVUhxpwKuc<8w^0{Gq|Ouz%a-4yZ-_)x*o;0Gtwhb3Gz6;qbw8XR zfX z&$Om4T{JUP$@QidbyH9e(|WkE7A7dU<_bsrSRTm}^H$fdv&Ch6o~}(`?`6|Zy_lmr z(dSRT@&r;2hA>mQ*@PxdKBf_=h?Kv#b6XX=*vv^ZY4UsWgN(i6l#K0}bBy|QqaiZh z;I{$p9?U3GH|@yM_)>+XHWwQ8ow-$UfM)r*qL}}p)hKtTPP^eC8zDt+_FjDb0ZE~8 zx_()fw5X|}CLP?$W!EX0|N|+VED;c+1TrF#rjQ86C`=d9qCM`h}21r@(lB3MD1y zS`%dueP(F1ZfL_>!gx=hNMK7LxWyfb;4wj1mVZxn>RRvN1ciL*vxZrUBn%MF4&yYw zW(ea0OR^R=;5UU{mY}i?A6XwicsyI3Uw*VYvtgO$r4C9z3M<}EPYGqOIRAd$TEZF{ zX9wb5k_}J_Hx8DO8XjpJv-*`|(Z@mUuBdQQu=v(ftBk6E<0tgU42}LNnFgl(uNR@V zCccs*2x7Km`ujsy51K%>=~?H*iR=A1;y-Ox9m`PuK+GCgrG8VT#V&SztLeFuz4O}w z|0jap|NqGT{|JH*|ErR1v3B0>XPuIqWY}}~J`6ej6;d0yW1nlR1j4c4plEe?U)~3y zA0n2e;FW8;2ilKA>kcFhPr*3bOQM6n#O!?CXb$21!oPHdWE;&z;bi^eF> z|J*ckSL9Z_XYp_~_(JExi$H-Piarwk2}@YMRmKO&K}?4Uqv2|+{3iXQx|~p<@i_CM z?*&9xTzgP^x>qb*5U+X`(c1M7oE-}N{498yK%RsV#Y6Dz1{fd)$EdV5+_B!e6QiuW zUI9H#9kpbqK*8GCdjBNo2J$g4LHjog)oTa3h5DQ@A{(BfX`VZl3|$`0>8iRbg}G(d zWd-hj68Qvk2Xa)rc$F0k;WE744d`R8i|1`+O!3Ns5q(~LLirvdZ=w{5;VXinmtWon z-i=aZ2KI|gg$rtRxZN87#=F5;$vJajzTvxGdEOEoC)YFd({*rxql>3aF^A7;WhZ4E zTMc>Tx8>7>gOd3X&RB>IPeG3~jngKr07t0~ZdQ-qw}Z|QPD8{+V`(<*|3Ot-yf0zQ zDN%K}vnuDNvkf2k5x;4Z{>~x&<0Aiir|`eI6!rZ+p7p1fCV`dpKf4%zzCQhL`W*GI zdVu}=7rA=w05^Z}beRaQ(%!00ijcSYG;8}dW=;^oU`eAMG`Z4apwU^4QNEu^> zMrUL4lyGn=T5hll2FFo=oh3^w`6vR?aJt&HL1S%WMcva=_IV?h3sB<;aoADa%hhm>{K@!?X#}>q_D7{n@0|kBgS>G!Ts?5hdo9QZzW8zL&=;&zh{AjPAnK|t%rBVKmFCZ(PHin}Z;CNX2{#Lyq^DO+;c8O*^y|A@D}b()?X+@L zBwamr8hsV}Q4GjNgHtBTCyEc|5)4ILvHYNrA{ET3{bv+%4J+>V*W;^csilMVk$k)K z9wUAjN*myV1#ddLQ|pEZa{1e+vG$fOvo3V{-U>{a2s6fION7`!WbFK2aoqDNg8fD4 zQDf0Qv8r{0)GR1LgTvRr(jysGSNGHn3og%v8`E01i9PekpyM8FAPetJ*SPZZIjwU! zJ0=pI#ze34i4>mD zbah!-DNcM1mOD8Pbis%c*-!6CWZw-kZNrtr?6mQqBj!R|UT~`apdA{QZ7+$nGXLwb z^MzYu3Lt7lx`hV;fWF5kcT?$8o_VdaqPpl6H6;uMTy1lNJo#})V%9fNQD=PQ;p+#r z^CH^V?duQxO09JcpRK3#sq4bDhvS9A$ShE(IbH-dVuJbw;MtJKJpQ?LVIv6ut`7UB zYr62HoF_uD!_~l4*=$5ihgg!~@67+-z|y~amHi)bkMj?x{FO01La6s3ZNMkaZ{cyo z+|47a^~xuiD8+)CtJUrmyb|XP)!60y5q62&gR*1zu}coRwGev_jIh6i1(HHEcLlLw z!&z7n{!|%8Igr*|@VzT%8F|ngTb{fjq^BMK&fJ@1@eYUJRj7!+4OVE22!@l}uH9-* zY!0KvBR}+Jj~{l>xI<-`sA`zxaS<{(fPQN?^;hYe?^{7MVou!BxP>@quBO; z(mnn+S*-sfWAyLzoWnNeiXSUfHM3QguSQA@^i<4Yc>Q?@jSAasG0Z*-nrt6&Gc&!r zo6?zV_A1vJRjLodHVv@hU&r!%O7Aq1OeC!#UN8)qVttsLM@3~@e=PG$Kj&)NhT|Lu z{d&N9d5!tE*m?}y+)lFUoWlX7vrWF>W7qqKs&PEDk^4LE$jz#2a!- z-b=7cGN_J?#dMvlt3-Kn6RIA)urH_gTW{s7+pTN}r2K&YYOs-8 z$3PdnP%1w)eC3eZc(kyMEYX`eNKW@e*;;WOHuP{gefsp2ey8K$;F`dN8db5-+S<#j zRG0ohn(*uN)zD>Ous6x~9F8GS8H=s1VvyiV&hOt&8GBlfu@_gCDvQlave?Z6E``;_ z?kp38`NMKUIYGEB++9@Yq@+J!E`HcX?yT^G#jK(#52!VPCoBajLY7tcp~xg#h3$PZ z^1FS01-d7V7F{~e{GPXYK`U&8`eH($Y!%LjQd^3=y)5Dx9^1Pk*4|e>O`xpLpV0+r z)=Vsx7lCpRqiXu}`{zP40P6PzXRH7BYV$vgl7H_J@|SKXQw8NKg&E$kqClmHarYO= z>;2pMGKi!gSZZ`Qde_z^^5hPR3*pR?J4df;I`=^%-|2wuWC0xW}nfwG9My*^P!q|;F_((y}B1}c@s(%LPVNMIqb z16)n%zC9-riq3bkc^~*D3u^bayt+nt`$Htl^YI>Q5EH$`P}j~EW`^t@>x#ehGV=gP z zWSp!W_3Q7YW;c`F&pwx$zAx$Ap+uO=QJ$_l#&BPKJ?V^`?LPmurTIgBZ_W2s*&XK_ zdTRQzgn+dqPl- z7mBByH=Ns3kDYD0;;ZKfNT7soPvl~`>NKwS=J~X_7gk=Ms337G zP=sqv&a9O&Z#{RXIseS`mh2Bl@V77d{V4vS%kuAp?M?srxL(0NE=Fe7`2?pBfgRcXY^36UdiM z_mTc~tL%f~hkT9HmxE)e;bW-7cFYm}em&}(3;Y_#=)%0<3NKoqJYyorkVp|KYTS}7 z{Jp+alv*`pLU))v>n?h`Q9eJ;l{${T2}!_W@TQI3z*IY{QqOB|i$64OTu%$2o!Iqx z=cKaFc8OqOIun-pZ2FPzLlF1%9&=sU3_ziZF029k5yGVWT#F+KbW zSBrAopkPm3k4KjKi+fSgvhGLxZ!QnQ{Zu61in7P&R(8IU9%T#Kv6G=TZJ;H}V%Ds& z+8>E?4W!D^rAt{s>bAI$5ymN}s0m+?l`muqve&h4xYv+W8t7=xnCZcH^|5U5jk zV`v{IXGF?E#ilt@T!(+LU&2{R=ym(;d-3EMiPes$)xrBZhn19|czRc~V=C8IOu!kpSD|AhB-mSg$-f61^2=&lX(iJr@euS_{Y?mb z<&oXzux5mM?WH(lcQ2bB)VC7dV&=wo`AZt-R_RO$6xP0xU=^i_DoY=T6dBNAy@^G% z+LO&Z%fq6pXT@p<3g@>+s$pLHLSaeipxY=kUgdFFRllkt4lmHP;~yT|l}}qdGrJ$< zr@)Wr_EFMoX=&+bia)xvY|2*C-HMB7<=R)Ii1)2`1<+RV- z%Xi+KU?I(Rj3}RyGS7|4sJL75#n-;ptI>ulbtm4Yluyre`~_7WUj+ zTa4~O4K@2%elTOFXG2!ohL&f`x$>0-X}!>^kJVBR-zh#!w<>n@p2Mow6SW(qfgIN- zi`QPgHAQ7^9wk4n_+n)QYBa*kUE|~>>}n=kIaq&?N+2^RAi>^UgT@om-9I>}v0BAh`v*lMk;hwf3 zVtvC&B4DhlnxNJk+L=N5k!uMK|Cri~HQMa}67FLC*sc22pxn{*ra~>=tf>yD3I8$h z{#ya}?*zX81<&ckF7|;H>+iiAYM49Sh}T%e-U)H-iRb2OZ^6y{wfI?8f=o_(hFo3= zZR9bK;?S}B(2(8*4eZMAGmAtzQ147u6?3my@qMUxUt4uBA+-0bq7HXSAFaAh#Xhcl z`uzt#_rv5T(elU+b*gh~Y5RsE*IA|R#qVZmrwfP{wQ^~>jA|vZdP}JIK)+shn1vUZ zu?!A#Hc>P6W9{~G5E)HayEwVvHr1xH1f@YMrmPu49`qCB<3h4h=F}ckN+yV9n96MV zj&mm$+-nV{=hdQDtcGo_`B^}?Zz{WzF_A;RQYzw=ry6IYRp@lkxpy$biXcrzK2qDq zpjUeEv4$O$b{<1B=+>ZLJJEF4?l#H#kHX;!h@a6EDx+7Hh%e{-`lR_c+H_ET8m3+M z3a*Yq1HYzP_Fp@)7t;vY54p_esqx&;!7pe5m9NR=Wg_f zS9T|88!zl_z&E(_%XqD+l7b92S5kI~FO4?4>P3BD)iW!RPc{t2d#;4n1 zNgBhL2u?|s-AA3P+vDIF3sG%|D)wNFt;uiuC|x6o-y!-DkfIXXq`>C>|x&#zq& z+1iMqo|WA6cr7no#yJrK1jfDQ70SJ(+vnJhJ2$jVE&a-#f)C)%NtP{70vooi^$1q> zDS@;fkS88y!E9$`#6|m~7W>}u1K`7{2rfK!$~zVBhO@Es>djUpw_Bq`6tp?CZ!a`; zkMX%mXbJmqZNJcsNg=0Ejqf_uVO;Mhgt7fhuPih#ww{9^Vceu^HD(&HUyH z$4;CSKhY3CnT5@Myj}yyUGE@Sx|!B<(;_2mYua383@@0;2G>eS7g^&H{Kr&J%|B|9 zaRf;;>af#)$(#s!Hb%RuUu4w$zLc0T6G7-%tLZ7#;}iy$L!tFmW4f-BsT->!YePon zU@j3eU04!`e$qUuJ0TL{jZ z?q2IYiryL-?^*uFQ0%%_acMfy22|Ym;i~xy!G1WEpBkSVw(i3`u3~N(7pboVkXwB+ zUw*P!;WE_b_~0VX&=J0|zeqm~nDC)zracRVy%pxF#~?BiRm60)wTxU5$E!;2ULkSL zAgRXyQ~&&N@st>48#>Hmi&)o>H5xe#9v(!FmHdkCamu3FK518%<~%}}eLKF=?KP|0 zF%1IZK|(2pO_0%&6mq)W`5GJ^0u-pY#P~y2tzIV#%Mxj^YP+o}ufR&Z(ND)?2n$jM-ss@a_jngsB|_3b_Fl{ z^g6DCT)fKku0L4a`gD{$UDB@A?~gxj$);;{_AfMhH+C9$hOUyS7Y!c6fCtjH)rd- z7oJ7VR@JtD3kM&uE4&B@42(SJ41VPJ@=?hHf(d>rWi__km;v35eZJJUbKI!^bQ46S-G)y>lgbAup1tD*c1irYEcj0+Wr z%JD#=F-`v(2(*?X7&|+r$MV1(>A02jO-%tS%gCMkF^lwZ#jYw@l&x)!ubS zHMwm2fFgM4HkuL?RJtAsO~4!rAZn;e=g=kesuY1B9Eu2pBBCf#LWdAVkWNH87(oO= z?;U9goe!W`8r^-t*hty2t^p(sz%WU#P!% zY8&uWZp@%L(}!^CTm(>@t+ln$-5F z&jqW+W{`IW$AtRE0y&>Ws@{lX_B35|4C%BD;qB1Cip|ZBpM%}VqWc_nZTvA^wP)5V zmy!*?sw$LceG%p8CasRj8rbSkZAr4BBGXvZaAj0-?TB8=7q>=Y^{RFjgOA2dguoEj z+2@*5?1I&vAYiB+I%>ToLTz!jc6A40#cIU^(72@rG!5UAs$rAtX*ISdJ-E=EPtNiM zG{BzVQV!(iIUmuU$0iM|Tir&;)v#qZ{lS$SI&wDZH#08I+y4z25rpb;9_VX|Pz>ahC%`mM$Ld`eyY>R@kmzTq+b^C#QA zv{xOu#>`K!Ivk6fEIg~xQ)O}Acrjj8Uh;sS=s4M=9jd-{*+j)E{IIpwl$LCZ?6i^8 zTL5u~=l+zOj^vQKSRe8vZJFS9x~L{1pD=cHJg0u*VgR}MOosqVjVGKit4x?xArzrz zE${+CxpS^@c04}#9B;jDG-C-SbcH`&uIp&b$Iz?$1jD1cI0vK^ z7<`3OL6G_7eoc{ne#2IWyPqw$&UTv=mFij*Z86z18CQCw>3p;sxNFX39@`~@EcMT^1f^*Hb@NpT=;xMZ@Oq7Y>&Abo|CRun5QB!4R!<}b@h z%2(2JI@m%m^er3dF6=cDJ~$_!2kSZ=nA(&mnO6LCs8Xi)V{yHL#NfUs->WFW6DPR! z2Z_t2ymj~^%bE6K4)z6%g`HR!CN+2Aez=X9M-PXq!%1yXja~?$K* ztTJ!z=rYIJu`e@dg&5em^0acg-vSw3q`7W{(ecw?VkUciCVPFk!(9}&vdI{0J7F_( zu>{{Pj-wI;P}Z?yy;Z#xkLp|`!iYMSODyDD6^nUkre=-K!WUh4xk8oDzn0&z;`P(YMvfNo!cs{%oWFb|BZ? z+f!VEn^pXj#9N1nsW$UaLPw=w*X*N_!m;h`fo!i}3bHP*(l?~P<%#TF&;5YFZ7eq-ZCKeV^w!oQ_ z2r#j3`(W{t18UzU+dpXF$a)LCEdx|bdEz?opFXPG(+ik=C%C6Bni9=mqQb_ddOhC-wu$xx~Xo_Z05MO=672|Vj8lLEh>wgKz~k)S5| zM)>4o>Q#!3+KW!~i_Sv+D}R5}uND0<2Jjk#*P;L95c943Nicpg=+dimyAu9EmHNH& z%nX!&)PnpcP1Yqxeel`$pX&Z2O#Boat3vi_mFQ~~V<`WNf$n#bY)ti(p1_YPgE>KN z#DlTU9Ulq_{^vB|{W02YYy@ecKc)iA6So7Ae?c~0%F0Y)_^T=OAI^If%HK(2=QCw3 z>r|-9n68=Tr!fe7Y+i=RWdUiQD~qqG(?alNI)tk3r@se}%# zspj3rMIvp5+SaZG7C>3Aho-tI+4`7`oKmMwN8+dSuCc}4F^%mr(h+czVe%pxguo{| z2f=%0pvXsT;}&t7TZ5ZmXVCM8sAlY5U2sxVVf@I7Rl}sDMNao6{}I-Wl_Kz}!2`b@ z|0_LZ6Ra4AE-Y$r=f#@@O}pXP`^3sE z&Lw)h*7tm5amKW@Xn@Jd>A_1PT8rn3P}A*YV#*Z2497JrTMx}NHAxUvx3z3Z8&D3j zziF?{Y!TVUt9E>OHL|NwGz?MBF3PSLAth=9Q7^8?xyHokNzPO=BU1Y~`XUZ?M918? zWeCt`E&()-byg0rNYtgC1hMA?jRe?hMO{zbg&mB&XLk7)$V?$lFMf^k5K65)wF7At zz`Sc2`%NKVtgzaOmLMv*v{zAz%D_BEq{ zMB8&k-0vQ%lVyLblD7TpsF!}K5=QsX0k9Tkn`Za)S#=vT12O%xVJbG3n(q#?ZP`0G zC{;JmJy%ukU$~YV;|R{G(I_pLf4IN5qqMz~6Yu;YMw>2gK8zR4Ff|-rVbC0)PB7FR zk~Pwq;(Vw%J)r;iMX+LI)v=Y0QuWLggFUoa)E(_dAunBM6g;M5 zJFD6z;HwEOYkc2lT`0U@9#uk5-B$}D)M)qPgYCLSqe&ad#dxa-n67(vX$gALe)JbL zr-QTgx0>&zReXAG&HaW$>S^8wK8bS1tfQ}8+pT1(8d}o0-A+7j0gx_#(yX zZBNG#&P&zVnK(c_Skxe6R(O5PmDdRbYfBC<*A@X}ezmZmh2pK8oa1asEK-}=2qb71 z-;2b}1y*W+n3ej&K;QtZywgTm%jvl{+2zpYB7IhP$XyHUJZB$taEl~OD%`wPW+2yV zq(2~t1CcCG9~52)LWJ>HWYyhXwiK{%R>HX5W9+TaND3v0pZ2_QtDTG}4#!W#`u%B4{&y_`3i0@YR z>j|Ads%&4>{I1)3oYnC9A5{NR8?xZ|Qw}{7fXw2_^hXYB^3exdR)#x}qy*wN6}5!J zG?BZ8ryof3%y>Mbq;+O}N;Ai&6tm7HxKjPyjn_7IAa&@ynTm5OdC&$b8NF>BN5)L~ zu#PO$pqQudi)dtN-@8@F`PEr+0G7hjCBN$y<+r0~%kk_vo*WRB}hZ z6mq_QU{KnVuCZQSmDTz8U$@`pp;}dEsk?YnpZ8`u8AFgpc*~qYM-q%$hqZ)Sr>rPw z8FUsx*=^#uJ9DSS#=khmw#kez^>^jkZ=?ej5X-m3Lc1GL5GT(hcC>c!np&Z<}adZ(45oJ2eFQ)$cJ2=c^YjU zMXLGf_J3$osyi8|QTR(9gtOL685~>Yx6quVR|`V&Z5$qp7%GYKU62b4Z*1fm<>VwK z?%@jU@xlQ)^`Umrs<^eGA6My@G9LZj*7jx2)VF$kLqb$TtSLm*T+1o@jPM`K*@l@P zhP*K>WlKdNIESYsmE=%GmC@~5Y(;65OOWhM0gaTm7msuB6{&h09mW5|8(y$t42D!O zc${FVFa>uiuK4MT6BWWaa&#Ke9<;@%J*_&~UU=m^k+`3?P8+n!)C{2;ko`NG3sW0v zN+}@&qr$w5l>Rlq@8U}^&i&#E8TA5@#nER3XIrzXpdqRI1hLRLA0Rm3xq=U;!cev| zc=8r}o8q{XzE3s7+p_Qlp}H$j_d3Lmp*HBe?AYY1idh%6BLiZwsZwEwJjzGr&B7u{ zWm0B#$F2rY a3Ur;{o>ecm4-~RnSU0tJgy8jDwtMK{& diff --git a/cutejava/docs/help/Service方法中使用this.txt b/cutejava/docs/help/Service方法中使用this.txt deleted file mode 100644 index 15a0db5c..00000000 --- a/cutejava/docs/help/Service方法中使用this.txt +++ /dev/null @@ -1,131 +0,0 @@ -# 关于在Spring Service中使用`this`调用方法的问题 - -确实，在Spring管理的Service类中直接使用`this`调用方法会导致Spring的AOP增强失效，这是一个需要注意的重要问题。 - -## 问题本质 - -当你在Spring Service中这样写代码： - -```java -@Service -public class MyService { - - public void methodA() { - this.methodB(); // 这里使用this调用 - } - - @Transactional - public void methodB() { - // 数据库操作 - } -} - -@Service -public class MyService { - public void methodA() { - methodB(); // 这里隐式使用了this.methodB() - } - - @Transactional - public void methodB() { - // 数据库操作 - } -} -``` - -`methodB()`上的`@Transactional`注解会失效，因为： - -1. Spring的AOP（包括事务管理`@Transactional`、缓存`@Cacheable`等）是通过代理实现的 -2. 使用`this`调用会绕过Spring的代理机制，直接调用原始对象的方法 -3. 只有通过代理调用的方法才会被Spring增强 - -## 解决方案 - -### 1. 自我注入（推荐） - -```java -@Service -public class MyService { - - @Autowired - private MyService self; // 注入自身代理 - - public void methodA() { - self.methodB(); // 通过代理调用 - } - - @Transactional - public void methodB() { - // 数据库操作 - } -} -``` - -### 2. 通过ApplicationContext获取代理 - -```java -@Service -public class MyService implements ApplicationContextAware { - - private ApplicationContext context; - - @Override - public void setApplicationContext(ApplicationContext context) { - this.context = context; - } - - public void methodA() { - context.getBean(MyService.class).methodB(); - } - - @Transactional - public void methodB() { - // 数据库操作 - } -} -``` - -### 3. 调整方法结构（最佳实践） - -```java -@Service -public class MyService { - - private final OtherService otherService; - - public MyService(OtherService otherService) { - this.otherService = otherService; - } - - public void methodA() { - // 将需要事务的方法提取到另一个Service - otherService.methodB(); - } -} - -@Service -public class OtherService { - - @Transactional - public void methodB() { - // 数据库操作 - } -} -``` - -## 为什么会出现这种情况？ - -Spring的AOP实现原理： -1. 默认使用JDK动态代理（基于接口）或CGLIB（基于子类） -2. 代理对象包装了原始对象 -3. 外部调用先经过代理，代理再决定是否应用增强逻辑 -4. `this`引用指向的是原始对象而非代理对象 - -## 最佳实践建议 - -1. 尽量避免在Service内部方法间调用需要AOP增强的方法 -2. 如果必须调用，使用自我注入的方式 -3. 考虑将需要事务管理的方法拆分到单独的Service中 -4. 对于复杂的业务逻辑，考虑使用领域驱动设计(DDD)的模式 - -这种设计是Spring AOP的固有特性，理解这一点对于正确使用Spring的事务管理、缓存、安全等AOP功能非常重要。 diff --git a/cutejava/docs/help/license.template b/cutejava/docs/help/license.template deleted file mode 100644 index 07e0fb60..00000000 --- a/cutejava/docs/help/license.template +++ /dev/null @@ -1,13 +0,0 @@ -Copyright 2021-2025 Odboy - -Licensed 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. \ No newline at end of file diff --git a/cutejava/docs/help/应用迭代定义.txt b/cutejava/docs/help/应用迭代定义.txt deleted file mode 100644 index daad3b4d..00000000 --- a/cutejava/docs/help/应用迭代定义.txt +++ /dev/null @@ -1 +0,0 @@ -一次迭代=N次尝试(流水线实例) + 发布分支(git分支) \ No newline at end of file diff --git a/cutejava/docs/help/注意事项.md b/cutejava/docs/help/注意事项.md deleted file mode 100644 index 7427d53e..00000000 --- a/cutejava/docs/help/注意事项.md +++ /dev/null @@ -1,3 +0,0 @@ -### 注意事项 - -long、bigdecimal返回前端时，字段尽量设置为String，否则会出现精度丢失问题 \ No newline at end of file diff --git a/cutejava/docs/help/缓存注解使用.txt b/cutejava/docs/help/缓存注解使用.txt deleted file mode 100644 index 5146490a..00000000 --- a/cutejava/docs/help/缓存注解使用.txt +++ /dev/null @@ -1,27 +0,0 @@ -@Service -public class UserService { - @Autowired - private UserRepository userRepository; - - @Cacheable(value = "users", key = "#userId") - public User getUserById(Long userId) { - return userRepository.findById(userId).orElse(null); - } - - @CachePut(value = "users", key = "#user.id") - // @CachePut(value = "users", key = "#user.id + '_' + #user.age") - public User updateUser(User user) { - userRepository.save(user); - return user; - } - - @CacheEvict(value = "users", key = "#userId") - public void deleteUser(Long userId) { - userRepository.deleteById(userId); - } - - @CacheEvict(value = "users", allEntries = true) - public void clearCache() { - // 清空缓存 - } -} \ No newline at end of file diff --git a/cutejava/docs/mysql/cutejava.sql b/cutejava/docs/mysql/cutejava.sql deleted file mode 100644 index 295d2e5b..00000000 --- a/cutejava/docs/mysql/cutejava.sql +++ /dev/null @@ -1,2015 +0,0 @@ -/* - Navicat Premium Dump SQL - - Source Server : mysql - Source Server Type : MySQL - Source Server Version : 80025 (8.0.25) - Source Host : 192.168.100.128:23306 - Source Schema : cutejava - - Target Server Type : MySQL - Target Server Version : 80025 (8.0.25) - File Encoding : 65001 -*/ - -SET NAMES utf8mb4; -SET -FOREIGN_KEY_CHECKS = 0; - --- ---------------------------- --- Table structure for demo_time_table_copy1 --- ---------------------------- -DROP TABLE IF EXISTS `demo_time_table_copy1`; -CREATE TABLE `demo_time_table_copy1` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id', - `create_time` datetime NOT NULL COMMENT '创建时间', - `update_time` datetime NOT NULL COMMENT '修改时间', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of demo_time_table_copy1 --- ---------------------------- - --- ---------------------------- --- Table structure for demo_user_time_logic_table --- ---------------------------- -DROP TABLE IF EXISTS `demo_user_time_logic_table`; -CREATE TABLE `demo_user_time_logic_table` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '创建人', - `create_time` datetime NOT NULL COMMENT '创建时间', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '修改人', - `update_time` datetime NOT NULL COMMENT '修改时间', - `available` tinyint(1) NOT NULL DEFAULT 1 COMMENT '数据有效性', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of demo_user_time_logic_table --- ---------------------------- - --- ---------------------------- --- Table structure for demo_user_time_table --- ---------------------------- -DROP TABLE IF EXISTS `demo_user_time_table`; -CREATE TABLE `demo_user_time_table` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '创建人', - `create_time` datetime NOT NULL COMMENT '创建时间', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '修改人', - `update_time` datetime NOT NULL COMMENT '修改时间', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of demo_user_time_table --- ---------------------------- - --- ---------------------------- --- Table structure for qrtz_blob_triggers --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_blob_triggers`; -CREATE TABLE `qrtz_blob_triggers` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_group` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `blob_data` blob NULL, - PRIMARY KEY (`sched_name`, `trigger_name`, `trigger_group`) USING BTREE, - INDEX `sched_name`(`sched_name` ASC, `trigger_name` ASC, `trigger_group` ASC) USING BTREE, - CONSTRAINT `qrtz_blob_triggers_ibfk_1` FOREIGN KEY (`sched_name`, `trigger_name`, `trigger_group`) REFERENCES `qrtz_triggers` (`sched_name`, `trigger_name`, `trigger_group`) ON DELETE RESTRICT ON UPDATE RESTRICT -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_blob_triggers --- ---------------------------- - --- ---------------------------- --- Table structure for qrtz_calendars --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_calendars`; -CREATE TABLE `qrtz_calendars` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `calendar_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `calendar` blob NOT NULL, - PRIMARY KEY (`sched_name`, `calendar_name`) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_calendars --- ---------------------------- - --- ---------------------------- --- Table structure for qrtz_cron_triggers --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_cron_triggers`; -CREATE TABLE `qrtz_cron_triggers` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_group` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `cron_expression` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `time_zone_id` varchar(80) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - PRIMARY KEY (`sched_name`, `trigger_name`, `trigger_group`) USING BTREE, - CONSTRAINT `qrtz_cron_triggers_ibfk_1` FOREIGN KEY (`sched_name`, `trigger_name`, `trigger_group`) REFERENCES `qrtz_triggers` (`sched_name`, `trigger_name`, `trigger_group`) ON DELETE RESTRICT ON UPDATE RESTRICT -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_cron_triggers --- ---------------------------- - --- ---------------------------- --- Table structure for qrtz_fired_triggers --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_fired_triggers`; -CREATE TABLE `qrtz_fired_triggers` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `entry_id` varchar(95) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_group` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `instance_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `fired_time` bigint NOT NULL, - `sched_time` bigint NOT NULL, - `priority` int NOT NULL, - `state` varchar(16) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `job_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `job_group` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `is_nonconcurrent` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `requests_recovery` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - PRIMARY KEY (`sched_name`, `entry_id`) USING BTREE, - INDEX `idx_qrtz_ft_trig_inst_name`(`sched_name` ASC, `instance_name` ASC) USING BTREE, - INDEX `idx_qrtz_ft_inst_job_req_rcvry`(`sched_name` ASC, `instance_name` ASC, `requests_recovery` ASC) USING BTREE, - INDEX `idx_qrtz_ft_j_g`(`sched_name` ASC, `job_name` ASC, `job_group` ASC) USING BTREE, - INDEX `idx_qrtz_ft_jg`(`sched_name` ASC, `job_group` ASC) USING BTREE, - INDEX `idx_qrtz_ft_t_g`(`sched_name` ASC, `trigger_name` ASC, `trigger_group` ASC) USING BTREE, - INDEX `idx_qrtz_ft_tg`(`sched_name` ASC, `trigger_group` ASC) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_fired_triggers --- ---------------------------- - --- ---------------------------- --- Table structure for qrtz_job_details --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_job_details`; -CREATE TABLE `qrtz_job_details` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `job_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `job_group` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `description` varchar(250) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `job_class_name` varchar(250) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `is_durable` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `is_nonconcurrent` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `is_update_data` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `requests_recovery` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `job_data` blob NULL, - PRIMARY KEY (`sched_name`, `job_name`, `job_group`) USING BTREE, - INDEX `idx_qrtz_j_req_recovery`(`sched_name` ASC, `requests_recovery` ASC) USING BTREE, - INDEX `idx_qrtz_j_grp`(`sched_name` ASC, `job_group` ASC) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_job_details --- ---------------------------- - --- ---------------------------- --- Table structure for qrtz_locks --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_locks`; -CREATE TABLE `qrtz_locks` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `lock_name` varchar(40) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - PRIMARY KEY (`sched_name`, `lock_name`) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_locks --- ---------------------------- -INSERT INTO `qrtz_locks` -VALUES ('ClusteredScheduler', 'STATE_ACCESS'); -INSERT INTO `qrtz_locks` -VALUES ('ClusteredScheduler', 'TRIGGER_ACCESS'); -INSERT INTO `qrtz_locks` -VALUES ('cutejava', 'STATE_ACCESS'); -INSERT INTO `qrtz_locks` -VALUES ('cutejava', 'TRIGGER_ACCESS'); - --- ---------------------------- --- Table structure for qrtz_paused_trigger_grps --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_paused_trigger_grps`; -CREATE TABLE `qrtz_paused_trigger_grps` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_group` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - PRIMARY KEY (`sched_name`, `trigger_group`) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_paused_trigger_grps --- ---------------------------- - --- ---------------------------- --- Table structure for qrtz_scheduler_state --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_scheduler_state`; -CREATE TABLE `qrtz_scheduler_state` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `instance_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `last_checkin_time` bigint NOT NULL, - `checkin_interval` bigint NOT NULL, - PRIMARY KEY (`sched_name`, `instance_name`) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_scheduler_state --- ---------------------------- -INSERT INTO `qrtz_scheduler_state` -VALUES ('ClusteredScheduler', 'DESKTOP-FM44BLS1742558233429', 1742558255052, 20000); -INSERT INTO `qrtz_scheduler_state` -VALUES ('cutejava', 'auto', 1761211053605, 10000); - --- ---------------------------- --- Table structure for qrtz_simple_triggers --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_simple_triggers`; -CREATE TABLE `qrtz_simple_triggers` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_group` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `repeat_count` bigint NOT NULL, - `repeat_interval` bigint NOT NULL, - `times_triggered` bigint NOT NULL, - PRIMARY KEY (`sched_name`, `trigger_name`, `trigger_group`) USING BTREE, - CONSTRAINT `qrtz_simple_triggers_ibfk_1` FOREIGN KEY (`sched_name`, `trigger_name`, `trigger_group`) REFERENCES `qrtz_triggers` (`sched_name`, `trigger_name`, `trigger_group`) ON DELETE RESTRICT ON UPDATE RESTRICT -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_simple_triggers --- ---------------------------- - --- ---------------------------- --- Table structure for qrtz_simprop_triggers --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_simprop_triggers`; -CREATE TABLE `qrtz_simprop_triggers` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_group` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `str_prop_1` varchar(512) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `str_prop_2` varchar(512) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `str_prop_3` varchar(512) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `int_prop_1` int NULL DEFAULT NULL, - `int_prop_2` int NULL DEFAULT NULL, - `long_prop_1` bigint NULL DEFAULT NULL, - `long_prop_2` bigint NULL DEFAULT NULL, - `dec_prop_1` decimal(13, 4) NULL DEFAULT NULL, - `dec_prop_2` decimal(13, 4) NULL DEFAULT NULL, - `bool_prop_1` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `bool_prop_2` varchar(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - PRIMARY KEY (`sched_name`, `trigger_name`, `trigger_group`) USING BTREE, - CONSTRAINT `qrtz_simprop_triggers_ibfk_1` FOREIGN KEY (`sched_name`, `trigger_name`, `trigger_group`) REFERENCES `qrtz_triggers` (`sched_name`, `trigger_name`, `trigger_group`) ON DELETE RESTRICT ON UPDATE RESTRICT -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_simprop_triggers --- ---------------------------- - --- ---------------------------- --- Table structure for qrtz_triggers --- ---------------------------- -DROP TABLE IF EXISTS `qrtz_triggers`; -CREATE TABLE `qrtz_triggers` -( - `sched_name` varchar(120) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_group` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `job_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `job_group` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `description` varchar(250) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `next_fire_time` bigint NULL DEFAULT NULL, - `prev_fire_time` bigint NULL DEFAULT NULL, - `priority` int NULL DEFAULT NULL, - `trigger_state` varchar(16) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `trigger_type` varchar(8) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL, - `start_time` bigint NOT NULL, - `end_time` bigint NULL DEFAULT NULL, - `calendar_name` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `misfire_instr` smallint NULL DEFAULT NULL, - `job_data` blob NULL, - PRIMARY KEY (`sched_name`, `trigger_name`, `trigger_group`) USING BTREE, - INDEX `idx_qrtz_t_j`(`sched_name` ASC, `job_name` ASC, `job_group` ASC) USING BTREE, - INDEX `idx_qrtz_t_jg`(`sched_name` ASC, `job_group` ASC) USING BTREE, - INDEX `idx_qrtz_t_c`(`sched_name` ASC, `calendar_name` ASC) USING BTREE, - INDEX `idx_qrtz_t_g`(`sched_name` ASC, `trigger_group` ASC) USING BTREE, - INDEX `idx_qrtz_t_state`(`sched_name` ASC, `trigger_state` ASC) USING BTREE, - INDEX `idx_qrtz_t_n_state`(`sched_name` ASC, `trigger_name` ASC, `trigger_group` ASC, `trigger_state` ASC) USING BTREE, - INDEX `idx_qrtz_t_n_g_state`(`sched_name` ASC, `trigger_group` ASC, `trigger_state` ASC) USING BTREE, - INDEX `idx_qrtz_t_next_fire_time`(`sched_name` ASC, `next_fire_time` ASC) USING BTREE, - INDEX `idx_qrtz_t_nft_st`(`sched_name` ASC, `trigger_state` ASC, `next_fire_time` ASC) USING BTREE, - INDEX `idx_qrtz_t_nft_misfire`(`sched_name` ASC, `misfire_instr` ASC, `next_fire_time` ASC) USING BTREE, - INDEX `idx_qrtz_t_nft_st_misfire`(`sched_name` ASC, `misfire_instr` ASC, `next_fire_time` ASC, `trigger_state` ASC) USING BTREE, - INDEX `idx_qrtz_t_nft_st_misfire_grp`(`sched_name` ASC, `misfire_instr` ASC, `next_fire_time` ASC, `trigger_group` ASC, `trigger_state` ASC) USING BTREE, - CONSTRAINT `qrtz_triggers_ibfk_1` FOREIGN KEY (`sched_name`, `job_name`, `job_group`) REFERENCES `qrtz_job_details` (`sched_name`, `job_name`, `job_group`) ON DELETE RESTRICT ON UPDATE RESTRICT -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of qrtz_triggers --- ---------------------------- - --- ---------------------------- --- Table structure for system_dept --- ---------------------------- -DROP TABLE IF EXISTS `system_dept`; -CREATE TABLE `system_dept` -( - `dept_id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `pid` bigint NULL DEFAULT NULL COMMENT '上级部门', - `sub_count` int NULL DEFAULT 0 COMMENT '子部门数目', - `name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '名称', - `dept_sort` int NULL DEFAULT 999 COMMENT '排序', - `enabled` bit(1) NOT NULL COMMENT '状态', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '创建者', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '更新者', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建日期', - `update_time` datetime NULL DEFAULT NULL COMMENT '更新时间', - PRIMARY KEY (`dept_id`) USING BTREE, - INDEX `idx_pid`(`pid` ASC) USING BTREE, - INDEX `idx_enabled`(`enabled` ASC) USING BTREE, - INDEX `idx_sys_dept_dept_id`(`dept_id` ASC) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 18 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '部门' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_dept --- ---------------------------- -INSERT INTO `system_dept` -VALUES (2, 7, 1, '研发部', 3, b'1', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dept` -VALUES (5, 7, 0, '运维部', 4, b'1', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dept` -VALUES (6, 8, 0, '测试部', 6, b'1', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dept` -VALUES (7, NULL, 2, '华南分部', 0, b'1', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dept` -VALUES (8, NULL, 2, '华北分部', 1, b'1', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dept` -VALUES (15, 8, 0, 'UI部门', 7, b'1', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dept` -VALUES (17, 2, 0, '研发一组', 999, b'1', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); - --- ---------------------------- --- Table structure for system_dict --- ---------------------------- -DROP TABLE IF EXISTS `system_dict`; -CREATE TABLE `system_dict` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '字典名称', - `description` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '描述', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '创建者', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '更新者', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建日期', - `update_time` datetime NULL DEFAULT NULL COMMENT '更新时间', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 9 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '数据字典' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_dict --- ---------------------------- -INSERT INTO `system_dict` -VALUES (1, 'user_status', '用户状态', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict` -VALUES (4, 'dept_status', '部门状态', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict` -VALUES (5, 'job_status', '岗位状态', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict` -VALUES (8, 'test_status', '测试状态', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); - --- ---------------------------- --- Table structure for system_dict_detail --- ---------------------------- -DROP TABLE IF EXISTS `system_dict_detail`; -CREATE TABLE `system_dict_detail` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `dict_id` bigint NULL DEFAULT NULL COMMENT '字典id', - `label` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '字典标签', - `value` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '字典值', - `dict_sort` int NULL DEFAULT NULL COMMENT '排序', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '创建者', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '更新者', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建日期', - `update_time` datetime NULL DEFAULT NULL COMMENT '更新时间', - PRIMARY KEY (`id`) USING BTREE, - INDEX `idx_dict_id`(`dict_id` ASC) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 29 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '数据字典详情' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_dict_detail --- ---------------------------- -INSERT INTO `system_dict_detail` -VALUES (1, 1, '激活', 'true', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (2, 1, '禁用', 'false', 2, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (3, 4, '启用', 'true', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (4, 4, '停用', 'false', 2, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (5, 5, '启用', 'true', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (6, 5, '停用', 'false', 2, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (7, 8, '打瞌睡01', 'ks01', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (8, 8, '打瞌睡2', 'ks02', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (9, 8, '打瞌睡3', 'ks03', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (10, 8, '打瞌睡4', 'ks04', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (11, 8, '打瞌睡5', 'ks05', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (12, 8, '打瞌睡6', 'ks06', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (13, 8, '打瞌睡7', 'ks07', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (14, 8, '打瞌睡8', 'ks08', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (15, 8, '打瞌睡9', 'ks09', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (16, 8, '打瞌睡10', 'ks10', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (17, 8, '打瞌睡11', 'ks11', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (18, 8, '打瞌睡12', 'ks12', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (19, 8, '打瞌睡13', 'ks13', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (20, 8, '打瞌睡14', 'ks14', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (21, 8, '打瞌睡15', 'ks15', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (22, 8, '打瞌睡16', 'ks16', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (23, 8, '打瞌睡17', 'ks17', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (24, 8, '打瞌睡18', 'ks18', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (25, 8, '打瞌睡19', 'ks19', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (26, 8, '打瞌睡20', 'ks20', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (27, 8, '打瞌睡21', 'ks21', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_dict_detail` -VALUES (28, 8, '打瞌睡22', 'ks22', 1, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); - --- ---------------------------- --- Table structure for system_email_config --- ---------------------------- -DROP TABLE IF EXISTS `system_email_config`; -CREATE TABLE `system_email_config` -( - `config_id` bigint NOT NULL COMMENT 'ID', - `from_user` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '收件人', - `host` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '邮件服务器SMTP地址', - `password` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '密码', - `port` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '端口', - `user` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '发件者用户名', - PRIMARY KEY (`config_id`) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '邮箱配置' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_email_config --- ---------------------------- - --- ---------------------------- --- Table structure for system_job --- ---------------------------- -DROP TABLE IF EXISTS `system_job`; -CREATE TABLE `system_job` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `name` varchar(180) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '岗位名称', - `enabled` bit(1) NOT NULL COMMENT '岗位状态', - `job_sort` int NULL DEFAULT NULL COMMENT '排序', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '创建者', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '更新者', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建日期', - `update_time` datetime NULL DEFAULT NULL COMMENT '更新时间', - PRIMARY KEY (`id`) USING BTREE, - UNIQUE INDEX `uniq_name`(`name` ASC) USING BTREE, - INDEX `idx_enabled`(`enabled` ASC) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 13 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '岗位' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_job --- ---------------------------- -INSERT INTO `system_job` -VALUES (8, '人事专员', b'1', 3, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_job` -VALUES (10, '产品经理', b'1', 4, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_job` -VALUES (11, '全栈开发', b'1', 2, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_job` -VALUES (12, '软件测试', b'1', 5, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); - --- ---------------------------- --- Table structure for system_local_storage --- ---------------------------- -DROP TABLE IF EXISTS `system_local_storage`; -CREATE TABLE `system_local_storage` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `real_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '文件真实的名称', - `name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '文件名', - `suffix` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '后缀', - `path` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '路径', - `type` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '类型', - `size` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '大小', - `date_group` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '日期分组', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '创建者', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '更新者', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建日期', - `update_time` datetime NULL DEFAULT NULL COMMENT '更新时间', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '本地存储' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_local_storage --- ---------------------------- - --- ---------------------------- --- Table structure for system_menu --- ---------------------------- -DROP TABLE IF EXISTS `system_menu`; -CREATE TABLE `system_menu` -( - `menu_id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `pid` bigint NULL DEFAULT NULL COMMENT '上级菜单ID', - `sub_count` int NULL DEFAULT 0 COMMENT '子菜单数目', - `type` int NULL DEFAULT NULL COMMENT '菜单类型', - `title` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '菜单标题', - `name` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '组件名称', - `component` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '组件', - `menu_sort` int NULL DEFAULT NULL COMMENT '排序', - `icon` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '图标', - `path` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '链接地址', - `i_frame` bit(1) NULL DEFAULT NULL COMMENT '是否外链', - `cache` bit(1) NULL DEFAULT b'0' COMMENT '缓存', - `hidden` bit(1) NULL DEFAULT b'0' COMMENT '隐藏', - `permission` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '权限', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '创建者', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '更新者', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建日期', - `update_time` datetime NULL DEFAULT NULL COMMENT '更新时间', - PRIMARY KEY (`menu_id`) USING BTREE, - UNIQUE INDEX `uniq_name`(`name` ASC) USING BTREE, - UNIQUE INDEX `uniq_title`(`title` ASC) USING BTREE, - INDEX `idx_pid`(`pid` ASC) USING BTREE, - INDEX `idx_sys_menu_menu_id`(`menu_id` ASC) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 151 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '系统菜单' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_menu --- ---------------------------- -INSERT INTO `system_menu` -VALUES (1, NULL, 9, 0, '系统管理', NULL, NULL, 998, 'system', 'system', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (2, 1, 3, 1, '用户管理', 'User', 'system/user/index', 2, 'peoples', 'user', b'0', b'0', b'0', 'user:list', 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (3, 1, 3, 1, '角色管理', 'Role', 'system/role/index', 3, 'role', 'role', b'0', b'0', b'0', 'roles:list', 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (5, 1, 3, 1, '菜单管理', 'Menu', 'system/menu/index', 5, 'menu', 'menu', b'0', b'0', b'0', 'menu:list', 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (6, 1, 3, 0, '系统监控', NULL, NULL, 11, 'monitor', 'monitor', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (9, 6, 0, 1, 'SQL监控', 'DruidSqlConsole', 'system/druidSql/index', 18, 'sqlMonitor', 'druid-console', b'0', b'0', b'0', NULL, 'admin', 'admin', - '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (10, NULL, 16, 0, '组件管理', NULL, NULL, 999, 'zujian', 'components', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (11, 10, 0, 1, '图标库', 'Icons', 'components/icons/index', 51, 'icon', 'icon', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (14, 36, 0, 1, '邮件工具', 'Email', 'system/email/index', 35, 'email', 'email', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (18, 36, 3, 1, '存储管理', 'Storage', 'system/storage/index', 34, 'qiniu', 'storage', b'0', b'0', b'0', 'storage:list', 'admin', 'admin', - '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (21, NULL, 2, 0, '演示:多级菜单', NULL, '', 999, 'menu', 'nested', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (22, 21, 2, 0, '二级菜单1', NULL, '', 999, 'menu', 'menu1', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (23, 21, 0, 1, '二级菜单2', NULL, 'nested/menu2/index', 999, 'menu', 'menu2', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (24, 22, 0, 1, '三级菜单1', 'Test', 'nested/menu1/menu1-1', 999, 'menu', 'menu1-1', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (27, 22, 0, 1, '三级菜单2', NULL, 'nested/menu1/menu1-2', 999, 'menu', 'menu1-2', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (28, 1, 3, 1, '任务调度', 'QuartzJob', 'system/quartzJob/index', 9, 'timing', 'quartz-job', b'0', b'0', b'0', 'quartzJob:list', 'admin', 'admin', - '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (34, 10, 0, 1, '演示:Yaml编辑器', 'CuteYamlEditorDemo', 'componentsDemo/CuteYamlEditorDemo', 999, 'menu', 'cuteYamlEditorDemo', b'0', b'0', b'0', NULL, - 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (35, 1, 3, 1, '部门管理', 'Dept', 'system/dept/index', 6, 'dept', 'dept', b'0', b'0', b'0', 'dept:list', 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (36, 1, 2, 0, '系统工具', NULL, '', 10, 'sys-tools', 'sys-tools', b'0', b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (37, 1, 3, 1, '岗位管理', 'Job', 'system/job/index', 7, 'Steve-Jobs', 'job', b'0', b'0', b'0', 'job:list', 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (39, 1, 3, 1, '字典管理', 'Dict', 'system/dict/index', 8, 'dictionary', 'dict', b'0', b'0', b'0', 'dict:list', 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (41, 6, 0, 1, '在线用户', 'OnlineUser', 'system/online/index', 10, 'Steve-Jobs', 'online', b'0', b'0', b'0', NULL, 'admin', 'admin', - '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (44, 2, 0, 2, '用户新增', NULL, '', 2, '', '', b'0', b'0', b'0', 'user:add', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (45, 2, 0, 2, '用户编辑', NULL, '', 3, '', '', b'0', b'0', b'0', 'user:edit', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (46, 2, 0, 2, '用户删除', NULL, '', 4, '', '', b'0', b'0', b'0', 'user:del', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (48, 3, 0, 2, '角色创建', NULL, '', 2, '', '', b'0', b'0', b'0', 'roles:add', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (49, 3, 0, 2, '角色修改', NULL, '', 3, '', '', b'0', b'0', b'0', 'roles:edit', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (50, 3, 0, 2, '角色删除', NULL, '', 4, '', '', b'0', b'0', b'0', 'roles:del', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (52, 5, 0, 2, '菜单新增', NULL, '', 2, '', '', b'0', b'0', b'0', 'menu:add', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (53, 5, 0, 2, '菜单编辑', NULL, '', 3, '', '', b'0', b'0', b'0', 'menu:edit', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (54, 5, 0, 2, '菜单删除', NULL, '', 4, '', '', b'0', b'0', b'0', 'menu:del', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (56, 35, 0, 2, '部门新增', NULL, '', 2, '', '', b'0', b'0', b'0', 'dept:add', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (57, 35, 0, 2, '部门编辑', NULL, '', 3, '', '', b'0', b'0', b'0', 'dept:edit', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (58, 35, 0, 2, '部门删除', NULL, '', 4, '', '', b'0', b'0', b'0', 'dept:del', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (60, 37, 0, 2, '岗位新增', NULL, '', 2, '', '', b'0', b'0', b'0', 'job:add', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (61, 37, 0, 2, '岗位编辑', NULL, '', 3, '', '', b'0', b'0', b'0', 'job:edit', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (62, 37, 0, 2, '岗位删除', NULL, '', 4, '', '', b'0', b'0', b'0', 'job:del', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (64, 39, 0, 2, '字典新增', NULL, '', 2, '', '', b'0', b'0', b'0', 'dict:add', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (65, 39, 0, 2, '字典编辑', NULL, '', 3, '', '', b'0', b'0', b'0', 'dict:edit', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (66, 39, 0, 2, '字典删除', NULL, '', 4, '', '', b'0', b'0', b'0', 'dict:del', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (73, 28, 0, 2, '任务新增', NULL, '', 2, '', '', b'0', b'0', b'0', 'quartzJob:add', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (74, 28, 0, 2, '任务编辑', NULL, '', 3, '', '', b'0', b'0', b'0', 'quartzJob:edit', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (75, 28, 0, 2, '任务删除', NULL, '', 4, '', '', b'0', b'0', b'0', 'quartzJob:del', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (77, 18, 0, 2, '上传文件', NULL, '', 2, '', '', b'0', b'0', b'0', 'storage:add', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (78, 18, 0, 2, '文件编辑', NULL, '', 3, '', '', b'0', b'0', b'0', 'storage:edit', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (79, 18, 0, 2, '文件删除', NULL, '', 4, '', '', b'0', b'0', b'0', 'storage:del', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (80, 6, 0, 1, '服务监控', 'ServerMonitor', 'system/server/index', 14, 'codeConsole', 'server', b'0', b'0', b'0', 'monitor:list', 'admin', 'admin', - '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (83, 10, 0, 1, '图表库', 'Echarts', 'components/base/Echarts', 50, 'chart', 'echarts', b'0', b'1', b'0', '', 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (117, 10, 0, 1, '演示:一键复制组件', 'CuteOneKeyCopy', 'componentsDemo/CuteOneKeyCopyDemo', 999, 'menu', 'cuteOneKeyCopyDemo', b'0', b'0', b'0', NULL, - 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (118, 10, 0, 1, '演示:Java代码编辑器', 'CuteJavaEditorDemo', 'componentsDemo/CuteJavaEditorDemo', 999, 'menu', 'cuteJavaEditorDemo', b'0', b'0', b'0', - NULL, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (119, 10, 0, 1, '数字滚动', 'countToDemo', 'components/base/CountToDemo', 56, 'menu', 'countToDemo', b'0', b'0', b'0', NULL, 'admin', 'admin', - '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (121, 10, 0, 1, '分割面板', 'splitPaneDemo', 'components/base/SplitPaneDemo', 57, 'menu', 'splitPaneDemo', b'0', b'0', b'0', NULL, 'admin', 'admin', - '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (122, 10, 0, 1, 'WebSocket', 'webSocketDemo', 'components/base/WebSocketDemo', 58, 'menu', 'webSocketDemo', b'0', b'0', b'0', NULL, 'admin', 'admin', - '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (125, 10, 0, 1, '演示:业务组件', 'CuteBusinessDemo', 'componentsDemo/CuteBusinessDemo', 999, 'menu', 'cuteBusinessDemo', b'0', b'0', b'0', NULL, 'admin', - 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (126, 10, 2, 1, '演示:简单表格组件', 'CuteSimpleTableDemo', 'componentsDemo/CuteSimpleTableDemo', 999, 'menu', 'cuteSimpleTableDemo', b'0', b'0', b'0', - NULL, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (127, 10, 2, 1, '演示:拖拽表格组件', 'CuteDragTableDemo', 'componentsDemo/CuteDragTableDemo', 999, 'menu', 'cuteDragTableDemo', b'0', b'0', b'0', NULL, - 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (128, 10, 0, 1, '演示:Markdown编辑器', 'CuteMarkdownDemo', 'componentsDemo/CuteMarkdownDemo', 999, 'menu', 'cuteMarkdownDemo', b'0', b'0', b'0', NULL, - 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (129, 10, 0, 1, '演示:富文本编辑器', 'CuteRichTextEditorDemo', 'componentsDemo/CuteRichTextEditorDemo', 999, 'menu', 'cuteRichTextEditorDemo', b'0', - b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (130, 10, 0, 1, '演示:文件上传', 'CuteFileUploadDemo', 'componentsDemo/CuteFileUploadDemo', 999, 'menu', 'cuteFileUploadDemo', b'0', b'0', b'0', NULL, - 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (132, 10, 0, 1, '演示:文件拖拽上传', 'CuteFileDragUploadDemo', 'componentsDemo/CuteFileDragUploadDemo', 999, 'menu', 'cuteFileDragUploadDemo', b'0', - b'0', b'0', NULL, 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_menu` -VALUES (150, 10, 0, 1, '演示:其他基础组件', 'CuteOtherDemo', 'componentsDemo/CuteOtherDemo', 999, 'menu', 'cuteOtherDemo', b'0', b'0', b'0', NULL, 'admin', - 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); - --- ---------------------------- --- Table structure for system_operation_log --- ---------------------------- -DROP TABLE IF EXISTS `system_operation_log`; -CREATE TABLE `system_operation_log` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id', - `biz_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `method` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `params` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL, - `request_ip` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `execute_time` bigint NULL DEFAULT NULL, - `username` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `address` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `browser_info` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL, - `exception_detail` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL, - `create_time` datetime NOT NULL, - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '审计日志' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_operation_log --- ---------------------------- - --- ---------------------------- --- Table structure for system_oss_storage --- ---------------------------- -DROP TABLE IF EXISTS `system_oss_storage`; -CREATE TABLE `system_oss_storage` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '创建者', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '更新者', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建日期', - `update_time` datetime NULL DEFAULT NULL COMMENT '更新时间', - `service_type` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '类型，比如minio', - `endpoint` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '服务地址', - `bucket_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '存储桶名称', - `file_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '完整文件名称', - `file_size` bigint NULL DEFAULT NULL COMMENT '文件大小, 单位：字节', - `file_mime` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '文件类型', - `file_prefix` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '短文件名', - `file_suffix` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '文件后缀', - `file_md5` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '文件md5', - `file_url` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL COMMENT '文件链接', - `file_code` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '文件编码', - `object_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '对象路径', - PRIMARY KEY (`id`) USING BTREE, - UNIQUE INDEX `udx_filemd5`(`file_md5` ASC) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = 'OSS存储' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_oss_storage --- ---------------------------- - --- ---------------------------- --- Table structure for system_quartz_job --- ---------------------------- -DROP TABLE IF EXISTS `system_quartz_job`; -CREATE TABLE `system_quartz_job` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `bean_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT 'Spring Bean名称', - `cron_expression` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT 'cron 表达式', - `is_pause` bit(1) NULL DEFAULT NULL COMMENT '状态：1暂停、0启用', - `job_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '任务名称', - `method_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '方法名称', - `params` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '参数', - `description` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '备注', - `person_in_charge` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '负责人', - `email` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '报警邮箱', - `sub_task` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '子任务ID', - `pause_after_failure` bit(1) NULL DEFAULT NULL COMMENT '任务失败后是否暂停', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '创建者', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '更新者', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建日期', - `update_time` datetime NULL DEFAULT NULL COMMENT '更新时间', - PRIMARY KEY (`id`) USING BTREE, - INDEX `idx_is_pause`(`is_pause` ASC) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 7 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '定时任务' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_quartz_job --- ---------------------------- -INSERT INTO `system_quartz_job` -VALUES (2, 'testTask', '0/5 * * * * ?', b'1', '测试1', 'run1', 'test', '带参测试，多参使用json', '测试', NULL, NULL, NULL, 'admin', 'admin', - '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_quartz_job` -VALUES (3, 'testTask', '0/5 * * * * ?', b'1', '测试', 'run', '', '不带参测试', 'Zheng Jie', '', '6', b'1', 'admin', 'admin', '2021-03-20 22:04:13', - '2021-03-20 22:04:13'); - --- ---------------------------- --- Table structure for system_quartz_log --- ---------------------------- -DROP TABLE IF EXISTS `system_quartz_log`; -CREATE TABLE `system_quartz_log` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `bean_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT 'Bean名称', - `cron_expression` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT 'cron 表达式', - `is_success` bit(1) NULL DEFAULT NULL COMMENT '是否执行成功', - `job_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '任务名称', - `method_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '方法名称', - `params` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '参数', - `time` bigint NULL DEFAULT NULL COMMENT '执行耗时', - `exception_detail` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL COMMENT '异常详情', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建时间', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '定时任务日志' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_quartz_log --- ---------------------------- - --- ---------------------------- --- Table structure for system_role --- ---------------------------- -DROP TABLE IF EXISTS `system_role`; -CREATE TABLE `system_role` -( - `role_id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `name` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '名称', - `level` int NULL DEFAULT NULL COMMENT '角色级别', - `description` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '描述', - `data_scope` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '数据权限', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '创建者', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '更新者', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建日期', - `update_time` datetime NULL DEFAULT NULL COMMENT '更新时间', - PRIMARY KEY (`role_id`) USING BTREE, - UNIQUE INDEX `uniq_name`(`name` ASC) USING BTREE, - INDEX `idx_level`(`level` ASC) USING BTREE, - INDEX `idx_sys_role_level`(`level` ASC) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 8 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '角色表' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_role --- ---------------------------- -INSERT INTO `system_role` -VALUES (1, '超级管理员', 1, '6666', '全部', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_role` -VALUES (2, '普通用户', 2, '-', '本级', 'admin', 'admin', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); - --- ---------------------------- --- Table structure for system_roles_depts --- ---------------------------- -DROP TABLE IF EXISTS `system_roles_depts`; -CREATE TABLE `system_roles_depts` -( - `role_id` bigint NOT NULL COMMENT '角色ID', - `dept_id` bigint NOT NULL COMMENT '部门ID', - PRIMARY KEY (`role_id`, `dept_id`) USING BTREE, - INDEX `idx_role_id`(`role_id` ASC) USING BTREE, - INDEX `idx_dept_id`(`dept_id` ASC) USING BTREE, - INDEX `idx_sys_roles_depts_role_dept`(`role_id` ASC, `dept_id` ASC) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '角色部门关联' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_roles_depts --- ---------------------------- - --- ---------------------------- --- Table structure for system_roles_menus --- ---------------------------- -DROP TABLE IF EXISTS `system_roles_menus`; -CREATE TABLE `system_roles_menus` -( - `menu_id` bigint NOT NULL COMMENT '菜单ID', - `role_id` bigint NOT NULL COMMENT '角色ID', - PRIMARY KEY (`menu_id`, `role_id`) USING BTREE, - INDEX `idx_menu_id`(`menu_id` ASC) USING BTREE, - INDEX `idx_role_id`(`role_id` ASC) USING BTREE, - INDEX `idx_sys_roles_menus_role_menu`(`role_id` ASC, `menu_id` ASC) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '角色菜单关联' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_roles_menus --- ---------------------------- -INSERT INTO `system_roles_menus` -VALUES (1, 1); -INSERT INTO `system_roles_menus` -VALUES (2, 1); -INSERT INTO `system_roles_menus` -VALUES (3, 1); -INSERT INTO `system_roles_menus` -VALUES (5, 1); -INSERT INTO `system_roles_menus` -VALUES (6, 1); -INSERT INTO `system_roles_menus` -VALUES (9, 1); -INSERT INTO `system_roles_menus` -VALUES (10, 1); -INSERT INTO `system_roles_menus` -VALUES (10, 2); -INSERT INTO `system_roles_menus` -VALUES (11, 1); -INSERT INTO `system_roles_menus` -VALUES (11, 2); -INSERT INTO `system_roles_menus` -VALUES (14, 1); -INSERT INTO `system_roles_menus` -VALUES (18, 1); -INSERT INTO `system_roles_menus` -VALUES (18, 2); -INSERT INTO `system_roles_menus` -VALUES (21, 1); -INSERT INTO `system_roles_menus` -VALUES (21, 2); -INSERT INTO `system_roles_menus` -VALUES (22, 1); -INSERT INTO `system_roles_menus` -VALUES (22, 2); -INSERT INTO `system_roles_menus` -VALUES (23, 1); -INSERT INTO `system_roles_menus` -VALUES (23, 2); -INSERT INTO `system_roles_menus` -VALUES (24, 1); -INSERT INTO `system_roles_menus` -VALUES (24, 2); -INSERT INTO `system_roles_menus` -VALUES (27, 1); -INSERT INTO `system_roles_menus` -VALUES (27, 2); -INSERT INTO `system_roles_menus` -VALUES (28, 1); -INSERT INTO `system_roles_menus` -VALUES (34, 1); -INSERT INTO `system_roles_menus` -VALUES (34, 2); -INSERT INTO `system_roles_menus` -VALUES (35, 1); -INSERT INTO `system_roles_menus` -VALUES (36, 1); -INSERT INTO `system_roles_menus` -VALUES (36, 2); -INSERT INTO `system_roles_menus` -VALUES (37, 1); -INSERT INTO `system_roles_menus` -VALUES (39, 1); -INSERT INTO `system_roles_menus` -VALUES (41, 1); -INSERT INTO `system_roles_menus` -VALUES (44, 1); -INSERT INTO `system_roles_menus` -VALUES (45, 1); -INSERT INTO `system_roles_menus` -VALUES (46, 1); -INSERT INTO `system_roles_menus` -VALUES (48, 1); -INSERT INTO `system_roles_menus` -VALUES (49, 1); -INSERT INTO `system_roles_menus` -VALUES (50, 1); -INSERT INTO `system_roles_menus` -VALUES (52, 1); -INSERT INTO `system_roles_menus` -VALUES (53, 1); -INSERT INTO `system_roles_menus` -VALUES (54, 1); -INSERT INTO `system_roles_menus` -VALUES (56, 1); -INSERT INTO `system_roles_menus` -VALUES (57, 1); -INSERT INTO `system_roles_menus` -VALUES (58, 1); -INSERT INTO `system_roles_menus` -VALUES (60, 1); -INSERT INTO `system_roles_menus` -VALUES (61, 1); -INSERT INTO `system_roles_menus` -VALUES (62, 1); -INSERT INTO `system_roles_menus` -VALUES (64, 1); -INSERT INTO `system_roles_menus` -VALUES (65, 1); -INSERT INTO `system_roles_menus` -VALUES (66, 1); -INSERT INTO `system_roles_menus` -VALUES (73, 1); -INSERT INTO `system_roles_menus` -VALUES (74, 1); -INSERT INTO `system_roles_menus` -VALUES (75, 1); -INSERT INTO `system_roles_menus` -VALUES (77, 1); -INSERT INTO `system_roles_menus` -VALUES (77, 2); -INSERT INTO `system_roles_menus` -VALUES (78, 1); -INSERT INTO `system_roles_menus` -VALUES (78, 2); -INSERT INTO `system_roles_menus` -VALUES (79, 1); -INSERT INTO `system_roles_menus` -VALUES (79, 2); -INSERT INTO `system_roles_menus` -VALUES (80, 1); -INSERT INTO `system_roles_menus` -VALUES (80, 2); -INSERT INTO `system_roles_menus` -VALUES (83, 1); -INSERT INTO `system_roles_menus` -VALUES (83, 2); -INSERT INTO `system_roles_menus` -VALUES (117, 1); -INSERT INTO `system_roles_menus` -VALUES (117, 2); -INSERT INTO `system_roles_menus` -VALUES (118, 1); -INSERT INTO `system_roles_menus` -VALUES (118, 2); -INSERT INTO `system_roles_menus` -VALUES (119, 1); -INSERT INTO `system_roles_menus` -VALUES (119, 2); -INSERT INTO `system_roles_menus` -VALUES (121, 1); -INSERT INTO `system_roles_menus` -VALUES (121, 2); -INSERT INTO `system_roles_menus` -VALUES (122, 1); -INSERT INTO `system_roles_menus` -VALUES (122, 2); -INSERT INTO `system_roles_menus` -VALUES (125, 1); -INSERT INTO `system_roles_menus` -VALUES (125, 2); -INSERT INTO `system_roles_menus` -VALUES (126, 1); -INSERT INTO `system_roles_menus` -VALUES (126, 2); -INSERT INTO `system_roles_menus` -VALUES (127, 1); -INSERT INTO `system_roles_menus` -VALUES (127, 2); -INSERT INTO `system_roles_menus` -VALUES (128, 1); -INSERT INTO `system_roles_menus` -VALUES (128, 2); -INSERT INTO `system_roles_menus` -VALUES (129, 1); -INSERT INTO `system_roles_menus` -VALUES (129, 2); -INSERT INTO `system_roles_menus` -VALUES (130, 1); -INSERT INTO `system_roles_menus` -VALUES (130, 2); -INSERT INTO `system_roles_menus` -VALUES (132, 1); -INSERT INTO `system_roles_menus` -VALUES (132, 2); -INSERT INTO `system_roles_menus` -VALUES (150, 1); - --- ---------------------------- --- Table structure for system_user --- ---------------------------- -DROP TABLE IF EXISTS `system_user`; -CREATE TABLE `system_user` -( - `user_id` bigint NOT NULL AUTO_INCREMENT COMMENT 'ID', - `dept_id` bigint NULL DEFAULT NULL COMMENT '部门名称', - `username` varchar(180) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '用户名', - `nick_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '昵称', - `gender` varchar(2) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '性别', - `phone` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '手机号码', - `email` varchar(180) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '邮箱', - `avatar_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '头像地址', - `avatar_path` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '头像真实路径', - `password` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '密码', - `is_admin` bit(1) NULL DEFAULT b'0' COMMENT '是否为admin账号', - `enabled` bit(1) NULL DEFAULT NULL COMMENT '状态：1启用、0禁用', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '创建者', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '更新者', - `pwd_reset_time` datetime NULL DEFAULT NULL COMMENT '修改密码的时间', - `create_time` datetime NULL DEFAULT NULL COMMENT '创建日期', - `update_time` datetime NULL DEFAULT NULL COMMENT '更新时间', - PRIMARY KEY (`user_id`) USING BTREE, - UNIQUE INDEX `uniq_email`(`email` ASC) USING BTREE, - UNIQUE INDEX `uniq_username`(`username` ASC) USING BTREE, - INDEX `idx_dept_id`(`dept_id` ASC) USING BTREE, - INDEX `idx_enabled`(`enabled` ASC) USING BTREE, - INDEX `uniq_phone`(`phone` ASC) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 105 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '系统用户' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_user --- ---------------------------- -INSERT INTO `system_user` -VALUES (1, 2, 'admin', '管理员', '男', '18888888888', '1943815081@qq.com', '', '', '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'1', b'1', - 'admin', 'admin', '2020-05-03 16:38:31', '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (4, 2, 'odboy100', 'odboy100测试用户', '男', '18797874100', '1943815100@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (5, 2, 'odboy101', 'odboy101测试用户', '男', '18797874101', '1943815101@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (6, 2, 'odboy102', 'odboy102测试用户', '男', '18797874102', '1943815102@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (7, 2, 'odboy103', 'odboy103测试用户', '男', '18797874103', '1943815103@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (8, 2, 'odboy104', 'odboy104测试用户', '男', '18797874104', '1943815104@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (9, 2, 'odboy105', 'odboy105测试用户', '男', '18797874105', '1943815105@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (10, 2, 'odboy106', 'odboy106测试用户', '男', '18797874106', '1943815106@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (11, 2, 'odboy107', 'odboy107测试用户', '男', '18797874107', '1943815107@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (12, 2, 'odboy108', 'odboy108测试用户', '男', '18797874108', '1943815108@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (13, 2, 'odboy109', 'odboy109测试用户', '男', '18797874109', '1943815109@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (14, 2, 'odboy110', 'odboy110测试用户', '男', '18797874110', '1943815110@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (15, 2, 'odboy111', 'odboy111测试用户', '男', '18797874111', '1943815111@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (16, 2, 'odboy112', 'odboy112测试用户', '男', '18797874112', '1943815112@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (17, 2, 'odboy113', 'odboy113测试用户', '男', '18797874113', '1943815113@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (18, 2, 'odboy114', 'odboy114测试用户', '男', '18797874114', '1943815114@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (19, 2, 'odboy115', 'odboy115测试用户', '男', '18797874115', '1943815115@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (20, 2, 'odboy116', 'odboy116测试用户', '男', '18797874116', '1943815116@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (21, 2, 'odboy117', 'odboy117测试用户', '男', '18797874117', '1943815117@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (22, 2, 'odboy118', 'odboy118测试用户', '男', '18797874118', '1943815118@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (23, 2, 'odboy119', 'odboy119测试用户', '男', '18797874119', '1943815119@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (24, 2, 'odboy120', 'odboy120测试用户', '男', '18797874120', '1943815120@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (25, 2, 'odboy121', 'odboy121测试用户', '男', '18797874121', '1943815121@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (26, 2, 'odboy122', 'odboy122测试用户', '男', '18797874122', '1943815122@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (27, 2, 'odboy123', 'odboy123测试用户', '男', '18797874123', '1943815123@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (28, 2, 'odboy124', 'odboy124测试用户', '男', '18797874124', '1943815124@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (29, 2, 'odboy125', 'odboy125测试用户', '男', '18797874125', '1943815125@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (30, 2, 'odboy126', 'odboy126测试用户', '男', '18797874126', '1943815126@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (31, 2, 'odboy127', 'odboy127测试用户', '男', '18797874127', '1943815127@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (32, 2, 'odboy128', 'odboy128测试用户', '男', '18797874128', '1943815128@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (33, 2, 'odboy129', 'odboy129测试用户', '男', '18797874129', '1943815129@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (34, 2, 'odboy130', 'odboy130测试用户', '男', '18797874130', '1943815130@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (35, 2, 'odboy131', 'odboy131测试用户', '男', '18797874131', '1943815131@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (36, 2, 'odboy132', 'odboy132测试用户', '男', '18797874132', '1943815132@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (37, 2, 'odboy133', 'odboy133测试用户', '男', '18797874133', '1943815133@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (38, 2, 'odboy134', 'odboy134测试用户', '男', '18797874134', '1943815134@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (39, 2, 'odboy135', 'odboy135测试用户', '男', '18797874135', '1943815135@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (40, 2, 'odboy136', 'odboy136测试用户', '男', '18797874136', '1943815136@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (41, 2, 'odboy137', 'odboy137测试用户', '男', '18797874137', '1943815137@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (42, 2, 'odboy138', 'odboy138测试用户', '男', '18797874138', '1943815138@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (43, 2, 'odboy139', 'odboy139测试用户', '男', '18797874139', '1943815139@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (44, 2, 'odboy140', 'odboy140测试用户', '男', '18797874140', '1943815140@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (45, 2, 'odboy141', 'odboy141测试用户', '男', '18797874141', '1943815141@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (46, 2, 'odboy142', 'odboy142测试用户', '男', '18797874142', '1943815142@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (47, 2, 'odboy143', 'odboy143测试用户', '男', '18797874143', '1943815143@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (48, 2, 'odboy144', 'odboy144测试用户', '男', '18797874144', '1943815144@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (49, 2, 'odboy145', 'odboy145测试用户', '男', '18797874145', '1943815145@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (50, 2, 'odboy146', 'odboy146测试用户', '男', '18797874146', '1943815146@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (51, 2, 'odboy147', 'odboy147测试用户', '男', '18797874147', '1943815147@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (52, 2, 'odboy148', 'odboy148测试用户', '男', '18797874148', '1943815148@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (53, 2, 'odboy149', 'odboy149测试用户', '男', '18797874149', '1943815149@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (54, 2, 'odboy150', 'odboy150测试用户', '男', '18797874150', '1943815150@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (55, 2, 'odboy151', 'odboy151测试用户', '男', '18797874151', '1943815151@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (56, 2, 'odboy152', 'odboy152测试用户', '男', '18797874152', '1943815152@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (57, 2, 'odboy153', 'odboy153测试用户', '男', '18797874153', '1943815153@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (58, 2, 'odboy154', 'odboy154测试用户', '男', '18797874154', '1943815154@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (59, 2, 'odboy155', 'odboy155测试用户', '男', '18797874155', '1943815155@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (60, 2, 'odboy156', 'odboy156测试用户', '男', '18797874156', '1943815156@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (61, 2, 'odboy157', 'odboy157测试用户', '男', '18797874157', '1943815157@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (62, 2, 'odboy158', 'odboy158测试用户', '男', '18797874158', '1943815158@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (63, 2, 'odboy159', 'odboy159测试用户', '男', '18797874159', '1943815159@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (64, 2, 'odboy160', 'odboy160测试用户', '男', '18797874160', '1943815160@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (65, 2, 'odboy161', 'odboy161测试用户', '男', '18797874161', '1943815161@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (66, 2, 'odboy162', 'odboy162测试用户', '男', '18797874162', '1943815162@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (67, 2, 'odboy163', 'odboy163测试用户', '男', '18797874163', '1943815163@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (68, 2, 'odboy164', 'odboy164测试用户', '男', '18797874164', '1943815164@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (69, 2, 'odboy165', 'odboy165测试用户', '男', '18797874165', '1943815165@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (70, 2, 'odboy166', 'odboy166测试用户', '男', '18797874166', '1943815166@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (71, 2, 'odboy167', 'odboy167测试用户', '男', '18797874167', '1943815167@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (72, 2, 'odboy168', 'odboy168测试用户', '男', '18797874168', '1943815168@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (73, 2, 'odboy169', 'odboy169测试用户', '男', '18797874169', '1943815169@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (74, 2, 'odboy170', 'odboy170测试用户', '男', '18797874170', '1943815170@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (75, 2, 'odboy171', 'odboy171测试用户', '男', '18797874171', '1943815171@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (76, 2, 'odboy172', 'odboy172测试用户', '男', '18797874172', '1943815172@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (77, 2, 'odboy173', 'odboy173测试用户', '男', '18797874173', '1943815173@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (78, 2, 'odboy174', 'odboy174测试用户', '男', '18797874174', '1943815174@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (79, 2, 'odboy175', 'odboy175测试用户', '男', '18797874175', '1943815175@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (80, 2, 'odboy176', 'odboy176测试用户', '男', '18797874176', '1943815176@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (81, 2, 'odboy177', 'odboy177测试用户', '男', '18797874177', '1943815177@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (82, 2, 'odboy178', 'odboy178测试用户', '男', '18797874178', '1943815178@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (83, 2, 'odboy179', 'odboy179测试用户', '男', '18797874179', '1943815179@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (84, 2, 'odboy180', 'odboy180测试用户', '男', '18797874180', '1943815180@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (85, 2, 'odboy181', 'odboy181测试用户', '男', '18797874181', '1943815181@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (86, 2, 'odboy182', 'odboy182测试用户', '男', '18797874182', '1943815182@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (87, 2, 'odboy183', 'odboy183测试用户', '男', '18797874183', '1943815183@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (88, 2, 'odboy184', 'odboy184测试用户', '男', '18797874184', '1943815184@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (89, 2, 'odboy185', 'odboy185测试用户', '男', '18797874185', '1943815185@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (90, 2, 'odboy186', 'odboy186测试用户', '男', '18797874186', '1943815186@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (91, 2, 'odboy187', 'odboy187测试用户', '男', '18797874187', '1943815187@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (92, 2, 'odboy188', 'odboy188测试用户', '男', '18797874188', '1943815188@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (93, 2, 'odboy189', 'odboy189测试用户', '男', '18797874189', '1943815189@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (94, 2, 'odboy190', 'odboy190测试用户', '男', '18797874190', '1943815190@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (95, 2, 'odboy191', 'odboy191测试用户', '男', '18797874191', '1943815191@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (96, 2, 'odboy192', 'odboy192测试用户', '男', '18797874192', '1943815192@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (97, 2, 'odboy193', 'odboy193测试用户', '男', '18797874193', '1943815193@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (98, 2, 'odboy194', 'odboy194测试用户', '男', '18797874194', '1943815194@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (99, 2, 'odboy195', 'odboy195测试用户', '男', '18797874195', '1943815195@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (100, 2, 'odboy196', 'odboy196测试用户', '男', '18797874196', '1943815196@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (101, 2, 'odboy197', 'odboy197测试用户', '男', '18797874197', '1943815197@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (102, 2, 'odboy198', 'odboy198测试用户', '男', '18797874198', '1943815198@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); -INSERT INTO `system_user` -VALUES (103, 2, 'odboy199', 'odboy199测试用户', '男', '18797874199', '1943815199@qq.com', NULL, NULL, - '$2a$10$Egp1/gvFlt7zhlXVfEFw4OfWQCGPw0ClmMcc6FjTnvXNRVf9zdMRa', b'0', b'1', 'admin', 'admin', NULL, '2021-03-20 22:04:13', '2021-03-20 22:04:13'); - --- ---------------------------- --- Table structure for system_users_jobs --- ---------------------------- -DROP TABLE IF EXISTS `system_users_jobs`; -CREATE TABLE `system_users_jobs` -( - `user_id` bigint NOT NULL COMMENT '用户ID', - `job_id` bigint NOT NULL COMMENT '岗位ID', - PRIMARY KEY (`user_id`, `job_id`) USING BTREE, - INDEX `idx_user_id`(`user_id` ASC) USING BTREE, - INDEX `idx_job_id`(`job_id` ASC) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '用户与岗位关联表' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_users_jobs --- ---------------------------- -INSERT INTO `system_users_jobs` -VALUES (1, 11); -INSERT INTO `system_users_jobs` -VALUES (3, 11); -INSERT INTO `system_users_jobs` -VALUES (4, 11); -INSERT INTO `system_users_jobs` -VALUES (5, 11); -INSERT INTO `system_users_jobs` -VALUES (6, 11); -INSERT INTO `system_users_jobs` -VALUES (7, 11); -INSERT INTO `system_users_jobs` -VALUES (8, 11); -INSERT INTO `system_users_jobs` -VALUES (9, 11); -INSERT INTO `system_users_jobs` -VALUES (10, 11); -INSERT INTO `system_users_jobs` -VALUES (11, 11); -INSERT INTO `system_users_jobs` -VALUES (12, 11); -INSERT INTO `system_users_jobs` -VALUES (13, 11); -INSERT INTO `system_users_jobs` -VALUES (14, 11); -INSERT INTO `system_users_jobs` -VALUES (15, 11); -INSERT INTO `system_users_jobs` -VALUES (16, 11); -INSERT INTO `system_users_jobs` -VALUES (17, 11); -INSERT INTO `system_users_jobs` -VALUES (18, 11); -INSERT INTO `system_users_jobs` -VALUES (19, 11); -INSERT INTO `system_users_jobs` -VALUES (20, 11); -INSERT INTO `system_users_jobs` -VALUES (21, 11); -INSERT INTO `system_users_jobs` -VALUES (22, 11); -INSERT INTO `system_users_jobs` -VALUES (23, 11); -INSERT INTO `system_users_jobs` -VALUES (24, 11); -INSERT INTO `system_users_jobs` -VALUES (25, 11); -INSERT INTO `system_users_jobs` -VALUES (26, 11); -INSERT INTO `system_users_jobs` -VALUES (27, 11); -INSERT INTO `system_users_jobs` -VALUES (28, 11); -INSERT INTO `system_users_jobs` -VALUES (29, 11); -INSERT INTO `system_users_jobs` -VALUES (30, 11); -INSERT INTO `system_users_jobs` -VALUES (31, 11); -INSERT INTO `system_users_jobs` -VALUES (32, 11); -INSERT INTO `system_users_jobs` -VALUES (33, 11); -INSERT INTO `system_users_jobs` -VALUES (34, 11); -INSERT INTO `system_users_jobs` -VALUES (35, 11); -INSERT INTO `system_users_jobs` -VALUES (36, 11); -INSERT INTO `system_users_jobs` -VALUES (37, 11); -INSERT INTO `system_users_jobs` -VALUES (38, 11); -INSERT INTO `system_users_jobs` -VALUES (39, 11); -INSERT INTO `system_users_jobs` -VALUES (40, 11); -INSERT INTO `system_users_jobs` -VALUES (41, 11); -INSERT INTO `system_users_jobs` -VALUES (42, 11); -INSERT INTO `system_users_jobs` -VALUES (43, 11); -INSERT INTO `system_users_jobs` -VALUES (44, 11); -INSERT INTO `system_users_jobs` -VALUES (45, 11); -INSERT INTO `system_users_jobs` -VALUES (46, 11); -INSERT INTO `system_users_jobs` -VALUES (47, 11); -INSERT INTO `system_users_jobs` -VALUES (48, 11); -INSERT INTO `system_users_jobs` -VALUES (49, 11); -INSERT INTO `system_users_jobs` -VALUES (50, 11); -INSERT INTO `system_users_jobs` -VALUES (51, 11); -INSERT INTO `system_users_jobs` -VALUES (52, 11); -INSERT INTO `system_users_jobs` -VALUES (53, 11); -INSERT INTO `system_users_jobs` -VALUES (54, 11); -INSERT INTO `system_users_jobs` -VALUES (55, 11); -INSERT INTO `system_users_jobs` -VALUES (56, 11); -INSERT INTO `system_users_jobs` -VALUES (57, 11); -INSERT INTO `system_users_jobs` -VALUES (58, 11); -INSERT INTO `system_users_jobs` -VALUES (59, 11); -INSERT INTO `system_users_jobs` -VALUES (60, 11); -INSERT INTO `system_users_jobs` -VALUES (61, 11); -INSERT INTO `system_users_jobs` -VALUES (62, 11); -INSERT INTO `system_users_jobs` -VALUES (63, 11); -INSERT INTO `system_users_jobs` -VALUES (64, 11); -INSERT INTO `system_users_jobs` -VALUES (65, 11); -INSERT INTO `system_users_jobs` -VALUES (66, 11); -INSERT INTO `system_users_jobs` -VALUES (67, 11); -INSERT INTO `system_users_jobs` -VALUES (68, 11); -INSERT INTO `system_users_jobs` -VALUES (69, 11); -INSERT INTO `system_users_jobs` -VALUES (70, 11); -INSERT INTO `system_users_jobs` -VALUES (71, 11); -INSERT INTO `system_users_jobs` -VALUES (72, 11); -INSERT INTO `system_users_jobs` -VALUES (73, 11); -INSERT INTO `system_users_jobs` -VALUES (74, 11); -INSERT INTO `system_users_jobs` -VALUES (75, 11); -INSERT INTO `system_users_jobs` -VALUES (76, 11); -INSERT INTO `system_users_jobs` -VALUES (77, 11); -INSERT INTO `system_users_jobs` -VALUES (78, 11); -INSERT INTO `system_users_jobs` -VALUES (79, 11); -INSERT INTO `system_users_jobs` -VALUES (80, 11); -INSERT INTO `system_users_jobs` -VALUES (81, 11); -INSERT INTO `system_users_jobs` -VALUES (82, 11); -INSERT INTO `system_users_jobs` -VALUES (83, 11); -INSERT INTO `system_users_jobs` -VALUES (84, 11); -INSERT INTO `system_users_jobs` -VALUES (85, 11); -INSERT INTO `system_users_jobs` -VALUES (86, 11); -INSERT INTO `system_users_jobs` -VALUES (87, 11); -INSERT INTO `system_users_jobs` -VALUES (88, 11); -INSERT INTO `system_users_jobs` -VALUES (89, 11); -INSERT INTO `system_users_jobs` -VALUES (90, 11); -INSERT INTO `system_users_jobs` -VALUES (91, 11); -INSERT INTO `system_users_jobs` -VALUES (92, 11); -INSERT INTO `system_users_jobs` -VALUES (93, 11); -INSERT INTO `system_users_jobs` -VALUES (94, 11); -INSERT INTO `system_users_jobs` -VALUES (95, 11); -INSERT INTO `system_users_jobs` -VALUES (96, 11); -INSERT INTO `system_users_jobs` -VALUES (97, 11); -INSERT INTO `system_users_jobs` -VALUES (98, 11); -INSERT INTO `system_users_jobs` -VALUES (99, 11); -INSERT INTO `system_users_jobs` -VALUES (100, 11); -INSERT INTO `system_users_jobs` -VALUES (101, 11); -INSERT INTO `system_users_jobs` -VALUES (102, 11); -INSERT INTO `system_users_jobs` -VALUES (103, 11); - --- ---------------------------- --- Table structure for system_users_roles --- ---------------------------- -DROP TABLE IF EXISTS `system_users_roles`; -CREATE TABLE `system_users_roles` -( - `user_id` bigint NOT NULL COMMENT '用户ID', - `role_id` bigint NOT NULL COMMENT '角色ID', - PRIMARY KEY (`user_id`, `role_id`) USING BTREE, - INDEX `idx_user_id`(`user_id` ASC) USING BTREE, - INDEX `idx_role_id`(`role_id` ASC) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '用户角色关联' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of system_users_roles --- ---------------------------- -INSERT INTO `system_users_roles` -VALUES (1, 1); -INSERT INTO `system_users_roles` -VALUES (3, 2); -INSERT INTO `system_users_roles` -VALUES (4, 2); -INSERT INTO `system_users_roles` -VALUES (5, 2); -INSERT INTO `system_users_roles` -VALUES (6, 2); -INSERT INTO `system_users_roles` -VALUES (7, 2); -INSERT INTO `system_users_roles` -VALUES (8, 2); -INSERT INTO `system_users_roles` -VALUES (9, 2); -INSERT INTO `system_users_roles` -VALUES (10, 2); -INSERT INTO `system_users_roles` -VALUES (11, 2); -INSERT INTO `system_users_roles` -VALUES (12, 2); -INSERT INTO `system_users_roles` -VALUES (13, 2); -INSERT INTO `system_users_roles` -VALUES (14, 2); -INSERT INTO `system_users_roles` -VALUES (15, 2); -INSERT INTO `system_users_roles` -VALUES (16, 2); -INSERT INTO `system_users_roles` -VALUES (17, 2); -INSERT INTO `system_users_roles` -VALUES (18, 2); -INSERT INTO `system_users_roles` -VALUES (19, 2); -INSERT INTO `system_users_roles` -VALUES (20, 2); -INSERT INTO `system_users_roles` -VALUES (21, 2); -INSERT INTO `system_users_roles` -VALUES (22, 2); -INSERT INTO `system_users_roles` -VALUES (23, 2); -INSERT INTO `system_users_roles` -VALUES (24, 2); -INSERT INTO `system_users_roles` -VALUES (25, 2); -INSERT INTO `system_users_roles` -VALUES (26, 2); -INSERT INTO `system_users_roles` -VALUES (27, 2); -INSERT INTO `system_users_roles` -VALUES (28, 2); -INSERT INTO `system_users_roles` -VALUES (29, 2); -INSERT INTO `system_users_roles` -VALUES (30, 2); -INSERT INTO `system_users_roles` -VALUES (31, 2); -INSERT INTO `system_users_roles` -VALUES (32, 2); -INSERT INTO `system_users_roles` -VALUES (33, 2); -INSERT INTO `system_users_roles` -VALUES (34, 2); -INSERT INTO `system_users_roles` -VALUES (35, 2); -INSERT INTO `system_users_roles` -VALUES (36, 2); -INSERT INTO `system_users_roles` -VALUES (37, 2); -INSERT INTO `system_users_roles` -VALUES (38, 2); -INSERT INTO `system_users_roles` -VALUES (39, 2); -INSERT INTO `system_users_roles` -VALUES (40, 2); -INSERT INTO `system_users_roles` -VALUES (41, 2); -INSERT INTO `system_users_roles` -VALUES (42, 2); -INSERT INTO `system_users_roles` -VALUES (43, 2); -INSERT INTO `system_users_roles` -VALUES (44, 2); -INSERT INTO `system_users_roles` -VALUES (45, 2); -INSERT INTO `system_users_roles` -VALUES (46, 2); -INSERT INTO `system_users_roles` -VALUES (47, 2); -INSERT INTO `system_users_roles` -VALUES (48, 2); -INSERT INTO `system_users_roles` -VALUES (49, 2); -INSERT INTO `system_users_roles` -VALUES (50, 2); -INSERT INTO `system_users_roles` -VALUES (51, 2); -INSERT INTO `system_users_roles` -VALUES (52, 2); -INSERT INTO `system_users_roles` -VALUES (53, 2); -INSERT INTO `system_users_roles` -VALUES (54, 2); -INSERT INTO `system_users_roles` -VALUES (55, 2); -INSERT INTO `system_users_roles` -VALUES (56, 2); -INSERT INTO `system_users_roles` -VALUES (57, 2); -INSERT INTO `system_users_roles` -VALUES (58, 2); -INSERT INTO `system_users_roles` -VALUES (59, 2); -INSERT INTO `system_users_roles` -VALUES (60, 2); -INSERT INTO `system_users_roles` -VALUES (61, 2); -INSERT INTO `system_users_roles` -VALUES (62, 2); -INSERT INTO `system_users_roles` -VALUES (63, 2); -INSERT INTO `system_users_roles` -VALUES (64, 2); -INSERT INTO `system_users_roles` -VALUES (65, 2); -INSERT INTO `system_users_roles` -VALUES (66, 2); -INSERT INTO `system_users_roles` -VALUES (67, 2); -INSERT INTO `system_users_roles` -VALUES (68, 2); -INSERT INTO `system_users_roles` -VALUES (69, 2); -INSERT INTO `system_users_roles` -VALUES (70, 2); -INSERT INTO `system_users_roles` -VALUES (71, 2); -INSERT INTO `system_users_roles` -VALUES (72, 2); -INSERT INTO `system_users_roles` -VALUES (73, 2); -INSERT INTO `system_users_roles` -VALUES (74, 2); -INSERT INTO `system_users_roles` -VALUES (75, 2); -INSERT INTO `system_users_roles` -VALUES (76, 2); -INSERT INTO `system_users_roles` -VALUES (77, 2); -INSERT INTO `system_users_roles` -VALUES (78, 2); -INSERT INTO `system_users_roles` -VALUES (79, 2); -INSERT INTO `system_users_roles` -VALUES (80, 2); -INSERT INTO `system_users_roles` -VALUES (81, 2); -INSERT INTO `system_users_roles` -VALUES (82, 2); -INSERT INTO `system_users_roles` -VALUES (83, 2); -INSERT INTO `system_users_roles` -VALUES (84, 2); -INSERT INTO `system_users_roles` -VALUES (85, 2); -INSERT INTO `system_users_roles` -VALUES (86, 2); -INSERT INTO `system_users_roles` -VALUES (87, 2); -INSERT INTO `system_users_roles` -VALUES (88, 2); -INSERT INTO `system_users_roles` -VALUES (89, 2); -INSERT INTO `system_users_roles` -VALUES (90, 2); -INSERT INTO `system_users_roles` -VALUES (91, 2); -INSERT INTO `system_users_roles` -VALUES (92, 2); -INSERT INTO `system_users_roles` -VALUES (93, 2); -INSERT INTO `system_users_roles` -VALUES (94, 2); -INSERT INTO `system_users_roles` -VALUES (95, 2); -INSERT INTO `system_users_roles` -VALUES (96, 2); -INSERT INTO `system_users_roles` -VALUES (97, 2); -INSERT INTO `system_users_roles` -VALUES (98, 2); -INSERT INTO `system_users_roles` -VALUES (99, 2); -INSERT INTO `system_users_roles` -VALUES (100, 2); -INSERT INTO `system_users_roles` -VALUES (101, 2); -INSERT INTO `system_users_roles` -VALUES (102, 2); -INSERT INTO `system_users_roles` -VALUES (103, 2); - --- ---------------------------- --- Table structure for task_instance_detail --- ---------------------------- -DROP TABLE IF EXISTS `task_instance_detail`; -CREATE TABLE `task_instance_detail` -( - `id` bigint NOT NULL COMMENT 'id', - `instance_id` bigint NOT NULL COMMENT '任务实例id', - `create_time` datetime NOT NULL COMMENT '创建时间', - `start_time` datetime NULL DEFAULT NULL COMMENT '开始时间', - `finish_time` datetime NULL DEFAULT NULL COMMENT '结束时间', - `biz_code` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '业务编码', - `biz_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '业务名称(步骤)', - `execute_params` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL COMMENT '执行参数', - `execute_info` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '执行信息', - `execute_status` varchar(20) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '执行状态(running进行中 success成功 fail失败)', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '任务实例明细' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of task_instance_detail --- ---------------------------- - --- ---------------------------- --- Table structure for task_instance_info --- ---------------------------- -DROP TABLE IF EXISTS `task_instance_info`; -CREATE TABLE `task_instance_info` -( - `id` bigint NOT NULL COMMENT 'id', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '创建人', - `create_time` datetime NOT NULL COMMENT '创建时间', - `update_time` datetime NOT NULL COMMENT '修改时间', - `context_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '名称', - `language` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '语言', - `change_type` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '变更类型', - `env_alias` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '环境别名', - `status` varchar(10) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '状态(running进行中 success成功 fail失败)', - `finish_time` datetime NULL DEFAULT NULL COMMENT '完成时间', - `source` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '来源', - `reason` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '变更原因', - `template` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL COMMENT '任务模板', - `job_data` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT 'QuartzJob参数', - `error_message` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL COMMENT '异常信息', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '任务实例' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of task_instance_info --- ---------------------------- - --- ---------------------------- --- Table structure for task_instance_step_detail --- ---------------------------- -DROP TABLE IF EXISTS `task_instance_step_detail`; -CREATE TABLE `task_instance_step_detail` -( - `id` bigint NOT NULL COMMENT 'id', - `create_time` datetime NOT NULL COMMENT '创建时间', - `instance_detail_id` bigint NOT NULL COMMENT 'task_instance_detail表id', - `step_desc` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '步骤描述', - `step_status` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '状态(success成功 fail失败)', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of task_instance_step_detail --- ---------------------------- - --- ---------------------------- --- Table structure for task_pipeline_config --- ---------------------------- -DROP TABLE IF EXISTS `task_pipeline_config`; -CREATE TABLE `task_pipeline_config` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '创建人', - `create_time` datetime NOT NULL COMMENT '创建时间', - `template_info_id` bigint NOT NULL COMMENT 'task_template_info表id', - `context_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '上下文名称', - `template_info` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '模板信息', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 4 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '任务流水线配置' ROW_FORMAT = DYNAMIC; - --- ---------------------------- --- Records of task_pipeline_config --- ---------------------------- -INSERT INTO `task_pipeline_config` -VALUES (1, 'admin', '2021-03-20 22:04:13', 4, 'cutejava', - '[{\"code\":\"node_init\",\"type\":\"service\",\"name\":\"初始化\",\"click\":\"true\",\"retry\":\"false\"},{\"code\":\"node_merge_branch\",\"type\":\"service\",\"name\":\"合并代码\",\"click\":\"true\",\"retry\":\"true\"},{\"code\":\"node_build_java\",\"type\":\"service\",\"name\":\"构建\",\"click\":\"true\",\"retry\":\"true\",\"detailType\":\"gitlab\",\"parameters\":{\"tags\":\"java\",\"job\":\"build\",\"version\":\"jdk11\"}},{\"code\":\"node_deploy_java\",\"type\":\"service\",\"name\":\"部署\",\"click\":\"true\",\"retry\":\"true\",\"buttons\":[{\"type\":\"link\",\"title\":\"查看部署详情\",\"code\":\"success\",\"parameters\":{\"isBlank\":\"true\"}}]}]'); -INSERT INTO `task_pipeline_config` -VALUES (2, 'admin', '2021-03-20 22:04:13', 5, 'cutejava', - '[{\"code\":\"node_init\",\"type\":\"service\",\"name\":\"初始化\",\"click\":\"true\",\"retry\":\"false\"},{\"code\":\"node_merge_branch\",\"type\":\"service\",\"name\":\"合并代码\",\"click\":\"true\",\"retry\":\"true\"},{\"code\":\"node_build_java\",\"type\":\"service\",\"name\":\"构建\",\"click\":\"true\",\"retry\":\"true\",\"detailType\":\"gitlab\",\"parameters\":{\"tags\":\"java\",\"job\":\"build\",\"version\":\"jdk11\"}},{\"code\":\"node_deploy_java\",\"type\":\"service\",\"name\":\"部署\",\"click\":\"true\",\"retry\":\"true\",\"buttons\":[{\"type\":\"link\",\"title\":\"查看部署详情\",\"code\":\"success\",\"parameters\":{\"isBlank\":\"true\"}}]}]'); -INSERT INTO `task_pipeline_config` -VALUES (3, 'admin', '2021-03-20 22:04:13', 6, 'cutejava', - '[{\"code\":\"node_init\",\"type\":\"service\",\"name\":\"初始化\",\"click\":\"true\",\"retry\":\"false\"},{\"code\":\"node_merge_branch\",\"type\":\"service\",\"name\":\"合并代码\",\"click\":\"true\",\"retry\":\"true\"},{\"code\":\"node_build_java\",\"type\":\"service\",\"name\":\"构建\",\"click\":\"true\",\"retry\":\"true\",\"detailType\":\"gitlab\",\"parameters\":{\"tags\":\"java\",\"job\":\"build\",\"version\":\"jdk11\"}},{\"code\":\"node_image_scan\",\"type\":\"service\",\"name\":\"镜像扫描\",\"click\":\"true\",\"retry\":\"true\",\"detailType\":\"gitlab\",\"parameters\":{\"job\":\"image-scan\"}},{\"code\":\"node_approve_deploy\",\"type\":\"service\",\"name\":\"部署审批\",\"click\":\"false\",\"retry\":\"true\",\"buttons\":[{\"type\":\"execute\",\"title\":\"同意\",\"code\":\"agree\",\"parameters\":{}},{\"type\":\"execute\",\"title\":\"拒绝\",\"code\":\"refuse\",\"parameters\":{}}]},{\"code\":\"node_deploy_java\",\"type\":\"service\",\"name\":\"部署\",\"click\":\"true\",\"retry\":\"false\",\"buttons\":[{\"type\":\"link\",\"title\":\"查看部署详情\",\"code\":\"success\",\"parameters\":{\"isBlank\":\"true\"}}]},{\"code\":\"node_merge_confirm\",\"type\":\"service\",\"name\":\"合并确认\",\"click\":\"false\",\"retry\":\"false\",\"buttons\":[{\"type\":\"execute\",\"title\":\"通过\",\"code\":\"agree\",\"parameters\":{}}]},{\"code\":\"node_merge_master\",\"type\":\"service\",\"name\":\"合并回Master\",\"click\":\"false\",\"retry\":\"true\"}]'); - --- ---------------------------- --- Table structure for task_template_info --- ---------------------------- -DROP TABLE IF EXISTS `task_template_info`; -CREATE TABLE `task_template_info` -( - `id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id', - `create_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '创建人', - `create_time` datetime NOT NULL COMMENT '创建时间', - `update_by` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '修改人', - `update_time` datetime NOT NULL COMMENT '修改时间', - `available` tinyint(1) NOT NULL DEFAULT 1 COMMENT '数据有效性', - `change_type` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '变更类型', - `name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '流水线名称', - `description` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '流水线描述', - `template` text CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '流水线模板内容', - `env_alias` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '环境别名', - `language` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL COMMENT '应用为语言，资源为类型', - PRIMARY KEY (`id`) USING BTREE -) ENGINE = InnoDB AUTO_INCREMENT = 39 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci COMMENT = '任务模板' ROW_FORMAT = Dynamic; - --- ---------------------------- --- Records of task_template_info --- ---------------------------- -INSERT INTO `task_template_info` -VALUES (4, 'admin', '2021-03-20 22:04:13', 'admin', '2021-03-20 22:04:13', 1, 'AppContainerDeploy', '日常发布流水线', '日常环境流水线(Java)', - '[{\"code\":\"node_init\",\"type\":\"service\",\"name\":\"初始化\",\"click\":\"true\",\"retry\":\"false\"},{\"code\":\"node_merge_branch\",\"type\":\"service\",\"name\":\"合并代码\",\"click\":\"true\",\"retry\":\"true\"},{\"code\":\"node_build_java\",\"type\":\"service\",\"name\":\"构建\",\"click\":\"true\",\"retry\":\"true\",\"detailType\":\"gitlab\",\"parameters\":{\"tags\":\"java\",\"job\":\"build\",\"version\":\"jdk11\"}},{\"code\":\"node_deploy_java\",\"type\":\"service\",\"name\":\"部署\",\"click\":\"true\",\"retry\":\"true\",\"buttons\":[{\"type\":\"link\",\"title\":\"查看部署详情\",\"code\":\"success\",\"parameters\":{\"isBlank\":\"true\"}}]}]', - 'daily', 'java'); -INSERT INTO `task_template_info` -VALUES (5, 'admin', '2021-03-20 22:04:13', 'admin', '2021-03-20 22:04:13', 1, 'AppContainerDeploy', '预发发布流水线', '预发环境流水线(Java)', - '[{\"code\":\"node_init\",\"type\":\"service\",\"name\":\"初始化\",\"click\":\"true\",\"retry\":\"false\"},{\"code\":\"node_merge_branch\",\"type\":\"service\",\"name\":\"合并代码\",\"click\":\"true\",\"retry\":\"true\"},{\"code\":\"node_build_java\",\"type\":\"service\",\"name\":\"构建\",\"click\":\"true\",\"retry\":\"true\",\"detailType\":\"gitlab\",\"parameters\":{\"tags\":\"java\",\"job\":\"build\",\"version\":\"jdk11\"}},{\"code\":\"node_deploy_java\",\"type\":\"service\",\"name\":\"部署\",\"click\":\"true\",\"retry\":\"true\",\"buttons\":[{\"type\":\"link\",\"title\":\"查看部署详情\",\"code\":\"success\",\"parameters\":{\"isBlank\":\"true\"}}]}]', - 'stage', 'java'); -INSERT INTO `task_template_info` -VALUES (6, 'admin', '2021-03-20 22:04:13', 'admin', '2021-03-20 22:04:13', 1, 'AppContainerDeploy', '生产发布流水线', '生产环境流水线(Java)', - '[{\"code\":\"node_init\",\"type\":\"service\",\"name\":\"初始化\",\"click\":\"true\",\"retry\":\"false\"},{\"code\":\"node_merge_branch\",\"type\":\"service\",\"name\":\"合并代码\",\"click\":\"true\",\"retry\":\"true\"},{\"code\":\"node_build_java\",\"type\":\"service\",\"name\":\"构建\",\"click\":\"true\",\"retry\":\"true\",\"detailType\":\"gitlab\",\"parameters\":{\"tags\":\"java\",\"job\":\"build\",\"version\":\"jdk11\"}},{\"code\":\"node_image_scan\",\"type\":\"service\",\"name\":\"镜像扫描\",\"click\":\"true\",\"retry\":\"true\",\"detailType\":\"gitlab\",\"parameters\":{\"job\":\"image-scan\"}},{\"code\":\"node_approve_deploy\",\"type\":\"service\",\"name\":\"部署审批\",\"click\":\"false\",\"retry\":\"true\",\"buttons\":[{\"type\":\"execute\",\"title\":\"同意\",\"code\":\"agree\",\"parameters\":{}},{\"type\":\"execute\",\"title\":\"拒绝\",\"code\":\"refuse\",\"parameters\":{}}]},{\"code\":\"node_deploy_java\",\"type\":\"service\",\"name\":\"部署\",\"click\":\"true\",\"retry\":\"false\",\"buttons\":[{\"type\":\"link\",\"title\":\"查看部署详情\",\"code\":\"success\",\"parameters\":{\"isBlank\":\"true\"}}]},{\"code\":\"node_merge_confirm\",\"type\":\"service\",\"name\":\"合并确认\",\"click\":\"false\",\"retry\":\"false\",\"buttons\":[{\"type\":\"execute\",\"title\":\"通过\",\"code\":\"agree\",\"parameters\":{}}]},{\"code\":\"node_merge_master\",\"type\":\"service\",\"name\":\"合并回Master\",\"click\":\"false\",\"retry\":\"true\"}]', - 'production', 'java'); - -SET -FOREIGN_KEY_CHECKS = 1; diff --git a/cutejava/docs/mysql/readme.md b/cutejava/docs/mysql/readme.md deleted file mode 100644 index 0b2cd198..00000000 --- a/cutejava/docs/mysql/readme.md +++ /dev/null @@ -1,3 +0,0 @@ -数据库名称：cutejava -数据库编码：utf8mb4 -排序规则：utf8mb4_0900_ai_ci \ No newline at end of file diff --git a/cutejava/docs/nginx/cutejava-api.odboy.cn.conf b/cutejava/docs/nginx/cutejava-api.odboy.cn.conf deleted file mode 100644 index 821d68eb..00000000 --- a/cutejava/docs/nginx/cutejava-api.odboy.cn.conf +++ /dev/null @@ -1,28 +0,0 @@ -server -{ - # 监听[配置] - listen 443 ssl; - server_name cutejava-api.odboy.cn; - access_log /var/log/cutejava-api.odboy.cn_access.log main; - charset utf-8; - client_max_body_size 5m; - - # SSL[配置] - ssl_certificate /usr/local/nginx/conf/ssl/odboy.cn.pem; - ssl_certificate_key /usr/local/nginx/conf/ssl/odboy.cn.key; - ssl_session_timeout 5m; - ssl_protocols TLSv1 TLSv1.1 TLSv1.2; - ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4; - ssl_prefer_server_ciphers on; - - gzip_static on; - - location / { - proxy_pass http://127.0.0.1:8000; - proxy_set_header X-Forwarded-Proto $scheme; - proxy_set_header X-Forwarded-Port $server_port; - proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; - proxy_set_header Upgrade $http_upgrade; - proxy_set_header Connection "upgrade"; - } -} diff --git a/cutejava/docs/nginx/cutejava.odboy.cn.conf b/cutejava/docs/nginx/cutejava.odboy.cn.conf deleted file mode 100644 index 32fa473c..00000000 --- a/cutejava/docs/nginx/cutejava.odboy.cn.conf +++ /dev/null @@ -1,31 +0,0 @@ -server -{ - # 监听[配置] - listen 443 ssl; - server_name cutejava.odboy.cn; - access_log /var/log/cutejava.odboy.cn_access.log main; - charset utf-8; - client_max_body_size 5m; - - # SSL[配置] - ssl_certificate /usr/local/nginx/conf/ssl/odboy.cn.pem; - ssl_certificate_key /usr/local/nginx/conf/ssl/odboy.cn.key; - ssl_session_timeout 5m; - ssl_protocols TLSv1 TLSv1.1 TLSv1.2; - ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4; - ssl_prefer_server_ciphers on; - - gzip_static on; - - index index.html; - # dist上传的路径 - root /root/dist; - # 避免访问出现 404 错误 - location / { - try_files $uri $uri/ @router; - index index.html; - } - location @router { - rewrite ^.*$ /index.html last; - } -}