Run on Docker on Tofuwine's Blog

使用 Docker 部署 Nacos

Wed, 12 Aug 2026 00:00:00 +0000

如果您是第一次阅读该系列文章，建议优先阅读 Docker 部署项目说明及索引

Docker Compose

以下是 Docker Compose 示例：(基于 Nacos 3.2.3)

version: "3.9"

services:
  nacos:
    image: nacos/nacos-server:latest
    container_name: nacos
    hostname: nacos
    restart: unless-stopped
    ports:
      - "8080:8080"
      - "8848:8848"
      - "9848:9848"
    volumes:
#      - /docker/nacos/conf/application.properties:/home/nacos/conf/application.properties  # 如需外置数据源则打开此配置
      - /docker/nacos/data:/home/nacos/data
      - /docker/nacos/logs:/home/nacos/logs
    environment:
      - TZ=Asia/Shanghai
      - PREFER_HOST_MODE=hostname
      - MODE=standalone
      - FUNCTION_MODE=microservice
      - NACOS_AUTH_IDENTITY_KEY=${your_nacos_server_identity_key}
      - NACOS_AUTH_IDENTITY_VALUE=${your_nacos_server_identity_value}
      - NACOS_AUTH_TOKEN=${your_nacos_auth_secret_token}
networks:
  default:
    external: true
    name: rod

配置说明

NACOS_AUTH_TOKEN: Nacos 用于生成 JWT Token 的密钥，使用长度大于 32 字符的字符串，再经过 Base64 编码。
NACOS_AUTH_IDENTITY_KEY: Nacos Server 端之间 Inner API 的身份标识的 Key，必填。
NACOS_AUTH_IDENTITY_VALUE: Nacos Server 端之间 Inner API 的身份标识的 Value，必填。

更多配置参考官网文档：系统参数

外置数据源说明

以 PostgreSQL 数据库为例：

创建 PostgreSQL 用户名及数据库
根据 nacos/conf/pg-schema.sql (Nacos 3.2.3 可根据附录: PostgreSQL 查看，其他版本可下载官方 nacos 安装包查看)，手动创建数据库表等数据
创建 application.properties 文件，并将上述 yml 中 volumes 相关注释打开。

配置文件主要修改如下内容：(注意：不同 nacos 版本相关配置可能不同，具体请参考官方文档。)

spring.sql.init.platform=postgresql
db.num=1
db.url.0=jdbc:postgresql://127.0.0.1:5432/nacos
db.user=nacos
db.password=nacos
db.pool.config.driverClassName=org.postgresql.Driver
db.pool.config.connectionTestQuery=SELECT 1

端口说明

Nacos 3.0 起，控制台端口与服务器端口解耦。默认端口如下：

端口	用途	暴露建议
`8080`	Nacos Console 端口	只向管理网络开放
`8848`	HTTP API 端口，用于 OpenAPI、Admin API 和部分插件请求	只向内部客户端、控制台或网关开放
`9848`	客户端 gRPC 端口	只向内部客户端开放，VIP/SLB 需要 TCP 转发
`9849`	服务端 gRPC 通信端口	只允许 Nacos Server 节点互通
`7848`	Raft 通信端口	只允许 Nacos Server 节点互通

使用 VIP、SLB 或 Nginx 时，9848 必须按 TCP 转发，不要按 HTTP 或 HTTP/2 代理。更多端口说明请参考部署手册概览

验证 Nacos 服务是否启动成功

通过 docker logs -f $container_id 命令，查看 Nacos 服务启动日志，如果看到如下日志，说明服务启动成功。

`1`	`Nacos started successfully in xxx mode. use xxx storage`

可通过如下方式，快速检验 Nacos 的功能。

Nacos 控制台页面

打开链接 http://localhost:8080，即可进入 Nacos 控制台页面。

注意：首次打开会要求初始化管理员用户 nacos 的密码。

服务注册

`1`	`curl -X POST 'http://127.0.0.1:8848/nacos/v3/client/ns/instance?serviceName=quickstart.test.service&ip=127.0.0.1&port=8080'`

服务发现

`1`	`curl -X GET 'http://127.0.0.1:8848/nacos/v3/client/ns/instance/list?serviceName=quickstart.test.service'`

发布配置

# 登陆获取access token
curl -X POST 'http://127.0.0.1:8848/nacos/v3/auth/user/login' -d 'username=nacos' -d 'password=${your_password}'
# 使用access token，创建配置
curl -X POST 'http://127.0.0.1:8848/nacos/v3/admin/cs/config?dataId=quickstart.test.config&groupName=test&content=HelloWorld' -H "accessToken:${your_access_token}"

注意：访问 Admin API，默认需要使用 access token，access token 可通过 POST /nacos/v3/auth/user/login 接口获得

获取配置

`1`	`curl -X GET 'http://127.0.0.1:8848/nacos/v3/client/cs/config?dataId=quickstart.test.config&groupName=test'`

NPM 反向代理

如果需要通过 NPM 设置反向代理，可参考如下方式：

注意：不推荐将 Nacos 映射到公网访问，仅做学习参考。

此处以 https://nacos.example.com 为例

如果未部署 NPM，可参考文章：使用 Docker 部署 Nginx Proxy Manager

Details

Domain Names: nacos.example.com
Scheme: http
Forward Hostname/IP: 127.0.0.1 (如果 NPM 未使用 HOST，则使用容器的 hostname: nacos)
Forward Port: 8080
Cache Assets: ✅

SSL

选择你已经配置好的 SSL Certificate，如 *.example.com, example.com
Force SSL: ✅
HTTP/2 Support: ✅
HSTS Enabled: ✅
HSTS Subdomains: ✅

注意：勾选 HSTS 设置，默认访问 https://nacos.example.com 时会跳转到 https://nacos.example.com/next ，如果不勾选 HSTS，会跳转到 http://nacos.example.com/next

Advanced

location / {
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    proxy_pass $forward_scheme://$server:$port;
}

参考网址

附录

PostgreSQL DDL

pg-schema.sql

/*
 * Copyright 1999-2018 Alibaba Group Holding Ltd.
 *
 * 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.
 */

-- ----------------------------
-- Table structure for config_info
-- ----------------------------
DROP TABLE IF EXISTS "config_info";
CREATE TABLE "config_info" (
  "id" bigserial NOT NULL,
  "data_id" varchar(255)  NOT NULL,
  "group_id" varchar(255) ,
  "content" text  NOT NULL,
  "md5" varchar(32) ,
  "gmt_create" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "gmt_modified" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "src_user" text ,
  "src_ip" varchar(20) ,
  "app_name" varchar(128) ,
  "tenant_id" varchar(128) NOT NULL DEFAULT '',
  "c_desc" varchar(256) ,
  "c_use" varchar(64) ,
  "effect" varchar(64) ,
  "type" varchar(64) ,
  "c_schema" text ,
  "encrypted_data_key" text  NOT NULL
)
;

COMMENT ON COLUMN "config_info"."id" IS 'id';
COMMENT ON COLUMN "config_info"."data_id" IS 'data_id';
COMMENT ON COLUMN "config_info"."content" IS 'content';
COMMENT ON COLUMN "config_info"."md5" IS 'md5';
COMMENT ON COLUMN "config_info"."gmt_create" IS '创建时间';
COMMENT ON COLUMN "config_info"."gmt_modified" IS '修改时间';
COMMENT ON COLUMN "config_info"."src_user" IS 'source user';
COMMENT ON COLUMN "config_info"."src_ip" IS 'source ip';
COMMENT ON COLUMN "config_info"."tenant_id" IS '租户字段';
COMMENT ON COLUMN "config_info"."encrypted_data_key" IS '秘钥';
COMMENT ON TABLE "config_info" IS 'config_info';

-- ----------------------------
-- Table structure for config_info_gray
-- ----------------------------
DROP TABLE IF EXISTS "config_info_gray";
CREATE TABLE "config_info_gray" (
  "id" bigserial NOT NULL,
  "data_id" varchar(255) NOT NULL,
  "group_id" varchar(128) NOT NULL,
  "content" text NOT NULL,
  "md5" varchar(32),
  "src_user" text,
  "src_ip" varchar(100),
  "gmt_create" timestamp(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "gmt_modified" timestamp(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "app_name" varchar(128),
  "tenant_id" varchar(128) NOT NULL DEFAULT '',
  "gray_name" varchar(128) NOT NULL,
  "gray_rule" text NOT NULL,
  "encrypted_data_key" varchar(256) NOT NULL DEFAULT ''
);

COMMENT ON COLUMN "config_info_gray"."id" IS 'id';
COMMENT ON COLUMN "config_info_gray"."data_id" IS 'data_id';
COMMENT ON COLUMN "config_info_gray"."group_id" IS 'group_id';
COMMENT ON COLUMN "config_info_gray"."content" IS 'content';
COMMENT ON COLUMN "config_info_gray"."md5" IS 'md5';
COMMENT ON COLUMN "config_info_gray"."src_user" IS 'source user';
COMMENT ON COLUMN "config_info_gray"."src_ip" IS 'source ip';
COMMENT ON COLUMN "config_info_gray"."gmt_create" IS '创建时间';
COMMENT ON COLUMN "config_info_gray"."gmt_modified" IS '修改时间';
COMMENT ON COLUMN "config_info_gray"."app_name" IS 'app_name';
COMMENT ON COLUMN "config_info_gray"."tenant_id" IS '租户字段';
COMMENT ON COLUMN "config_info_gray"."gray_name" IS '灰度名称';
COMMENT ON COLUMN "config_info_gray"."gray_rule" IS '灰度规则';
COMMENT ON COLUMN "config_info_gray"."encrypted_data_key" IS '秘钥';
COMMENT ON TABLE "config_info_gray" IS 'config_info_gray';

-- 创建索引
CREATE UNIQUE INDEX "uk_configinfogray_datagrouptenantgray" ON "config_info_gray" USING btree ("data_id", "group_id", "tenant_id", "gray_name");
CREATE INDEX "idx_dataid_gmt_modified_gray" ON "config_info_gray" USING btree ("data_id", "gmt_modified");
CREATE INDEX "idx_gmt_modified_gray" ON "config_info_gray" USING btree ("gmt_modified");

ALTER TABLE "config_info_gray" ADD CONSTRAINT "config_info_gray_pkey" PRIMARY KEY ("id");

-- ----------------------------
-- Records of config_info_gray
-- ----------------------------
BEGIN;
COMMIT;


-- ----------------------------
-- Table structure for config_tags_relation
-- ----------------------------
DROP TABLE IF EXISTS "config_tags_relation";
CREATE TABLE "config_tags_relation" (
  "id" bigint NOT NULL,
  "tag_name" varchar(128)  NOT NULL,
  "tag_type" varchar(64) ,
  "data_id" varchar(255)  NOT NULL,
  "group_id" varchar(128)  NOT NULL,
  "tenant_id" varchar(128) NOT NULL DEFAULT '',
  "nid" bigserial NOT NULL
)
;
COMMENT ON COLUMN "config_tags_relation"."id" IS 'id';
COMMENT ON COLUMN "config_tags_relation"."tag_name" IS 'tag_name';
COMMENT ON COLUMN "config_tags_relation"."tag_type" IS 'tag_type';
COMMENT ON COLUMN "config_tags_relation"."data_id" IS 'data_id';
COMMENT ON COLUMN "config_tags_relation"."group_id" IS 'group_id';
COMMENT ON COLUMN "config_tags_relation"."tenant_id" IS 'tenant_id';
COMMENT ON TABLE "config_tags_relation" IS 'config_tag_relation';

-- ----------------------------
-- Records of config_tags_relation
-- ----------------------------
BEGIN;
COMMIT;

-- ----------------------------
-- Table structure for group_capacity
-- ----------------------------
DROP TABLE IF EXISTS "group_capacity";
CREATE TABLE "group_capacity" (
  "id" bigserial NOT NULL,
  "group_id" varchar(128)  NOT NULL,
  "quota" int4 NOT NULL,
  "usage" int4 NOT NULL,
  "max_size" int4 NOT NULL,
  "max_aggr_count" int4 NOT NULL,
  "max_aggr_size" int4 NOT NULL,
  "max_history_count" int4 NOT NULL DEFAULT 0,
  "gmt_create" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "gmt_modified" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP
)
;
COMMENT ON COLUMN "group_capacity"."id" IS '主键ID';
COMMENT ON COLUMN "group_capacity"."group_id" IS 'Group ID，空字符表示整个集群';
COMMENT ON COLUMN "group_capacity"."quota" IS '配额，0表示使用默认值';
COMMENT ON COLUMN "group_capacity"."usage" IS '使用量';
COMMENT ON COLUMN "group_capacity"."max_size" IS '单个配置大小上限，单位为字节，0表示使用默认值';
COMMENT ON COLUMN "group_capacity"."max_aggr_count" IS '聚合子配置最大个数，，0表示使用默认值';
COMMENT ON COLUMN "group_capacity"."max_aggr_size" IS '单个聚合数据的子配置大小上限，单位为字节，0表示使用默认值';
COMMENT ON COLUMN "group_capacity"."max_history_count" IS '最大变更历史数量';
COMMENT ON COLUMN "group_capacity"."gmt_create" IS '创建时间';
COMMENT ON COLUMN "group_capacity"."gmt_modified" IS '修改时间';
COMMENT ON TABLE "group_capacity" IS '集群、各Group容量信息表';

-- ----------------------------
-- Records of group_capacity
-- ----------------------------
BEGIN;
COMMIT;

-- ----------------------------
-- Table structure for his_config_info
-- ----------------------------
DROP TABLE IF EXISTS "his_config_info";
CREATE TABLE "his_config_info" (
  "id" int8 NOT NULL,
  "nid" bigserial NOT NULL,
  "data_id" varchar(255)  NOT NULL,
  "group_id" varchar(128)  NOT NULL,
  "app_name" varchar(128) ,
  "content" text  NOT NULL,
  "md5" varchar(32) ,
  "gmt_create" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "gmt_modified" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "src_user" text ,
  "src_ip" varchar(20) ,
  "op_type" char(10) ,
  "tenant_id" varchar(128) NOT NULL DEFAULT '',
  "encrypted_data_key" text  NOT NULL,
  "publish_type" varchar(50) DEFAULT 'formal',
  "gray_name" varchar(50),
  "ext_info" text
)
;
COMMENT ON COLUMN "his_config_info"."app_name" IS 'app_name';
COMMENT ON COLUMN "his_config_info"."tenant_id" IS '租户字段';
COMMENT ON COLUMN "his_config_info"."encrypted_data_key" IS '秘钥';
COMMENT ON COLUMN "his_config_info"."publish_type" IS 'publish type gray or formal';
COMMENT ON COLUMN "his_config_info"."gray_name" IS 'gray name';
COMMENT ON COLUMN "his_config_info"."ext_info" IS 'ext info';
COMMENT ON TABLE "his_config_info" IS '多租户改造';


-- ----------------------------
-- Table structure for permissions
-- ----------------------------
DROP TABLE IF EXISTS "permissions";
CREATE TABLE "permissions" (
  "role" varchar(50)  NOT NULL,
  "resource" varchar(512)  NOT NULL,
  "action" varchar(8)  NOT NULL
)
;

-- ----------------------------
-- Records of permissions
-- ----------------------------
BEGIN;
COMMIT;

-- ----------------------------
-- Table structure for roles
-- ----------------------------
DROP TABLE IF EXISTS "roles";
CREATE TABLE "roles" (
  "username" varchar(50)  NOT NULL,
  "role" varchar(50)  NOT NULL
)
;

-- ----------------------------
-- Records of roles
-- ----------------------------
-- No seed rows: MySQL schema also leaves `roles` empty so the console can run first-time admin setup.
-- A row like ('nacos', 'ROLE_ADMIN') blocks that flow when the DB account name is `nacos` (common JDBC user).
BEGIN;
COMMIT;

-- ----------------------------
-- Table structure for tenant_capacity
-- ----------------------------
DROP TABLE IF EXISTS "tenant_capacity";
CREATE TABLE "tenant_capacity" (
  "id" bigserial NOT NULL,
  "tenant_id" varchar(128)  NOT NULL,
  "quota" int4 NOT NULL,
  "usage" int4 NOT NULL,
  "max_size" int4 NOT NULL,
  "max_aggr_count" int4 NOT NULL,
  "max_aggr_size" int4 NOT NULL,
  "max_history_count" int4 NOT NULL DEFAULT 0,
  "gmt_create" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "gmt_modified" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP
)
;
COMMENT ON COLUMN "tenant_capacity"."id" IS '主键ID';
COMMENT ON COLUMN "tenant_capacity"."tenant_id" IS 'Tenant ID';
COMMENT ON COLUMN "tenant_capacity"."quota" IS '配额，0表示使用默认值';
COMMENT ON COLUMN "tenant_capacity"."usage" IS '使用量';
COMMENT ON COLUMN "tenant_capacity"."max_size" IS '单个配置大小上限，单位为字节，0表示使用默认值';
COMMENT ON COLUMN "tenant_capacity"."max_aggr_count" IS '聚合子配置最大个数';
COMMENT ON COLUMN "tenant_capacity"."max_aggr_size" IS '单个聚合数据的子配置大小上限，单位为字节，0表示使用默认值';
COMMENT ON COLUMN "tenant_capacity"."max_history_count" IS '最大变更历史数量';
COMMENT ON COLUMN "tenant_capacity"."gmt_create" IS '创建时间';
COMMENT ON COLUMN "tenant_capacity"."gmt_modified" IS '修改时间';
COMMENT ON TABLE "tenant_capacity" IS '租户容量信息表';

-- ----------------------------
-- Records of tenant_capacity
-- ----------------------------
BEGIN;
COMMIT;

-- ----------------------------
-- Table structure for tenant_info
-- ----------------------------
DROP TABLE IF EXISTS "tenant_info";
CREATE TABLE "tenant_info" (
  "id" bigserial NOT NULL,
  "kp" varchar(128)  NOT NULL,
  "tenant_id" varchar(128) ,
  "tenant_name" varchar(128) ,
  "tenant_desc" varchar(256) ,
  "create_source" varchar(32) ,
  "gmt_create" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "gmt_modified" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP
)
;
COMMENT ON COLUMN "tenant_info"."id" IS 'id';
COMMENT ON COLUMN "tenant_info"."kp" IS 'kp';
COMMENT ON COLUMN "tenant_info"."tenant_id" IS 'tenant_id';
COMMENT ON COLUMN "tenant_info"."tenant_name" IS 'tenant_name';
COMMENT ON COLUMN "tenant_info"."tenant_desc" IS 'tenant_desc';
COMMENT ON COLUMN "tenant_info"."create_source" IS 'create_source';
COMMENT ON COLUMN "tenant_info"."gmt_create" IS '创建时间';
COMMENT ON COLUMN "tenant_info"."gmt_modified" IS '修改时间';
COMMENT ON TABLE "tenant_info" IS 'tenant_info';

-- ----------------------------
-- Records of tenant_info
-- ----------------------------
BEGIN;
COMMIT;

-- ----------------------------
-- Table structure for users
-- ----------------------------
DROP TABLE IF EXISTS "users";
CREATE TABLE "users" (
  "username" varchar(50)  NOT NULL,
  "password" varchar(500)  NOT NULL,
  "enabled" boolean NOT NULL
)
;

-- ----------------------------
-- Records of users
-- ----------------------------
BEGIN;
COMMIT;

-- ----------------------------
-- Indexes structure for table config_info
-- ----------------------------
CREATE UNIQUE INDEX "uk_configinfo_datagrouptenant" ON "config_info" ("data_id","group_id","tenant_id");

-- ----------------------------
-- Primary Key structure for table config_info
-- ----------------------------
ALTER TABLE "config_info" ADD CONSTRAINT "config_info_pkey" PRIMARY KEY ("id");

-- ----------------------------
-- Indexes structure for table config_tags_relation
-- ----------------------------
CREATE INDEX "idx_tenant_id" ON "config_tags_relation" USING btree (
  "tenant_id"
);
CREATE UNIQUE INDEX "uk_configtagrelation_configidtag" ON "config_tags_relation" USING btree (
  "id",
  "tag_name",
  "tag_type"
);

-- ----------------------------
-- Primary Key structure for table config_tags_relation
-- ----------------------------
ALTER TABLE "config_tags_relation" ADD CONSTRAINT "config_tags_relation_pkey" PRIMARY KEY ("nid");

-- ----------------------------
-- Indexes structure for table group_capacity
-- ----------------------------
CREATE UNIQUE INDEX "uk_group_id" ON "group_capacity" USING btree (
  "group_id"
);

-- ----------------------------
-- Primary Key structure for table group_capacity
-- ----------------------------
ALTER TABLE "group_capacity" ADD CONSTRAINT "group_capacity_pkey" PRIMARY KEY ("id");

-- ----------------------------
-- Indexes structure for table his_config_info
-- ----------------------------
CREATE INDEX "idx_did" ON "his_config_info" USING btree (
  "data_id"
);
CREATE INDEX "idx_gmt_create" ON "his_config_info" USING btree (
  "gmt_create"
);
CREATE INDEX "idx_gmt_modified" ON "his_config_info" USING btree (
  "gmt_modified"
);

-- ----------------------------
-- Primary Key structure for table his_config_info
-- ----------------------------
ALTER TABLE "his_config_info" ADD CONSTRAINT "his_config_info_pkey" PRIMARY KEY ("nid");

-- ----------------------------
-- Indexes structure for table permissions
-- ----------------------------
CREATE UNIQUE INDEX "uk_role_permission" ON "permissions" USING btree (
  "role",
  "resource",
  "action"
);

-- ----------------------------
-- Indexes structure for table roles
-- ----------------------------
CREATE UNIQUE INDEX "uk_username_role" ON "roles" USING btree (
  "username",
  "role"
);

-- ----------------------------
-- Indexes structure for table tenant_capacity
-- ----------------------------
CREATE UNIQUE INDEX "uk_tenant_id" ON "tenant_capacity" USING btree (
  "tenant_id"
);

-- ----------------------------
-- Primary Key structure for table tenant_capacity
-- ----------------------------
ALTER TABLE "tenant_capacity" ADD CONSTRAINT "tenant_capacity_pkey" PRIMARY KEY ("id");

-- ----------------------------
-- Indexes structure for table tenant_info
-- ----------------------------
CREATE UNIQUE INDEX "uk_tenant_info_kptenantid" ON "tenant_info" USING btree (
  "kp",
  "tenant_id"
);

-- ----------------------------
-- Table structure for pipeline_execution
-- ----------------------------
DROP TABLE IF EXISTS "pipeline_execution";
CREATE TABLE "pipeline_execution" (
  "execution_id"  varchar(64)  NOT NULL,
  "resource_type" varchar(32)  NOT NULL,
  "resource_name" varchar(256) NOT NULL,
  "namespace_id"  varchar(128) DEFAULT NULL,
  "version"       varchar(64)  DEFAULT NULL,
  "status"        varchar(32)  NOT NULL,
  "pipeline"      text         NOT NULL,
  "create_time"   bigint       NOT NULL,
  "update_time"   bigint       NOT NULL
);
COMMENT ON COLUMN "pipeline_execution"."execution_id" IS '执行ID';
COMMENT ON COLUMN "pipeline_execution"."resource_type" IS '资源类型';
COMMENT ON COLUMN "pipeline_execution"."resource_name" IS '资源名称';
COMMENT ON COLUMN "pipeline_execution"."namespace_id" IS '命名空间ID';
COMMENT ON COLUMN "pipeline_execution"."version" IS '版本';
COMMENT ON COLUMN "pipeline_execution"."status" IS '执行状态';
COMMENT ON COLUMN "pipeline_execution"."pipeline" IS 'pipeline节点结果JSON';
COMMENT ON COLUMN "pipeline_execution"."create_time" IS '创建时间';
COMMENT ON COLUMN "pipeline_execution"."update_time" IS '修改时间';
COMMENT ON TABLE "pipeline_execution" IS 'AI资源发布审核Pipeline执行记录';

-- ----------------------------
-- Primary Key structure for table pipeline_execution
-- ----------------------------
ALTER TABLE "pipeline_execution" ADD CONSTRAINT "pipeline_execution_pkey" PRIMARY KEY ("execution_id");

-- ----------------------------
-- Table structure for ai_resource
-- ----------------------------
DROP TABLE IF EXISTS "ai_resource";
CREATE TABLE "ai_resource" (
  "id" bigserial NOT NULL,
  "gmt_create" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "gmt_modified" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "name" varchar(256) NOT NULL,
  "type" varchar(32) NOT NULL,
  "c_desc" varchar(1024),
  "status" varchar(32),
  "namespace_id" varchar(128) NOT NULL DEFAULT '',
  "biz_tags" varchar(1024),
  "ext" text,
  "c_from" varchar(256) NOT NULL DEFAULT 'local',
  "version_info" text,
  "meta_version" bigint NOT NULL DEFAULT 1,
  "scope" varchar(16) NOT NULL DEFAULT 'PRIVATE',
  "owner" varchar(128) NOT NULL DEFAULT '',
  "download_count" bigint NOT NULL DEFAULT 0
)
;

COMMENT ON COLUMN "ai_resource"."id" IS 'id';
COMMENT ON COLUMN "ai_resource"."gmt_create" IS '创建时间';
COMMENT ON COLUMN "ai_resource"."gmt_modified" IS '修改时间';
COMMENT ON COLUMN "ai_resource"."name" IS '资源名称';
COMMENT ON COLUMN "ai_resource"."type" IS '资源类型';
COMMENT ON COLUMN "ai_resource"."c_desc" IS '资源描述';
COMMENT ON COLUMN "ai_resource"."status" IS '资源状态';
COMMENT ON COLUMN "ai_resource"."namespace_id" IS '命名空间ID';
COMMENT ON COLUMN "ai_resource"."biz_tags" IS '业务标签';
COMMENT ON COLUMN "ai_resource"."ext" IS '扩展信息(JSON)';
COMMENT ON COLUMN "ai_resource"."c_from" IS '来源标识(导入/同步来源)';
COMMENT ON COLUMN "ai_resource"."version_info" IS '版本信息(JSON)';
COMMENT ON COLUMN "ai_resource"."meta_version" IS '元数据版本(乐观锁)';
COMMENT ON COLUMN "ai_resource"."scope" IS '可见性: PUBLIC/PRIVATE';
COMMENT ON COLUMN "ai_resource"."owner" IS '创建者用户名';
COMMENT ON COLUMN "ai_resource"."download_count" IS '下载次数';
COMMENT ON TABLE "ai_resource" IS 'AI资源元数据表';

-- ----------------------------
-- Primary Key structure for table ai_resource
-- ----------------------------
ALTER TABLE "ai_resource" ADD CONSTRAINT "ai_resource_pkey" PRIMARY KEY ("id");

-- ----------------------------
-- Indexes structure for table ai_resource
-- ----------------------------
CREATE UNIQUE INDEX "uk_ai_resource_ns_name_type" ON "ai_resource" USING btree (
  "namespace_id",
  "name",
  "type",
  "c_from"
);
CREATE INDEX "idx_ai_resource_name" ON "ai_resource" USING btree ("name");
CREATE INDEX "idx_ai_resource_type" ON "ai_resource" USING btree ("type");
CREATE INDEX "idx_ai_resource_gmt_modified" ON "ai_resource" USING btree ("gmt_modified");

-- ----------------------------
-- Table structure for ai_resource_version
-- ----------------------------
DROP TABLE IF EXISTS "ai_resource_version";
CREATE TABLE "ai_resource_version" (
  "id" bigserial NOT NULL,
  "gmt_create" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "gmt_modified" timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
  "type" varchar(32) NOT NULL,
  "author" varchar(128),
  "name" varchar(256) NOT NULL,
  "c_desc" varchar(1024),
  "status" varchar(32) NOT NULL,
  "version" varchar(64) NOT NULL,
  "namespace_id" varchar(128) NOT NULL DEFAULT '',
  "storage" text,
  "publish_pipeline_info" text,
  "download_count" bigint NOT NULL DEFAULT 0
)
;

COMMENT ON COLUMN "ai_resource_version"."id" IS 'id';
COMMENT ON COLUMN "ai_resource_version"."gmt_create" IS '创建时间';
COMMENT ON COLUMN "ai_resource_version"."gmt_modified" IS '修改时间';
COMMENT ON COLUMN "ai_resource_version"."type" IS '资源类型';
COMMENT ON COLUMN "ai_resource_version"."author" IS '作者';
COMMENT ON COLUMN "ai_resource_version"."name" IS '资源名称';
COMMENT ON COLUMN "ai_resource_version"."c_desc" IS '版本描述';
COMMENT ON COLUMN "ai_resource_version"."status" IS '版本状态';
COMMENT ON COLUMN "ai_resource_version"."version" IS '版本号';
COMMENT ON COLUMN "ai_resource_version"."namespace_id" IS '命名空间ID';
COMMENT ON COLUMN "ai_resource_version"."storage" IS '存储信息(JSON)';
COMMENT ON COLUMN "ai_resource_version"."publish_pipeline_info" IS '发布流水线信息(JSON)';
COMMENT ON COLUMN "ai_resource_version"."download_count" IS '下载次数';
COMMENT ON TABLE "ai_resource_version" IS 'AI资源版本表';

-- ----------------------------
-- Primary Key structure for table ai_resource_version
-- ----------------------------
ALTER TABLE "ai_resource_version" ADD CONSTRAINT "ai_resource_version_pkey" PRIMARY KEY ("id");

-- ----------------------------
-- Indexes structure for table ai_resource_version
-- ----------------------------
CREATE UNIQUE INDEX "uk_ai_resource_ver_ns_name_type_ver" ON "ai_resource_version" USING btree (
  "namespace_id",
  "name",
  "type",
  "version"
);
CREATE INDEX "idx_ai_resource_ver_name" ON "ai_resource_version" USING btree ("name");
CREATE INDEX "idx_ai_resource_ver_status" ON "ai_resource_version" USING btree ("status");
CREATE INDEX "idx_ai_resource_ver_gmt_modified" ON "ai_resource_version" USING btree ("gmt_modified");

pg-upgrade-null-tenant-id.sql

/*
 * Copyright 1999-2026 Alibaba Group Holding Ltd.
 *
 * 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.
 */

-- PostgreSQL upgrade script for deployments that still contain nullable tenant_id
-- values in config-related tables.
--
-- IMPORTANT:
-- 1. Review and clean duplicate logical rows before replacing NULL tenant_id
--    values with '' on config_info, otherwise the UPDATE may conflict with the
--    existing unique index on (data_id, group_id, tenant_id).
-- 2. Apply this script before upgrading to a Nacos build that validates the
--    PostgreSQL tenant schema on startup.
--
-- Suggested pre-check for duplicate logical config rows:
-- SELECT data_id, group_id, COUNT(*)
-- FROM config_info
-- WHERE tenant_id IS NULL
-- GROUP BY data_id, group_id
-- HAVING COUNT(*) > 1;

ALTER TABLE config_info ALTER COLUMN tenant_id SET DEFAULT '';
UPDATE config_info SET tenant_id = '' WHERE tenant_id IS NULL;
ALTER TABLE config_info ALTER COLUMN tenant_id SET NOT NULL;

ALTER TABLE config_info_gray ALTER COLUMN tenant_id SET DEFAULT '';
UPDATE config_info_gray SET tenant_id = '' WHERE tenant_id IS NULL;
ALTER TABLE config_info_gray ALTER COLUMN tenant_id SET NOT NULL;

ALTER TABLE config_tags_relation ALTER COLUMN tenant_id SET DEFAULT '';
UPDATE config_tags_relation SET tenant_id = '' WHERE tenant_id IS NULL;
ALTER TABLE config_tags_relation ALTER COLUMN tenant_id SET NOT NULL;

ALTER TABLE his_config_info ALTER COLUMN tenant_id SET DEFAULT '';
UPDATE his_config_info SET tenant_id = '' WHERE tenant_id IS NULL;
ALTER TABLE his_config_info ALTER COLUMN tenant_id SET NOT NULL;

pg-grant-nacos-readwrite.sql

/*
 * Copyright 1999-2018 Alibaba Group Holding Ltd.
 *
 * 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.
 */

/*
 * Optional: grant read/write on existing Nacos tables to application role `nacos` only.
 *
 * When to use:
 *   Load pg-schema.sql as a DBA/superuser (tables then belong to that role). Create the app user:
 *     CREATE USER nacos WITH PASSWORD 'your-password';
 *   Then run this script while connected to the Nacos database as the same role that owns the tables
 *   (often superuser), so privileges apply to all current objects.
 *
 * What you get:
 *   USAGE on public schema, SELECT/INSERT/UPDATE/DELETE on all tables, USAGE+SELECT on sequences
 *   (covers bigserial / identity). No CREATE/DROP on schema, no superuser.
 *
 * CONNECT: use `psql -d your_nacos_db` so the session can open the DB, or from another database run:
 *   GRANT CONNECT ON DATABASE your_nacos_db TO nacos;
 */

GRANT USAGE ON SCHEMA public TO nacos;
GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO nacos;
GRANT USAGE, SELECT ON ALL SEQUENCES IN SCHEMA public TO nacos;

-- Objects created later by the same owner (e.g. future migrations run as superuser):
ALTER DEFAULT PRIVILEGES IN SCHEMA public
  GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES TO nacos;
ALTER DEFAULT PRIVILEGES IN SCHEMA public
  GRANT USAGE, SELECT ON SEQUENCES TO nacos;

Docker 部署项目说明及索引

Thu, 06 Aug 2026 00:00:00 +0000

如果你是新手，建议先阅读 Docker Compose 入门理解 Docker 基本概念和指令。

Run on Docker 说明

该系列文章为作者使用 Docker 运行项目所记录的步骤。此外有一些额外的前置条件说明。

配置说明

运行项目一般使用 docker-compose.yml 文件来部署，volumes 映射的本地目录统一在 docker 目录下新建文件夹，应在运行容器前创建。
大部分项目提供了 Nginx Proxy Manager 来进行反向代理，如不需要则可跳过相关内容。
镜像一般使用 latest 版本，如需指定版本，请自行修改。
端口（port）映射默认原端口，请自行修改可用端口。

网络设置

在大部分项目的 docker-compose.yml 文件中，你会看到类似如下配置：

networks:
  default:
    external: true
    name: rod

这因为作者所有运行的 Docker 容器均在同一名为 rod 的网络下。使用如下指令创建：

`1`	`docker network create rod`

但也有一些特殊的容器，使用了 HOST 模式，如 DDNS-GO、Nginx Proxy Manager 等。

文章索引

使用 Docker 部署 qBittorrent

Tue, 30 Jul 2024 00:00:00 +0000

如果您是第一次阅读该系列文章，建议优先阅读 Docker 部署项目说明及索引

Docker Compose

version: "3.9"

services:
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    hostname: qbittorrent
    restart: unless-stopped
    ports:
      - "8080:8080"
    volumes:
      - /docker/qbittorrent/config:/config
      - /docker/qbittorrent/downloads:/downloads
    environment:
      - WEBUI_PORT=8080
      - TORRENTING_PORT=6881
      - TZ=Asia/Shanghai
networks:
  default:
    external: true
    name: rod

使用 qBittorrent

打开 WebUI 管理界面 (http://localhost:8080 )：

默认账号: admin
默认密码: 使用 docker logs -f qbittorrent 查看临时密码。

使用 Docker 部署 Nginx Proxy Manager

Fri, 19 Jan 2024 00:00:00 +0000

如果您是第一次阅读该系列文章，建议优先阅读 Docker 部署项目说明及索引

Docker Compose

以下是 Docker Compose 示例：

version: "3.9"

services:
  npm:
    image: 'jc21/nginx-proxy-manager:2.11.3'
    container_name: npm
    hostname: npm
    restart: unless-stopped
    network_mode: host
    volumes:
      - /docker/nginx-proxy-manager/data:/data
      - /docker/nginx-proxy-manager/letsencrypt:/etc/letsencrypt

注意事项：

上述配置网络使用的 HOST 模式，如果端口 (80、81、443) 被占用，请修改为端口映射。

前往 http://localhost:81 ，使用如下默认账号/密码登录：

Default Username	admin@example.com
Default Password	changeme

登录后请先修改个人信息。

FAQs

SSL Certificates

SSL Certificates 配置证书 (Let’s Encrypt) 时，提示缺少 zope。当使用 DNSPod 时一般会提示此错误。

解决方式：(安装 zope)

进入容器

`1`	`docker exec -it npm bash`

执行如下代码安装 zope 模块

`1`	`pip install zope -i https://pypi.tuna.tsinghua.edu.cn/simple`

Nginx Proxy Manager 配置说明

主要介绍 Nginx Proxy Manager 界面操作对应 Nginx 中的配置。

Nginx 路径

Nginx 存放在容器路径： /etc/nginx

Add Proxy Host

设置反向代理时，可以勾选一些常用配置，勾选后会在相应的配置文件中添加对应配置内容。

配置文件路径：/data/nginx/proxy_host，可通过界面查看对应的配置。

如下图: #22 对应 22.conf,则勾选对应配置时，修改 22.conf 的内容。

Details

配置	含义
Cache Assets	缓存
Block Common Exploits	阻止常见漏洞
Websockets Support	支持 WS

Cache Assets

设置缓存，启用该项后，会添加如下内容：

1
2

# Asset Caching
include conf.d/include/assets.conf;

assets.conf 完整内容如下：

容器内绝对路径：/etc/nginx/conf.d/include/assets.conf

location ~* ^.*\.(css|js|jpe?g|gif|png|webp|woff|eot|ttf|svg|ico|css\.map|js\.map)$ {
        if_modified_since off;

        # use the public cache
        proxy_cache public-cache;
        proxy_cache_key $host$request_uri;

        # ignore these headers for media
        proxy_ignore_headers Set-Cookie Cache-Control Expires X-Accel-Expires;

        # cache 200s and also 404s (not ideal but there are a few 404 images for some reason)
        proxy_cache_valid any 30m;
        proxy_cache_valid 404 1m;

        # strip this header to avoid If-Modified-Since requests
        proxy_hide_header Last-Modified;
        proxy_hide_header Cache-Control;
        proxy_hide_header Vary;

        proxy_cache_bypass 0;
        proxy_no_cache 0;

        proxy_cache_use_stale error timeout updating http_500 http_502 http_503 http_504 http_404;
        proxy_connect_timeout 5s;
        proxy_read_timeout 45s;

        expires @30m;
        access_log  off;

        include conf.d/include/proxy.conf;
}

proxy.conf 完整内容如下：

容器内绝对路径：/etc/nginx/conf.d/include/proxy.conf

add_header       X-Served-By $host;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Scheme $scheme;
proxy_set_header X-Forwarded-Proto  $scheme;
proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP          $remote_addr;
proxy_pass       $forward_scheme://$server:$port$request_uri;

Block Common Exploits

阻止常见的漏洞，启用该配置后，会添加如下内容：

1
2

# Block Exploits
include conf.d/include/block-exploits.conf;

block-exploits.conf 完整内容如下：

容器内绝对路径：/etc/nginx/conf.d/include/block-exploits.conf

## Block SQL injections
set $block_sql_injections 0;

if ($query_string ~ "union.*select.*\(") {
        set $block_sql_injections 1;
}

if ($query_string ~ "union.*all.*select.*") {
        set $block_sql_injections 1;
}

if ($query_string ~ "concat.*\(") {
        set $block_sql_injections 1;
}

if ($block_sql_injections = 1) {
        return 403;
}

## Block file injections
set $block_file_injections 0;

if ($query_string ~ "[a-zA-Z0-9_]=http://") {
        set $block_file_injections 1;
}

if ($query_string ~ "[a-zA-Z0-9_]=(\.\.//?)+") {
        set $block_file_injections 1;
}

if ($query_string ~ "[a-zA-Z0-9_]=/([a-z0-9_.]//?)+") {
        set $block_file_injections 1;
}

if ($block_file_injections = 1) {
        return 403;
}

## Block common exploits
set $block_common_exploits 0;

if ($query_string ~ "(<|%3C).*script.*(>|%3E)") {
        set $block_common_exploits 1;
}

if ($query_string ~ "GLOBALS(=|\[|\%[0-9A-Z]{0,2})") {
        set $block_common_exploits 1;
}

if ($query_string ~ "_REQUEST(=|\[|\%[0-9A-Z]{0,2})") {
        set $block_common_exploits 1;
}

if ($query_string ~ "proc/self/environ") {
        set $block_common_exploits 1;
}

if ($query_string ~ "mosConfig_[a-zA-Z_]{1,21}(=|\%3D)") {
        set $block_common_exploits 1;
}

if ($query_string ~ "base64_(en|de)code\(.*\)") {
        set $block_common_exploits 1;
}

if ($block_common_exploits = 1) {
        return 403;
}

## Block spam
set $block_spam 0;

if ($query_string ~ "\b(ultram|unicauca|valium|viagra|vicodin|xanax|ypxaieo)\b") {
        set $block_spam 1;
}

if ($query_string ~ "\b(erections|hoodia|huronriveracres|impotence|levitra|libido)\b") {
        set $block_spam 1;
}

if ($query_string ~ "\b(ambien|blue\spill|cialis|cocaine|ejaculation|erectile)\b") {
        set $block_spam 1;
}

if ($query_string ~ "\b(lipitor|phentermin|pro[sz]ac|sandyauer|tramadol|troyhamby)\b") {
        set $block_spam 1;
}

if ($block_spam = 1) {
        return 403;
}

## Block user agents
set $block_user_agents 0;

# Disable Akeeba Remote Control 2.5 and earlier
if ($http_user_agent ~ "Indy Library") {
        set $block_user_agents 1;
}

# Common bandwidth hoggers and hacking tools.
if ($http_user_agent ~ "libwww-perl") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "GetRight") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "GetWeb!") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "Go!Zilla") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "Download Demon") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "Go-Ahead-Got-It") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "TurnitinBot") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "GrabNet") {
        set $block_user_agents 1;
}

if ($block_user_agents = 1) {
        return 403;
}

Websockets Support

支持 Websocket，启用该配置后，会添加如下内容：

1
2
3

proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;

SSL

配置	含义
Force SSL	强制 SSL
HTTP/2 Support	支持 HTTP/2
HSTS Enabled	启用 HTTP 严格传输安全
HSTS Subdomains	启用 HTTP 严格传输安全（包含子域）

Force SSL

强制 SSL，启用该配置后，会添加如下内容：

1
2

# Force SSL
include conf.d/include/force-ssl.conf;

force-ssl.conf 完整内容如下：

容器内绝对路径：/etc/nginx/conf.d/include/force-ssl.conf

1
2
3

if ($scheme = "http") {
        return 301 https://$host$request_uri;
}

HSTS Enabled & HSTS Subdomains

HSTS Enabled 启用 HTTP 严格传输安全，启用该配置，会添加如下内容：

1
2

# HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
add_header Strict-Transport-Security "max-age=63072000; preload" always;

如果启用了 HSTS Subdomains，则会额外添加 includeSubDomains;，最终内容如下：

1
2

# HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
add_header Strict-Transport-Security "max-age=63072000;includeSubDomains; preload" always;

以下内容摘自 Wikipedia

HTTP 严格传输安全（HTTP Strict Transport Security，HSTS）是一套由互联网工程任务组发布的互联网安全策略机制。网站可以选择使用 HSTS 策略，来让浏览器强制使用 HTTPS 与网站进行通信，以减少会话劫持风险。

其征求修正意见书文件编号是 RFC 6797 ，发布于2012年11月。

HSTS 的作用是强制客户端（如浏览器）使用 HTTPS 与服务器建立连接。服务器开启 HSTS 的方法是，当客户端通过 HTTPS 发出请求时，在服务器返回的超文本传输协议（HTTP）响应头中包含 Strict-Transport-Security 字段。非加密传输时设置的 HSTS 字段无效。

比如，https://example.com/ 的响应头含有 Strict-Transport-Security: max-age=31536000; includeSubDomains。这意味着两点：

在接下来的 31536000 秒（即一年）中，浏览器向example.com或其子域名发送HTTP请求时，必须采用HTTPS来发起连接。比如，用户点击超链接或在地址栏输入 http://www.example.com/ ，浏览器应当自动将 http 转写成 https，然后直接向 https://www.example.com/ 发送请求。
在接下来的一年中，如果 example.com 服务器发送的 TLS 证书无效，用户不能忽略浏览器警告继续访问网站。

使用 Docker 部署 Gogs

Fri, 21 Jul 2023 00:00:00 +0000

如果您是第一次阅读该系列文章，建议优先阅读 Docker 部署项目说明及索引

前置操作

提前创建好 Gogs 的数据库，Gogs 支持 MySQL、PostgreSQL、SQLite3 或 TiDB（MySQL 协议）数据库。

Docker Compose

version: "3.9"

services:
  gogs:
    image: gogs/gogs:latest
    container_name: gogs
    hostname: gogs
    restart: unless-stopped
    ports:
      - "3000:3000"
    volumes:
      - /docker/gogs:/data
    environment:
      - TZ=Asia/Shanghai
networks:
  default:
    external: true
    name: rod

使用 Gogs

打开链接： http://localhost:3000 按指引安装配置 Gogs 即可。

NPM 反向代理配置

此处以 https://gogs.example.com 为例

如果未部署 NPM，可参考文章：使用 Docker 部署 Nginx Proxy Manager

Details

Domain Names: gogs.example.com
Scheme: http
Forward Hostname/IP: 127.0.0.1 (如果 NPM 未使用 HOST，则使用容器的 hostname: gogs)
Forward Port: 3000
Cache Assets: ✅

SSL

选择你已经配置好的 SSL Certificate，如 *.example.com, example.com
Force SSL: ✅
HTTP/2 Support: ✅

Advanced

location / {
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    proxy_pass $forward_scheme://$server:$port;
}

参考链接

Gogs 官方文档

使用 Docker 部署 nexus3

Tue, 31 Jan 2023 00:00:00 +0000

如果您是第一次阅读该系列文章，建议优先阅读 Docker 部署项目说明及索引

Docker Compose

version: "3.9"

services:
  nexus3:
    image: sonatype/nexus3:latest
    container_name: nexus3
    hostname: nexus3
    restart: unless-stopped
    ports:
      - "8081:8081"
    volumes:
      - /docker/nexus/nexus-data:/nexus-data
    environment:
      - TZ=Asia/Shanghai
networks:
  default:
    external: true
    name: rod

使用 nexus3

打开链接： (http://localhost:8081 )：

NPM 反向代理配置

此处以 https://nexus3.example.com 为例

如果未部署 NPM，可参考文章：使用 Docker 部署 Nginx Proxy Manager

Details

Domain Names: nexus3.example.com
Scheme: http
Forward Hostname/IP: 127.0.0.1 (如果 NPM 未使用 HOST，则使用容器的 hostname: nexus3)
Forward Port: 8081
Cache Assets: ✅

SSL

选择你已经配置好的 SSL Certificate，如 *.example.com, example.com
Force SSL: ✅
HTTP/2 Support: ✅

Advanced

location / {
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    proxy_pass $forward_scheme://$server:$port;
}

使用 Docker 部署 vaultwarden

Mon, 10 Oct 2022 00:00:00 +0000

如果您是第一次阅读该系列文章，建议优先阅读 Docker 部署项目说明及索引

前置条件

部署 vaultwarden 前需要具备数据库条件，本文以 PostgreSQL 为例。

如未部署 Postgres 可参考使用 Docker 部署 PostgreSQL & pgAdmin4

参考上述文章创建自己的 vaultwarden 数据库，并修改下述 docker-compose.yml 文件中的配置。

Docker Compose

version: "3.9"

services:
  vaultwarden:
    image: vaultwarden/server:latest
    container_name: vaultwarden
    hostname: vaultwarden
    restart: unless-stopped
    ports:
      - "80:80"
      - "8080:8080"
      - "3012:3012"
    volumes:
      - /docker/vaultwarden/data:/data
    environment:
      - ROCKET_ADDRESS=0.0.0.0
      - ROCKET_PORT=8080
      - TZ=Asia/Shanghai
#      - ADMIN_TOKEN=your_token    #启用该项可访问 /admin 路径
      - DOMAIN=https://vaultwarden.example.com/
      - SIGNUPS_ALLOWED=true
      - WEB_VAULT_ENABLED=true
      - ENABLE_WEBSOCKET=true
      - DATABASE_URL=postgres://username:password@postgres:5432/vaultwarden?application_name=vaultwarden
networks:
  default:
    external: true
    name: rod

NPM 反向代理配置

此处以 https://vaultwarden.example.com 为例

如果未部署 NPM，可参考文章：使用 Docker 部署 Nginx Proxy Manager

Details

Domain Names: vaultwarden.example.com
Scheme: http
Forward Hostname/IP: 127.0.0.1 (如果 NPM 未使用 HOST，则使用容器的 hostname: vaultwarden)
Forward Port: 8080
Cache Assets: ✅
WebSockets Support: ✅

SSL

选择你已经配置好的 SSL Certificate，如 *.example.com, example.com
Force SSL: ✅
HTTP/2 Support: ✅

Advanced

location / {
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    proxy_pass $forward_scheme://$server:$port;
}

location /notifications/hub {
    proxy_pass http://$server:3012;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
}

location /notifications/hub/negotiate {
    proxy_pass http://$server:80;
}

使用 vaultwarden

打开链接：https://vaultwarden.example.com 注册账号。

注意：

如果仅自己使用，推荐注册账号后将 SIGNUPS_ALLOWED 修改为 false 后重新构建项目启动。
如果设置了 ADMIN_TOKEN，则访问 https://vaultwarden.example.com/admin 可进入管理页面。

使用 Docker 部署使用 Docker 部署 PostgreSQL & pgAdmin4

Mon, 19 Sep 2022 00:00:00 +0000

如果您是第一次阅读该系列文章，建议优先阅读 Docker 部署项目说明及索引

Docker Compose

version: '3.9'

services:
  postgres:
    image: postgres:latest
    container_name: postgres
    hostname: postgres
    restart: unless-stopped
    ports:
      - "5432:5432"
    volumes:
      - /docker/postgres/db/data:/var/lib/postgresql/data
    environment:
      - PGDATA=/var/lib/postgresql/data
      - POSTGRES_PASSWORD=your_password
      - ALLOW_IP_RANGE=0.0.0.0/0
      - TZ=Asia/Shanghai
  pgadmin:
    image: dpage/pgadmin4:latest
    container_name: pgadmin
    hostname: pgadmin
    restart: unless-stopped
    ports:
      - "80:80"
    volumes:
      - /docker/postgres/pgadmin4/data:/var/lib/pgadmin
    environment:
      - TZ=Asia/Shanghai
      - PGADMIN_DEFAULT_PASSWORD=your_password
      - PGADMIN_DEFAULT_EMAIL=your_email@example.com
    depends_on:
      - postgres
networks:
  default:
    external: true
    name: rod

NPM 反向代理配置

此处以 https://pgadmin.example.com 为例

如果未部署 NPM，可参考文章：使用 Docker 部署 Nginx Proxy Manager

Details

Domain Names: pgadmin.example.com
Scheme: http
Forward Hostname/IP: 127.0.0.1 (如果 NPM 未使用 HOST，则使用容器的 hostname: pgadmin)
Forward Port: 80
Cache Assets: ✅
WebSockets Support: ✅

SSL

选择你已经配置好的 SSL Certificate，如 *.example.com, example.com
Force SSL: ✅
HTTP/2 Support: ✅

Advanced

location / {
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    proxy_pass $forward_scheme://$server:$port;
}

创建用户 & 数据库

# 1. 连接 postgres 数据库
psql -U postgres

# 2. 创建 myuser 用户，密码 my_password
create user myuser with password 'my_password';

# 3. 创建 mydb 数据库
create database mydb owner myuser;

# 4. 授权
grant all privileges on database mydb to myuser;

# 5. 退出
\q

使用 pgAdmin4

打开链接：https://pgadmin.example.com 登录账号。

Run on Docker on Tofuwine's Blog

使用 Docker 部署 Nacos

Docker Compose

配置说明

外置数据源说明

端口说明

验证 Nacos 服务是否启动成功

Nacos 控制台页面

服务注册

服务发现

发布配置

获取配置

NPM 反向代理

Details

SSL

Advanced

参考网址

附录

PostgreSQL DDL

pg-schema.sql

pg-upgrade-null-tenant-id.sql

pg-grant-nacos-readwrite.sql

Docker 部署项目说明及索引

Run on Docker 说明

配置说明

网络设置

文章索引

使用 Docker 部署 qBittorrent

Docker Compose

使用 qBittorrent

使用 Docker 部署 Nginx Proxy Manager

Docker Compose

Login

FAQs

SSL Certificates

Nginx Proxy Manager 配置说明

Nginx 路径

Add Proxy Host

Details

Cache Assets

Block Common Exploits

Websockets Support

SSL

Force SSL

HSTS Enabled & HSTS Subdomains

使用 Docker 部署 Gogs

前置操作

Docker Compose

使用 Gogs

NPM 反向代理配置

Details

SSL

Advanced

参考链接

使用 Docker 部署 nexus3

Docker Compose

使用 nexus3

NPM 反向代理配置

Details

SSL

Advanced

使用 Docker 部署 vaultwarden

前置条件

Docker Compose

NPM 反向代理配置

Details

SSL

Advanced

使用 vaultwarden

使用 Docker 部署 使用 Docker 部署 PostgreSQL & pgAdmin4

Docker Compose

NPM 反向代理配置

Details

SSL

Advanced

创建用户 & 数据库

使用 pgAdmin4

使用 Docker 部署使用 Docker 部署 PostgreSQL & pgAdmin4