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 bb6b1914..00000000 Binary files a/cutejava/docs/help/IDEA换行调整.jpg and /dev/null differ 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; - } -}