构建php5.3.29+phalcon2的docker环境

1、拉取centos7镜像

# arm64架构CPU
docker pull arm64v8/centos:7.9.2009

# amd64架构cpu
docker pull centos:7.6.1810

2、新建一个基础容器

# arm64架构CPU
docker run --privileged=true -it arm64v8/centos:7.9.2009 /bin/bash

# amd64架构cpu
docker run --privileged=true -it arm64v8/centos:7.9.2009 /bin/bash

3、进行构建php5.3.29和phalcon2基础环境

yum install epel-release

yum groupinstall "Development Tools" -y

yum install gcc gcc-c++ make autoconf libxml2-devel bzip2-devel curl-devel \
libjpeg-devel libpng-devel freetype-devel libmcrypt-devel \
mysql-devel openssl-devel libmcrypt-devel libicu-devel -y

  • 如果是amd64 架构不要安装mysql-devel, 用一下方式安装mysql依赖包
yum remove mariadb-devel
wget https://dev.mysql.com/get/Downloads/MySQL-5.5/MySQL-devel-5.5.62-1.el7.x86_64.rpm
wget https://dev.mysql.com/get/Downloads/MySQL-5.5/MySQL-shared-5.5.62-1.el7.x86_64.rpm
yum install MySQL-devel-5.5.62-1.el7.x86_64.rpm MySQL-shared-5.5.62-1.el7.x86_64.rpm

4、开始编译

# 下载php源码包
wget https://www.php.net/distributions/php-5.3.29.tar.gz
# 解压
tar -zxf php-5.3.29.tar.gz
# 进入目录
cd php-5.3.29
# 执行配置检查
./configure \
    --prefix=/usr/local/php/5.3 \
    --with-config-file-path=/usr/local/php/5.3/etc \
    --with-mysql=mysqlnd \
    --with-mysqli=mysqlnd \
    --with-pdo-mysql=mysqlnd \
    --with-openssl \
    --with-zlib \
    --with-curl \
    --with-jpeg-dir=/usr \
    --with-png-dir=/usr \
    --with-freetype-dir=/usr \
    --enable-mbstring \
    --enable-soap \
    --enable-sockets \
    --enable-sysvsem \
    --enable-sysvshm \
    --enable-shmop \
    --enable-pcntl \
    --enable-mbregex \
    --enable-exif \
    --enable-bcmath \
    --enable-calendar \
    --enable-ftp \
    --with-mcrypt \
    --with-gd \
    --with-xmlrpc \
    --enable-intl \
    --enable-fpm \
    --disable-opcache \
    --with-libdir=lib64 \
    LIBS="-lstdc++ -lpthread"

# 配置通过后开始编译
make -j$(nproc)

# make通过后直接安装
make install

# 将源码包下的php.ini-development 文件复制到/usr/local/php/5.3/etc目录
cp php.ini-development  /usr/local/php/5.3/etc/php.ini

# 将/usr/local/php/5.3/etc目录下的php-fpm.conf.default文件重命名为php-fpm.conf
mv /usr/local/php/5.3/etc/php-fpm.conf.default /usr/local/php/5.3/etc/php-fpm.conf

5、编译phalcon2.0.1扩展

# 下载phalcon源码
https://github.com/phalcon/cphalcon/archive/refs/tags/phalcon-v2.0.1.tar.gz

# 解压源码
tar -zxf phalcon-v2.0.1.tar.gz
cd cphalcon-phalcon-v2.0.1

# 进入到源码build/64bits 目录下执行 phpize命令
phpize

# 执行配置检查configure(arm64架构)
./configure --build=aarch64-unknown-linux-gnu --with-php-config=/usr/local/php/5.3/bin/php-config

# 执行配置检查configure(amd64架构)
./configure --with-php-config=/usr/local/php/5.3/bin/php-config

# 执行编译构建
make -j$(nproc)

# 执行安装
make install

# 在php.ini文件最后添加phalcon配置项
[phalcon]
extension=phalcon.so

6、编译nginx1.8.1

wget https://nginx.org/download/nginx-1.8.1.tar.gz

# 执行配置
./configure \
  --prefix=/usr/local/nginx \
  --with-http_ssl_module \
  --with-http_stub_status_module \
  --with-http_gzip_static_module \
  --with-http_realip_module \
  --with-http_sub_module \
  --with-http_addition_module \
  --with-pcre

# 执行编译构建
make -j$(nproc)

# 执行安装
make install

# 新建conf.d 目录,用于用户映射自定义配置文件
mkdir -p /usr/local/nginx/conf/conf.d

# 配置nginx.conf,在localhost 配置项下添加php解析服务
location ~ \.php$ {
    root           html;
    fastcgi_pass   127.0.0.1:9000;
    fastcgi_index  index.php;
    fastcgi_param  SCRIPT_FILENAME  /$document_root$fastcgi_script_name;
    include        fastcgi_params;
}
# 在文件最后添加引入用户自定义配置文件
include conf.d/*.conf;

7、构建php-fpm+nginx启动脚本

vim /start.sh

#!/bin/bash

/usr/local/php/5.3/sbin/php-fpm &

exec /usr/local/nginx/sbin/nginx -g "daemon off;"
  • 设置环境变量
echo 'export PATH=/usr/local/php/5.3/sbin:$PATH' >> ~/.bashrc
echo 'export PATH=/usr/local/php/5.3/bin:$PATH' >> ~/.bashrc
echo 'export PATH=/usr/local/nginx/sbin:$PATH' >> ~/.bashrc

8、提交当前docker容器为docker 镜像

docker commit [容器ID] 镜像名:版本

docker commit 4d47739c75e5 harbor.dev.10t.link:8443/library/php5.3_http_arm64v8:0.1

9、通过新打包的镜像进行创建容器服务

  • 创建docker-compose.yml 文件
services:
  php5.3_web:
    image: harbor.dev.10t.link:8443/library/php5.3_http_arm64v8:0.1
    container_name: php5.3_web2
    environment:
      - TZ=Asia/Shanghai
    ports:
      - "18380:80"
    privileged: true
    command: ["/bin/bash", "/start.sh"]
    volumes:
      - /User/code/demo/html:/usr/local/nginx/html
      - /User/code/demo/conf:/usr/local/nginx/conf.d
    restart: unless-stopped

10、以下是一个简单的nginx配置代码

server {
    listen       80;
    server_name  demo.test.com;

    #charset koi8-r;

    #access_log  logs/host.access.log  main;

    location / {
        root   html;
        index  index.html index.htm index.php;
    }

    #error_page  404              /404.html;

    error_page   500 502 503 504  /50x.html;
    location = /50x.html {
        root   html;
    }

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #
    location ~ \.php$ {
        root           html;
        fastcgi_pass   127.0.0.1:9000;
        fastcgi_index  index.php;
        fastcgi_param  SCRIPT_FILENAME  /$document_root$fastcgi_script_name;
        include        fastcgi_params;
    }
    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    #location ~ /\.ht {
    #    deny  all;
    #}
}

Git 多分支开发同步流程文档


✅ 1. 分支规范(推荐)

| 分支类型 | 命名规则 | 用途说明 |
|----------|----------|----------|
| 主分支 | master / main | 可部署的稳定版本 |
| 开发分支 | dev / 8001_dev / feature_xxx | 每个功能或模块单独分支开发 |
| 修复分支 | hotfix_xxx | 临时紧急修复,通常从 master 开出 |


✅ 2. 开发分支创建流程

git checkout master
git pull origin master  # 确保主干是最新的
git checkout -b 8001_dev  # 创建开发分支
git push -u origin 8001_dev  # 推送远程并建立跟踪

🔄 3. 日常开发:提交 & 推送

# 编写代码后:
git add .
git commit -m "feat: 完善用户登录逻辑"
git push origin 8001_dev

🔁 4. 同步主分支更新(推荐定期进行)

# 方式一:合并方式
# 有 merge commit,适合多人合并

git checkout 8001_dev
git pull origin master
# 方式二:变基方式
# 历史更细准,适合个人分支

git checkout 8001_dev
git pull --rebase origin master

✅ 建议使用 --rebase 保持提交历史线性,特别是功能开发阶段


🚀 5. 开发完成后合并到主干

git checkout master
git pull origin master  # 保证是最新
git merge 8001_dev
git push origin master

🧼 6. 合并后清理(可选)

git branch -d 8001_dev             # 删除本地分支
git push origin --delete 8001_dev  # 删除远程分支(如已完成)

📈 7. 实际例子(分支命名示例)

| 功能 | 分支名示例 |
|--------|----------------|
| 用户登录 | feature/login |
| 账号管理 | feature/account |
| 临时修复 | hotfix/login-crash |
| 经理查看页 | feature/manager-ui |


📚 8. 实用命令速查

| 命令 | 说明 |
|------|------|
| git branch | 查看本地分支 |
| git branch -r | 查看远程分支 |
| git checkout -b xxx origin/xxx | 从远程新建本地分支 |
| git pull origin master | 合并远程 master 到当前分支 |
| git pull --rebase origin master | 变基到 master 最新状态 |
| git log --oneline --graph --all | 直观查看分支历史 |
| git status | 查看当前状态 |


🛡️ 9. Tips & 风险防控

  • 【必须】始终 pull,再 push
  • 多人协作时尽量避免直接重型 rebase (变基)
  • 使用 stash 临时保存本地修改:
    git stash
    git pull --rebase origin master
    git stash pop
    
  • 保持分支维护经济,时间大的分支尽早合并/删除

CentOS7 安装nodejs 18版本

CentOS7 安装nodejs 18版本

1、centos7中升级make到最新版本

https://www.cnblogs.com/liujiaxin2018/p/16745159.html

  • wget https://ftp.gnu.org/gnu/glibc/glibc-2.28.tar.gz --no-check-certificate

2、安装并启用 devtoolset-8

yum install devtoolset-8
scl enable devtoolset-8 bash
gcc --version

3、永久启用 devtoolset-8

echo "source /opt/rh/devtoolset-8/enable" >> ~/.bashrc
source ~/.bashrc

4、开始编译glibc-2.28


mkdir build && cd build

CFLAGS="-O2 -Wno-error=missing-attributes" ../configure --prefix=/usr --disable-profile --enable-add-ons --with-headers=/usr/include --with-binutils=/usr/bin --enable-obsolete-nsl

make

make install

  • 以上如果make install报错,那么用以下命令重试
cd glibc-2.28
mkdir build
cd build
CFLAGS="-O2 -Wno-error=missing-attributes" ../configure --prefix=/opt/glibc-2.28 --disable-profile --enable-add-ons --enable-obsolete-nsl
make -j4
sudo make install DESTDIR=/opt/glibc-2.28
export LD_LIBRARY_PATH=/opt/glibc-2.28/lib:$LD_LIBRARY_PATH

MyBatis-Plus联表查询的短板,终于有一款工具补齐了

  • mybatis-plus作为mybatis的增强工具,它的出现极大地简化了开发中的数据库操作,但是长久以来,它的联表查询能力一直被大家所诟病。一旦遇到left join或right join的左右连接,你还是得老老实实地打开xml文件,手写上一大段的sql语句。

  • 直到前几天,偶然碰到了这么一款叫做mybatis-plus-join的工具(后面就简称mpj了),使用了一下,不得不说真香!彻底将我从xml地狱中解放了出来,终于可以以类似mybatis-plus中QueryWrapper的方式来进行联表查询了,话不多说,我们下面开始体验。

引入依赖

首先在项目中引入引入依赖坐标,因为mpj中依赖较高版本mybatis-plus中的一些api,所以项目建议直接使用高版本。

<dependency>
    <groupId>com.github.yulichang</groupId>
    <artifactId>mybatis-plus-join</artifactId>
    <version>1.2.4</version>
</dependency>
<dependency>
    <groupId>com.baomidou</groupId>
    <artifactId>mybatis-plus-boot-starter</artifactId>
    <version>3.5.1</version>
</dependency>

引入相关依赖后,在springboot项目中,像往常一样正常配置数据源连接信息就可以了。

数据准备

因为要实现联表查询,所以我们先来建几张表进行测试。

订单表:
824d2133203245e4aec8122feb860971.png

用户表,包含用户姓名:
dde7b546424d49b2855311353db4c3a6.jpg

商品表,包含商品名称和单价:
beac53b77c1a466fb307a465210a25af.jpg

在订单表中,通过用户id和商品id与其他两张表进行关联。

修改Mapper

以往在使用myatis-plus的时候,我们的Mapper层接口都是直接继承的BaseMapper,使用mpj后需要对其进行修改,改为继承MPJBaseMapper接口。

@Mapper
public interface OrderMapper extends MPJBaseMapper<Order> {
}

对其余两个表的Mapper接口也进行相同的改造。此外,我们的service也可以选择继承MPJBaseService,serviceImpl选择继承MPJBaseServiceImpl,这两者为非必须继承。

查询

Mapper接口改造完成后,我们把它注入到Service中,虽然说我们要完成3张表的联表查询,但是以Order作为主表的话,那么只注入这一个对应的OrderMapper就可以,非常简单。

@Service
@AllArgsConstructor
public class OrderServiceImpl implements OrderService {
    private final OrderMapper orderMapper;
}

MPJLambdaWrapper

接下来,我们体验一下再也不用写sql的链表查询:

public void getOrder() {
    List<OrderDto> list = orderMapper.selectJoinList(OrderDto.class,
     new MPJLambdaWrapper<Order>()
      .selectAll(Order.class)
      .select(Product::getUnitPrice)
      .selectAs(User::getName,OrderDto::getUserName)
      .selectAs(Product::getName,OrderDto::getProductName)
      .leftJoin(User.class, User::getId, Order::getUserId)
      .leftJoin(Product.class, Product::getId, Order::getProductId)
      .eq(Order::getStatus,3));

    list.forEach(System.out::println);
}

不看代码,我们先调用接口来看一下执行结果:
34b088370b224375ae0f03d1beec49ec.png

可以看到,成功查询出了关联表中的信息,下面我们一点点介绍上面代码的语义。

首先,调用mapper的selectJoinList()方法,进行关联查询,返回多条结果。后面的第一个参数OrderDto.class代表接收返回查询结果的类,作用和我们之前在xml中写的resultType类似。

这个类可以直接继承实体,再添加上需要在关联查询中返回的列表即可:

@Data
@ToString(callSuper = true)
@EqualsAndHashCode(callSuper = true)
public class OrderDto extends Order {
    String userName;
    String productName;
    Double unitPrice;
}

接下来的MPJLambdaWrapper就是构建查询条件的核心了,看一下我们在上面用到的几个方法:

  • selectAll():查询指定实体类的全部字段
  • select():查询指定的字段,支持可变长参数同时查询多个字段,但是在同一个select中只能查询相同表的字段,所以如果查询多张表的字段需要分开写
  • selectAs():字段别名查询,用于数据库字段与接收结果的dto中属性名称不一致时转换
  • leftJoin():左连接,其中第一个参数是参与联表的表对应的实体类,第二个参数是这张表联表的ON字段,第三个参数是参与联表的ON的另一个实体类属性

除此之外,还可以正常调用mybatis-plus中的各种原生方法,文档中还提到,默认主表别名是t,其他的表别名以先后调用的顺序使用t1、t2、t3以此类推。

我们用插件读取日志转化为可读的sql语句,可以看到两条左连接条件都被正确地添加到了sql中:

048bad23630e4e4a9351a527cb7bb5ad.png

MPJQueryWrapper

和mybatis-plus非常类似,除了LamdaWrapper外还提供了普通QueryWrapper的写法,改造上面的代码:

public void getOrderSimple() {
    List<OrderDto> list = orderMapper.selectJoinList(OrderDto.class,
     new MPJQueryWrapper<Order>()
      .selectAll(Order.class)
      .select("t2.unit_price","t2.name as product_name")
      .select("t1.name as user_name")
      .leftJoin("t_user t1 on t1.id = t.user_id")
      .leftJoin("t_product t2 on t2.id = t.product_id")
      .eq("t.status", "3")
    );

    list.forEach(System.out::println);
}

运行结果与之前完全相同,需要注意的是,这样写时在引用表名时不要使用数据库中的原表名,主表默认使用t,其他表使用join语句中我们为它起的别名,如果使用原表名在运行中会出现报错。

并且,在MPJQueryWrapper中,可以更灵活的支持子查询操作,如果业务比较复杂,那么使用这种方式也是不错的选择。

分页查询

mpj中也能很好地支持列表查询中的分页功能,首先我们要在项目中加入分页拦截器:

@Bean
public MybatisPlusInterceptor mybatisPlusInterceptor(){
    MybatisPlusInterceptor interceptor = new MybatisPlusInterceptor();
    interceptor.addInnerInterceptor(new PaginationInnerInterceptor(DbType.H2));
    return interceptor;
}

接下来改造上面的代码,调用selectJoinPage()方法:

public void page() {
    IPage<OrderDto> orderPage = orderMapper.selectJoinPage(
      new Page<OrderDto>(2,10),
      OrderDto.class,
      new MPJLambdaWrapper<Order>()
        .selectAll(Order.class)
        .select(Product::getUnitPrice)
        .selectAs(User::getName, OrderDto::getUserName)
        .selectAs(Product::getName, OrderDto::getProductName)
        .leftJoin(User.class, User::getId, Order::getUserId)
        .leftJoin(Product.class, Product::getId, Order::getProductId)
        .orderByAsc(Order::getId));

    orderPage.getRecords().forEach(System.out::println);
}

注意在这里需要添加一个分页参数的Page对象,我们再执行上面的代码,并对日志进行解析,查看sql语句:

a5cce2c58dd44032b34d75316cf58c23.png

可以看到底层通过添加limit进行了分页,同理,MPJQueryWrapper也可以这样进行分页。

最后

经过简单的测试,个人感觉mpj这款工具在联表查询方面还是比较实用的,能够应对项目中不是非常复杂的场景下的sql查询,大大提高我们的生产效率。当然,在项目的issues中也能看到当前版本中也仍然存在一些问题,希望在后续版本迭代中能继续完善。

Spring Boot踩坑笔记二:SpringBoot整合redis报No qualifying bean of type 'org.springframework.data.redis.core.RedisTemplate<java.lang.String, java.lang.Object>异常

今天在学习Spring Boot整合redis的过程中遇到个问题,在使用注入时,启动项目会报异常

@Autowired
private RedisTemplate<String, Object> redisTemplate;
[2022-07-08 22:56:56,195][DEBUG][main] Application failed to start due to an exception (LoggingFailureAnalysisReporter.java:37)
org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.springframework.data.redis.core.RedisTemplate<java.lang.String, java.lang.Object>' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)}
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoMatchingBeanFound(DefaultListableBeanFactory.java:1801) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1357) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1311) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:656) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:639) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:399) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1431) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:619) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:276) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1391) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1311) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:656) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:639) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:399) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1431) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:619) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:955) ~[spring-beans-5.3.21.jar:5.3.21]
    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) ~[spring-context-5.3.21.jar:5.3.21]
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583) ~[spring-context-5.3.21.jar:5.3.21]
    at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:147) ~[spring-boot-2.7.1.jar:2.7.1]
    at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:734) ~[spring-boot-2.7.1.jar:2.7.1]
    at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:408) ~[spring-boot-2.7.1.jar:2.7.1]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:308) ~[spring-boot-2.7.1.jar:2.7.1]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1306) ~[spring-boot-2.7.1.jar:2.7.1]
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:1295) ~[spring-boot-2.7.1.jar:2.7.1]
    at com.recallg.huobitask.HuoBiTaskApplication.main(HuoBiTaskApplication.java:14) ~[classes/:?]
[2022-07-08 22:56:56,198][ERROR][main] 

***************************
APPLICATION FAILED TO START
***************************

Description:

Field redisTemplate in com.recallg.huobitask.service.cache.impl.RedisServiceImpl required a bean of type 'org.springframework.data.redis.core.RedisTemplate' that could not be found.

The injection point has the following annotations:
    - @org.springframework.beans.factory.annotation.Autowired(required=true)


Action:

Consider defining a bean of type 'org.springframework.data.redis.core.RedisTemplate' in your configuration.
 (LoggingFailureAnalysisReporter.java:40)

Process finished with exit code 1

这么一大串看的是不是有点懵,其实咱们看一句可以了

org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.springframework.data.redis.core.RedisTemplate<java.lang.String, java.lang.Object>' available: expected at least 1 bean which qualifies as autowire candidate

大致意思是没有与RedisTemplate<String, Object>匹配的bean

解决方法

1、不指定泛型,如

@Autowired
private RedisTemplate redisTemplate;

2、使用@Resource注解代替@Autowired,如

@Resource
private RedisTemplate<String, Object> redisTemplate;