푰’풎 풉풉품, 푰 풂풎 풂 품풓풂풅풖풂풕풆 풔풕풖풅풆풏풕 풇풓풐풎 푵풂풏풋풊풏품, 푪풉풊풏풂.
- 푺풉풄풐풐풍: 푯풐풉풂풊 푼풏풊풗풆풓풔풊풕풚
- 푳풆풂풓풏풊풏품: 푰’풎 풄풖풓풓풆풏풕풍풚 풍풆풂풓풏풊풏품 풅풆풔풊품풏 풑풂풕풕풆풓풏, 푳풆풆풕풄풐풅풆, 풅풊풔풕풓풊풃풖풕풆풅 풔풚풔풕풆풎, 풎풊풅풅풍풆풘풂풓풆 풂풏풅 풔풐 풐풏.
- 푯풐풘 풕풐 풓풆풂풄풉 풎풆:푽푿
- 푴풚 풃풍풐품: 풉풕풕풑풔://풉풉품풚풚풅풔.풃풍풐품.풄풔풅풏.풏풆풕/
- 푷풓풐풇풆풔풔풊풐풏풂풍 풔풌풊풍풍풔:풎풚 풅풓풆풂풎
配置结构:
由于所有的服务都是在docker中起的,也就是说势会接触docker的network。所有的服务都位于一个network中,如果不手动配置网段和各个服务的ip的话,那么就会默认创建一个network并每个服务配置相应的ip,但是要记住,当你重新docker-compose构建修改过后的容器的时候,会将这些ip重新分配。 我们都知道,写项目的时候一定会写配置的对不对,如果你无法一次性部署好docker环境,万一以后要加什么东西,ip改来改去,对于你的项目中的ip配置这很糟糕。所以我的解决方法是:在docker-compose.yml中手动创建network并且为每一个服务写上特定的ip地址。
文末有所有配置文件的地址!!!!!可以直接复制稍加修改然后启动,但是有些东西你还是要手动配的,所以你有必要看完整个文章
1-3:MySQL 5.7 mysql:
container_name: royi-mysql
# 最新的mysql8版本
image: mysql:5.7
environment:
# mysql root用户密码
MYSQL_ROOT_PASSWORD: root
TZ: Asia/Shanghai
command:
--default-authentication-plugin=mysql_native_password
--character-set-server=utf8mb4
--collation-server=utf8mb4_general_ci
--explicit_defaults_for_timestamp=true
--lower_case_table_names=1
--max_allowed_packet=128M;
volumes:
# mysql的数据文件
- ./mysql/data:/var/lib/mysql
# mysql配置文件
- ./mysql/config:/etc/mysql/conf.d
ports:
- "3306:3306"
networks:
ruoyinet:
ipv4_address: 172.1.0.8
restart: always
1-4:Nginx+Nacos集群部署
1-4-1:Nginx配置
文件结构
Nginx做nacos的负载均衡,这里最重要的就是要配置对应的Grpc端口。为什么总是显示,启动若依项目,${nacosPort}+1000这个Grpc端口一直没有响应呢?因为大概率是你的Nginx里面没有配置。
nginx.conf
关键配置,我已经加了注释,服务是8881, 对应的8881+9881就是Grpc端口,172.1.0.7:9848 172.1.0.6:9848 172.1.0.5:9848 分别是3个nacos的地址(也就是我说的,我自己在docker-compose.yml配的)
user www-data; worker_processes auto; pid /run/nginx.pid; include /etc/nginx/modules-enabled SET NAMES utf8mb4; SET FOREIGN_KEY_CHECKS = 0; -- ---------------------------- -- Table structure for config_info -- ---------------------------- DROp TABLE IF EXISTS `config_info`; CREATE TABLE `config_info` ( `id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT 'id', `data_id` varchar(255) COLLATE utf8_bin NOT NULL COMMENT 'data_id', `group_id` varchar(255) COLLATE utf8_bin DEFAULT NULL, `content` longtext COLLATE utf8_bin NOT NULL COMMENT 'content', `md5` varchar(32) COLLATE utf8_bin DEFAULT NULL COMMENT 'md5', `gmt_create` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间', `gmt_modified` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '修改时间', `src_user` text COLLATE utf8_bin COMMENT 'source user', `src_ip` varchar(50) COLLATE utf8_bin DEFAULT NULL COMMENT 'source ip', `app_name` varchar(128) COLLATE utf8_bin DEFAULT NULL, `tenant_id` varchar(128) COLLATE utf8_bin DEFAULT '' COMMENT '租户字段', `c_desc` varchar(256) COLLATE utf8_bin DEFAULT NULL, `c_use` varchar(64) COLLATE utf8_bin DEFAULT NULL, `effect` varchar(64) COLLATE utf8_bin DEFAULT NULL, `type` varchar(64) COLLATE utf8_bin DEFAULT NULL, `c_schema` text COLLATE utf8_bin, PRIMARY KEY (`id`), UNIQUE KEY `uk_configinfo_datagrouptenant` (`data_id`,`group_id`,`tenant_id`) ) ENGINE=InnoDB AUTO_INCREMENT=62 DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='config_info'; -- ---------------------------- -- Table structure for config_info_aggr -- ---------------------------- DROP TABLE IF EXISTS `config_info_aggr`; CREATE TABLE `config_info_aggr` ( `id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT 'id', `data_id` varchar(255) COLLATE utf8_bin NOT NULL COMMENT 'data_id', `group_id` varchar(255) COLLATE utf8_bin NOT NULL COMMENT 'group_id', `datum_id` varchar(255) COLLATE utf8_bin NOT NULL COMMENT 'datum_id', `content` longtext COLLATE utf8_bin NOT NULL COMMENT '内容', `gmt_modified` datetime NOT NULL COMMENT '修改时间', `app_name` varchar(128) COLLATE utf8_bin DEFAULT NULL, `tenant_id` varchar(128) COLLATE utf8_bin DEFAULT '' COMMENT '租户字段', PRIMARY KEY (`id`), UNIQUE KEY `uk_configinfoaggr_datagrouptenantdatum` (`data_id`,`group_id`,`tenant_id`,`datum_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='增加租户字段'; -- ---------------------------- -- Table structure for config_info_beta -- ---------------------------- DROP TABLE IF EXISTS `config_info_beta`; CREATE TABLE `config_info_beta` ( `id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT 'id', `data_id` varchar(255) COLLATE utf8_bin NOT NULL COMMENT 'data_id', `group_id` varchar(128) COLLATE utf8_bin NOT NULL COMMENT 'group_id', `app_name` varchar(128) COLLATE utf8_bin DEFAULT NULL COMMENT 'app_name', `content` longtext COLLATE utf8_bin NOT NULL COMMENT 'content', `beta_ips` varchar(1024) COLLATE utf8_bin DEFAULT NULL COMMENT 'betaIps', `md5` varchar(32) COLLATE utf8_bin DEFAULT NULL COMMENT 'md5', `gmt_create` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间', `gmt_modified` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '修改时间', `src_user` text COLLATE utf8_bin COMMENT 'source user', `src_ip` varchar(50) COLLATE utf8_bin DEFAULT NULL COMMENT 'source ip', `tenant_id` varchar(128) COLLATE utf8_bin DEFAULT '' COMMENT '租户字段', PRIMARY KEY (`id`), UNIQUE KEY `uk_configinfobeta_datagrouptenant` (`data_id`,`group_id`,`tenant_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='config_info_beta'; -- ---------------------------- -- Table structure for config_info_tag -- ---------------------------- DROP TABLE IF EXISTS `config_info_tag`; CREATE TABLE `config_info_tag` ( `id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT 'id', `data_id` varchar(255) COLLATE utf8_bin NOT NULL COMMENT 'data_id', `group_id` varchar(128) COLLATE utf8_bin NOT NULL COMMENT 'group_id', `tenant_id` varchar(128) COLLATE utf8_bin DEFAULT '' COMMENT 'tenant_id', `tag_id` varchar(128) COLLATE utf8_bin NOT NULL COMMENT 'tag_id', `app_name` varchar(128) COLLATE utf8_bin DEFAULT NULL COMMENT 'app_name', `content` longtext COLLATE utf8_bin NOT NULL COMMENT 'content', `md5` varchar(32) COLLATE utf8_bin DEFAULT NULL COMMENT 'md5', `gmt_create` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间', `gmt_modified` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '修改时间', `src_user` text COLLATE utf8_bin COMMENT 'source user', `src_ip` varchar(50) COLLATE utf8_bin DEFAULT NULL COMMENT 'source ip', PRIMARY KEY (`id`), UNIQUE KEY `uk_configinfotag_datagrouptenanttag` (`data_id`,`group_id`,`tenant_id`,`tag_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='config_info_tag'; -- ---------------------------- -- Table structure for config_tags_relation -- ---------------------------- DROP TABLE IF EXISTS `config_tags_relation`; CREATE TABLE `config_tags_relation` ( `id` bigint(20) NOT NULL COMMENT 'id', `tag_name` varchar(128) COLLATE utf8_bin NOT NULL COMMENT 'tag_name', `tag_type` varchar(64) COLLATE utf8_bin DEFAULT NULL COMMENT 'tag_type', `data_id` varchar(255) COLLATE utf8_bin NOT NULL COMMENT 'data_id', `group_id` varchar(128) COLLATE utf8_bin NOT NULL COMMENT 'group_id', `tenant_id` varchar(128) COLLATE utf8_bin DEFAULT '' COMMENT 'tenant_id', `nid` bigint(20) NOT NULL AUTO_INCREMENT, PRIMARY KEY (`nid`), UNIQUE KEY `uk_configtagrelation_configidtag` (`id`,`tag_name`,`tag_type`), KEY `idx_tenant_id` (`tenant_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='config_tag_relation'; -- ---------------------------- -- Table structure for group_capacity -- ---------------------------- DROP TABLE IF EXISTS `group_capacity`; CREATE TABLE `group_capacity` ( `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT COMMENT '主键ID', `group_id` varchar(128) COLLATE utf8_bin NOT NULL DEFAULT '' COMMENT 'Group ID,空字符表示整个集群', `quota` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '配额,0表示使用默认值', `usage` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '使用量', `max_size` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '单个配置大小上限,单位为字节,0表示使用默认值', `max_aggr_count` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '聚合子配置最大个数,,0表示使用默认值', `max_aggr_size` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '单个聚合数据的子配置大小上限,单位为字节,0表示使用默认值', `max_history_count` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '最大变更历史数量', `gmt_create` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间', `gmt_modified` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '修改时间', PRIMARY KEY (`id`), UNIQUE KEY `uk_group_id` (`group_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='集群、各Group容量信息表'; -- ---------------------------- -- Table structure for his_config_info -- ---------------------------- DROP TABLE IF EXISTS `his_config_info`; CREATE TABLE `his_config_info` ( `id` bigint(64) unsigned NOT NULL, `nid` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `data_id` varchar(255) COLLATE utf8_bin NOT NULL, `group_id` varchar(128) COLLATE utf8_bin NOT NULL, `app_name` varchar(128) COLLATE utf8_bin DEFAULT NULL COMMENT 'app_name', `content` longtext COLLATE utf8_bin NOT NULL, `md5` varchar(32) COLLATE utf8_bin DEFAULT NULL, `gmt_create` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP, `gmt_modified` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP, `src_user` text COLLATE utf8_bin, `src_ip` varchar(50) COLLATE utf8_bin DEFAULT NULL, `op_type` char(10) COLLATE utf8_bin DEFAULT NULL, `tenant_id` varchar(128) COLLATE utf8_bin DEFAULT '' COMMENT '租户字段', PRIMARY KEY (`nid`), KEY `idx_gmt_create` (`gmt_create`), KEY `idx_gmt_modified` (`gmt_modified`), KEY `idx_did` (`data_id`) ) ENGINE=InnoDB AUTO_INCREMENT=84 DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='多租户改造'; -- ---------------------------- -- Table structure for permissions -- ---------------------------- DROP TABLE IF EXISTS `permissions`; CREATE TABLE `permissions` ( `role` varchar(50) NOT NULL, `resource` varchar(255) NOT NULL, `action` varchar(8) NOT NULL, UNIQUE KEY `uk_role_permission` (`role`,`resource`,`action`) USING BTREE ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- ---------------------------- -- Table structure for roles -- ---------------------------- DROP TABLE IF EXISTS `roles`; CREATE TABLE `roles` ( `username` varchar(50) NOT NULL, `role` varchar(50) NOT NULL, UNIQUE KEY `idx_user_role` (`username`,`role`) USING BTREE ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- ---------------------------- -- Table structure for tenant_capacity -- ---------------------------- DROP TABLE IF EXISTS `tenant_capacity`; CREATE TABLE `tenant_capacity` ( `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT COMMENT '主键ID', `tenant_id` varchar(128) COLLATE utf8_bin NOT NULL DEFAULT '' COMMENT 'Tenant ID', `quota` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '配额,0表示使用默认值', `usage` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '使用量', `max_size` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '单个配置大小上限,单位为字节,0表示使用默认值', `max_aggr_count` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '聚合子配置最大个数', `max_aggr_size` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '单个聚合数据的子配置大小上限,单位为字节,0表示使用默认值', `max_history_count` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '最大变更历史数量', `gmt_create` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间', `gmt_modified` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '修改时间', PRIMARY KEY (`id`), UNIQUE KEY `uk_tenant_id` (`tenant_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='租户容量信息表'; -- ---------------------------- -- Table structure for tenant_info -- ---------------------------- DROP TABLE IF EXISTS `tenant_info`; CREATE TABLE `tenant_info` ( `id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT 'id', `kp` varchar(128) COLLATE utf8_bin NOT NULL COMMENT 'kp', `tenant_id` varchar(128) COLLATE utf8_bin DEFAULT '' COMMENT 'tenant_id', `tenant_name` varchar(128) COLLATE utf8_bin DEFAULT '' COMMENT 'tenant_name', `tenant_desc` varchar(256) COLLATE utf8_bin DEFAULT NULL COMMENT 'tenant_desc', `create_source` varchar(32) COLLATE utf8_bin DEFAULT NULL COMMENT 'create_source', `gmt_create` bigint(20) NOT NULL COMMENT '创建时间', `gmt_modified` bigint(20) NOT NULL COMMENT '修改时间', PRIMARY KEY (`id`), UNIQUE KEY `uk_tenant_info_kptenantid` (`kp`,`tenant_id`), KEY `idx_tenant_id` (`tenant_id`) ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='tenant_info'; -- ---------------------------- -- Table structure for users -- ---------------------------- DROP TABLE IF EXISTS `users`; CREATE TABLE `users` ( `username` varchar(50) NOT NULL, `password` varchar(500) NOT NULL, `enabled` tinyint(1) NOT NULL, PRIMARY KEY (`username`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; SET FOREIGN_KEY_CHECKS = 1;
nacos-hostname.env
#nacos dev env PREFER_HOST_MODE=hostname # docker实例别名,可以换成ip NACOS_SERVERS=nacos1:8848 nacos2:8848 nacos3:8848 MYSQL_SERVICE_HOST=mysql # 指定保存数据的数据库名称 MYSQL_SERVICE_DB_NAME=ry-config # 访问mysql端口 MYSQL_SERVICE_PORT=3306 # 访问mysql的用户名 MYSQL_SERVICE_USER=root # 访问mysql的密码 MYSQL_SERVICE_PASSWORD=root
custom.propeties 这个是nacos的服务的相关配置不用管它
nacos.naming.empty-service.auto-clean=true
nacos.naming.empty-service.clean.initial-delay-ms=50000
nacos.naming.empty-service.clean.period-time-ms=30000
management.endpoints.web.exposure.include=*
management.metrics.export.elastic.enabled=false
management.metrics.export.influx.enabled=false
server.tomcat.accesslog.enabled=true
server.tomcat.accesslog.pattern=%h %l %u %t "%r" %s %b %D %{User-Agent}i %{Request-Source}i
server.tomcat.basedir=
nacos.security.ignore.urls=/,/error,*.css,*.js,*.html,*.map,*.svg,*.png,*.ico,/console-ui/public/**,/v1/auth/**,/v1/console/health/**,/actuator/**,/v1/console/server/**
nacos.core.auth.system.type=nacos
nacos.core.auth.enabled=false
nacos.core.auth.default.token.expire.seconds=18000
nacos.core.auth.default.token.secret.key=SecretKey012345678901234567890123456789012345678901234567890123456789
nacos.core.auth.caching.enabled=true
nacos.core.auth.enable.userAgentAuthWhite=false
nacos.core.auth.server.identity.key=serverIdentity
nacos.core.auth.server.identity.value=security
nacos.istio.mcp.server.enabled=false
docker-compose.yml中的相关配置
nacos1:
hostname: nacos1
container_name: royi-nacos1
image: nacos/nacos-server:latest
volumes:
# 需要添加mysql8的插件
#- ./nacos/plugins/mysql/:/home/nacos/plugins/mysql/
# 把日志文件映射出来
- ./nacos/cluster-logs/nacos1:/home/nacos/logs
# 把配置文件映射出来
- ./nacos/init.d/custom.properties:/home/nacos/init.d/custom.properties
environment: # 设置环境变量,相当于docker run命令中的-e
- JVM_XMS=512m
- JVM_XMX=512m
- JVM_XMN=128m
- TZ=Asia/Shanghai
#- MODE=standalone
ports:
- "8848:8848"
- "9848:9848"
- "9555:9555"
env_file:
# 集群配置文件
- ./nacos/env/nacos-hostname.env
restart: always
depends_on:
- mysql
networks:
ruoyinet:
ipv4_address: 172.1.0.7
nacos2:
hostname: nacos2
image: nacos/nacos-server:latest
container_name: royi-nacos2
volumes:
#- ./nacos/plugins/mysql/:/home/nacos/plugins/mysql/
- ./nacos/cluster-logs/nacos2:/home/nacos/logs
- ./nacos/init.d/custom.properties:/home/nacos/init.d/custom.properties
environment: # 设置环境变量,相当于docker run命令中的-e
- JVM_XMS=512m
- JVM_XMX=512m
- JVM_XMN=128m
- TZ=Asia/Shanghai
ports:
- "8849:8848"
env_file:
- ./nacos/env/nacos-hostname.env
restart: always
depends_on:
- mysql
networks:
ruoyinet:
ipv4_address: 172.1.0.6
nacos3:
hostname: nacos3
image: nacos/nacos-server:latest
container_name: royi-nacos3
volumes:
#- ./nacos/plugins/mysql/:/home/nacos/plugins/mysql/
- ./nacos/cluster-logs/nacos3:/home/nacos/logs
- ./nacos/init.d/custom.properties:/home/nacos/init.d/custom.properties
environment: # 设置环境变量,相当于docker run命令中的-e
- JVM_XMS=512m
- JVM_XMX=512m
- JVM_XMN=128m
- TZ=Asia/Shanghai
ports:
- "8850:8848"
env_file:
- ./nacos/env/nacos-hostname.env
restart: always
depends_on:
- mysql
networks:
ruoyinet:
ipv4_address: 172.1.0.5
1-5:Redis
没啥好写的,直接用最后的github文件部署就行。
1-6:Sentinel如果你要用docker-compos部署sentinel,你需要使用sentinel-dashboard-1.7.2.jar 自己制作一个java镜像。步骤如下:
Dockerfile
FROM openjdk:8 #使用镜像 RUN sed -i "s/archive.ubuntu./mirrors.aliyun./g" /etc/apt/sources.list RUN sed -i "s/deb.debian.org/mirrors.aliyun.com/g" /etc/apt/sources.list RUN sed -i "s/security.debian.org/mirrors.aliyun.com/debian-security/g" /etc/apt/sources.list #复制上下文目录下的jar包到容器里 使用COPY命令亦可 ADD sentinel-dashboard-1.7.2.jar sentinel-dashboard-1.7.2.jar EXPOSE 8080 #指定容器启动程序及参数" " ENTRYPOINT ["java","-jar","sentinel-dashboard-1.7.2.jar"]
构建镜像的命令
docker build -t sentinel-dashboard-1.7.2 . REPOSITORY TAG IMAGE ID CREATED SIZE sentinel-dashboard-1.7.2 latest 442c56e77ebe 2 weeks ago 547MB
这样就可以用dokcer-compose构建容器了。没有镜像是启动不了的,也就是说我在docker-compose上用的是自己制作的sentinel本地镜像。
1-7:Seataseata我用的是基于数据库的。
注意事项
需要用这个sh文件将config.txt中的配置文件上传到nacos服务中去所以,你要保证先把nacos服务启动起来,也就是说,不能一次性启动整个,要先启动mysql(创建ry-seata库并且导入ry-seata.sql文件),nginx,nacos集群之后,你才能启动seata。还要做的事情就是要新建一个group和一个命名空间,这样你才有group和namespace命名空间的Id。
上传配置命令:
sh nacos-config.sh -h localhost -p 8848 -g SEATA_GROUP(你的group) -t 8f86ea8c-2a39-4728-bade-4af9ebece539(命名空间的ID) -u nacos(登录账号) -w naco(登录密码)
registry.conf命名空间的id和group同样要在registry中进行配置
#seata.tx-service-group=my_test_tx_group
registry {
type = "nacos"
nacos {
# seata服务注册在nacos上的别名,客户端通过该别名调用服务
application = "seata-server"
# 请根据实际生产环境配置nacos服务的ip和端口
serverAddr = "172.1.0.4:8881"
# nacos上指定的namespace
namespace = "2b19e55b-6325-4d48-87f1-7958f86d0053"
group = "SEATA_GROUP"
cluster = "default"
username = "nacos"
password = "nacos"
}
}
config {
type = "nacos"
nacos {
# 请根据实际生产环境配置nacos服务的ip和端口
serverAddr = "172.1.0.4:8881"
# nacos上指定的namespace
namespace = "2b19e55b-6325-4d48-87f1-7958f86d0053"
group = "SEATA_GROUP"
username = "nacos"
password = "nacos"
# 从v1.4.2版本开始,已支持从一个Nacos dataId中获取所有配置信息,你只需要额外添加一个dataId配置项(我尝试过,但是失败了)
#dataId: "seataServer.properties"
}
}
1-8:github地址:
配置文件获取github地址



