Ubuntu 22.04.1默认采用systemd-resolved作为DNS维护服务，其生成的/etc/resolv.conf文件内容如下：

# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 192.168.1.1
search .

如果需要修改DNS服务器，则修改文件/etc/systemd/resolved.conf中的DNS字段，示例:

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it under the
#  terms of the GNU Lesser General Public License as published by the Free
#  Software Foundation; either version 2.1 of the License, or (at your option)
#  any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the resolved.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config.
#
# See resolved.conf(5) for details.

[Resolve]
# Some examples of DNS servers which may be used for DNS= and FallbackDNS=:
# Cloudflare: 1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::1001#cloudflare-dns.com
# Google:     8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google
# Quad9:      9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
DNS=223.6.6.6 119.29.29.29
#FallbackDNS=
#Domains=
#DNSSEC=no
#DNSOverTLS=no
#MulticastDNS=no
#LLMNR=no
#Cache=no-negative
#CacheFromLocalhost=no
#DNSStubListener=yes
#DNSStubListenerExtra=
#ReadEtcHosts=yes
#ResolveUnicastSingleLabel=no

再重启服务生效：

sudo systemctl restart systemd-resolved

frps作为服务端，需要在Windows服务器上实现服务后台运行，借助winsw工具快速搞定，记录如下：

• 下载winsw
  https://github.com/winsw/winsw/releases
  下载对应的版本，如WinSW-x64.exe

• 填写服务配置文件
  配置文件名：WinSW-x64.xml，注意取名跟所下载的应用程序名WinSW-x64.exe相同，并放入同一目录下。

  <service>
  <!--  该服务的唯一标识  -->
  <id>frps</id>
  <!--  该服务的名称  -->
  <name>frp-server</name>
  <!--  该服务的描述  -->
  <description>frp服务器</description>
  <!--  要运行的程序路径  -->
  <executable>C:\bug\frp\frps.exe</executable>
  <!--  携带的参数  -->
  <startargument>-c</startargument>
  <startargument>C:\bug\frp\frps.toml</startargument>
  <!--  第一次启动失败 60秒重启  -->
  <onfailure action="restart" delay="60 sec"/>
  <!--  第二次启动失败 120秒后重启  -->
  <onfailure action="restart" delay="120 sec"/>
  <!--  日志模式  -->
  <logmode>append</logmode>
  <!--  指定日志文件目录(相对于executable配置的路径)  -->
  <logpath>logs</logpath>
  </service>

• 安装并启动服务

  以管理员权限运行cmd:

    WinSW-x64.exe install
    WinSW-x64.exe start

• 查看log
  找到配置文件所在的logs目录查看即可。

Nginx 只允许Cloudflare CDN IP访问

server {
    listen 80;
    server_name your_domain.com;

    # 允许 Cloudflare 的 IP 地址访问
    # 定义允许的 IPv4 地址范围
    allow 173.245.48.0/20;
    allow 103.21.244.0/22;
    allow 103.22.200.0/22;
    allow 103.31.4.0/22;
    allow 141.101.64.0/18;
    allow 108.162.192.0/18;
    allow 190.93.240.0/20;
    allow 188.114.96.0/20;
    allow 197.234.240.0/22;
    allow 198.41.128.0/17;
    allow 162.158.0.0/15;
    allow 104.16.0.0/13;
    allow 104.24.0.0/14;
    allow 172.64.0.0/13;
    allow 131.0.72.0/22;

    # 定义允许的 IPv6 地址范围
    allow 2400:cb00::/32;
    allow 2606:4700::/32;
    allow 2803:f800::/32;
    allow 2405:b500::/32;
    allow 2405:8100::/32;
    allow 2a06:98c0::/29;
    allow 2c0f:f248::/32;

    # 禁止其他 IP 地址访问
    deny all;

    # 此处添加其他 Nginx 配置，如 location 等
}

现有一个简单的需求，需要用户弹窗选择一个铃音，要求在正式的确认之前就能播放对应的音乐作预听，微信小程序picker（mode = selector）可以实现选择确认功能，但只有点击确认后的bindchange事件，没有选择变化事件。根据微信文档，在mode = multiSelector时，有多了一个bindcolumnchange事件，灵光一闪，只有一列的multiSelector不就是selector？那不就可以把multiSelector当selector用？

wxml:

          <view class="option">铃声: 
          <picker mode="multiSelector" range="{{[ringtones]}}" data-alarmid="{{item.id}}" bindcolumnchange="bindRingtoneSelect" bindchange="bindRingtoneChange">
            <view class="picker">{{ringtones[item.ringtoneIndex]}} <text class="picker-selector"> ❯</text> </view> 
          </picker>
          </view>

特别注意其中：ringtones一维数组，调整为：[ringtones]引用。

js:

  bindRingtoneSelect: function(e) {
    proto.sendPlayMusic(e.detail.value);
  },

  bindRingtoneChange:function(e) {
    proto.sendSaveMusic(e.detail.value);
  },

实验效果完美解决~~