SpringBoot项目打包部署上线全流程本地跑得好好的一上线就白屏500——这大概是每个后端新手都经历过的噩梦。打包部署看似简单但细节不到位就会踩坑。本文带你从打包到上线全流程走一遍。一、打包方式jar vs warSpringBoot支持两种打包方式对比项jar包war包Web容器内嵌Tomcat独立运行需外部Tomcat部署部署方式java -jar直接运行放入Tomcat的webapps目录配置复杂度低开箱即用高需配置外部Tomcat性能与外部Tomcat无明显差异同左适用场景微服务、容器化部署传统部署、需与Tomcat共存推荐使用jar包。SpringBoot的设计理念就是内嵌容器、独立运行jar包部署最简单。除非公司有统一的外部Tomcat要求否则没必要用war包。war包打包改造了解即可packagingwar/packagingdependencygroupIdorg.springframework.boot/groupIdartifactIdspring-boot-starter-tomcat/artifactIdscopeprovided/scope!-- 打包时排除内嵌Tomcat --/dependency启动类继承SpringBootServletInitializerpublicclassApplicationextendsSpringBootServletInitializer{OverrideprotectedSpringApplicationBuilderconfigure(SpringApplicationBuilderbuilder){returnbuilder.sources(Application.class);}}二、Maven打包配置2.1 spring-boot-maven-pluginbuildfinalNameshop-app/finalName!-- 打包后的文件名 --pluginsplugingroupIdorg.springframework.boot/groupIdartifactIdspring-boot-maven-plugin/artifactIdconfigurationmainClasscom.example.ShopApplication/mainClass/configurationexecutionsexecutiongoalsgoalrepackage/goal!-- 打成可执行jar --/goals/execution/executions/plugin/plugins/build2.2 执行打包# 清理打包跳过测试加速mvn clean package-DskipTests# 打包后会在target目录生成# target/shop-app.jar三、多环境打包实际开发中至少有开发、测试、生产三套环境配置各不相同。3.1 多环境配置文件resources/ ├── application.yml # 主配置公共配置 ├── application-dev.yml # 开发环境 ├── application-test.yml # 测试环境 └── application-prod.yml # 生产环境主配置文件中指定激活的环境spring:profiles:active:spring.profiles.active# 通过Maven占位符注入3.2 Maven多环境Profileprofilesprofileiddev/idpropertiesspring.profiles.activedev/spring.profiles.active/propertiesactivationactiveByDefaulttrue/activeByDefault!-- 默认激活dev --/activation/profileprofileidtest/idpropertiesspring.profiles.activetest/spring.profiles.active/properties/profileprofileidprod/idpropertiesspring.profiles.activeprod/spring.profiles.active/properties/profile/profiles3.3 按环境打包# 打生产环境包mvn clean package-Pprod-DskipTests# 打测试环境包mvn clean package-Ptest-DskipTests也可以运行时通过命令行参数覆盖java-jarshop-app.jar--spring.profiles.activeprod四、jar包运行方式4.1 前台运行java-jarshop-app.jar关掉终端服务就停了仅适合临时调试。4.2 后台运行nohupjava-jarshop-app.jar--spring.profiles.activeprod/dev/null21# nohup终端关闭后进程不退出# /dev/null标准输出丢弃# 21错误输出也重定向到标准输出# 后台运行4.3 查看日志# 实时查看日志tail-fnohup.out# 或配置了logback日志文件tail-f/var/log/shop-app/info.log五、启动参数优化生产环境不能裸跑java -jar需要配置JVM参数java\-Xms512m\# 初始堆内存-Xmx512m\# 最大堆内存与Xms一致避免动态扩缩-Xmn256m\# 新生代大小-XX:MetaspaceSize128m\# 元空间初始大小-XX:MaxMetaspaceSize256m\# 元空间最大大小-XX:UseG1GC\# 使用G1垃圾收集器-XX:MaxGCPauseMillis200\# GC最大停顿时间目标-XX:HeapDumpOnOutOfMemoryError\# OOM时自动dump-XX:HeapDumpPath/var/log/dump/\# dump文件路径-Dserver.port8080\# 应用端口-jarshop-app.jar\--spring.profiles.activeprod参数说明-Xms / -Xmx建议设为相同值避免JVM动态调整堆大小带来的性能开销G1收集器JDK9默认即为G1适合大内存、低延迟场景HeapDumpOnOutOfMemoryErrorOOM时自动生成堆转储文件方便事后分析六、Linux部署流程6.1 上传jar包# 使用scp上传scptarget/shop-app.jar userserver:/opt/app/# 或使用rz命令需安装lrzszrz6.2 创建启动脚本#!/bin/bash# /opt/app/shop-app/start.shAPP_NAMEshop-appAPP_DIR/opt/app/shop-appJAR_FILE$APP_DIR/$APP_NAME.jarLOG_DIR/var/log/$APP_NAMEJAVA_OPTS-Xms512m -Xmx512m -XX:UseG1GC -XX:HeapDumpOnOutOfMemoryError -XX:HeapDumpPath$LOG_DIR/mkdir-p$LOG_DIR# 停止旧进程PID$(ps-ef|grep$JAR_FILE|grep-vgrep|awk{print $2})if[-n$PID];thenecho停止旧进程:$PIDkill-15$PIDsleep3fi# 启动nohupjava$JAVA_OPTS-jar$JAR_FILE--spring.profiles.activeprod$LOG_DIR/startup.log21echo启动完成PID:$!七、systemd服务配置手动用脚本管理进程不够优雅Linux的systemd可以像管理系统服务一样管理Java应用。7.1 创建service文件# /etc/systemd/system/shop-app.service[Unit]DescriptionShop Application ServiceAfternetwork.target mysql.service redis.service[Service]TypesimpleUserappuser# 运行用户非rootWorkingDirectory/opt/app/shop-app# 工作目录ExecStart/usr/bin/java-Xms512m-Xmx512m-XX:UseG1GC-jar/opt/app/shop-app/shop-app.jar--spring.profiles.activeprodExecStop/bin/kill-15$MAINPIDRestartalways# 崩溃后自动重启RestartSec10# 重启间隔10秒StandardOutputappend:/var/log/shop-app/systemd.logStandardErrorappend:/var/log/shop-app/systemd-error.log[Install]WantedBymulti-user.target7.2 服务管理命令# 重新加载service配置systemctl daemon-reload# 启动systemctl start shop-app# 停止systemctl stop shop-app# 重启systemctl restart shop-app# 查看状态systemctl status shop-app# 开机自启systemctlenableshop-app# 查看实时日志journalctl-ushop-app-f配置systemd后应用崩溃会自动重启服务器重启后自动拉起运维省心很多。八、Nginx反向代理Java应用直接暴露8080端口不安全也不专业通常用Nginx做反向代理。8.1 基础反向代理配置server { listen 80; server_name api.example.com; location / { proxy_pass http://127.0.0.1:8080; proxy_set_header Host $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_connect_timeout 60s; proxy_read_timeout 120s; proxy_send_timeout 60s; } }8.2 SSL证书配置HTTPSserver { listen 443 ssl; server_name api.example.com; ssl_certificate /etc/nginx/ssl/example.com.pem; ssl_certificate_key /etc/nginx/ssl/example.com.key; ssl_protocols TLSv1.2 TLSv1.3; ssl_ciphers HIGH:!aNULL:!MD5; location / { proxy_pass http://127.0.0.1:8080; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } } # HTTP自动跳转HTTPS server { listen 80; server_name api.example.com; return 301 https://$host$request_uri; }8.3 静态资源代理前后端分离部署时前端静态资源也由Nginx托管location /static/ { alias /opt/app/frontend/dist/; expires 30d; add_header Cache-Control public, immutable; } location /api/ { proxy_pass http://127.0.0.1:8080/; }九、Docker部署方式预告传统部署方式需要手动安装JDK、配置环境迁移到新服务器得重来一遍。Docker把应用和环境打包成镜像一次构建到处运行。# Dockerfile FROM eclipse-temurin:17-jre-alpine WORKDIR /app COPY target/shop-app.jar app.jar EXPOSE 8080 ENTRYPOINT [java, -Xms512m, -Xmx512m, -jar, app.jar, --spring.profiles.activeprod]# 构建镜像dockerbuild-tshop-app:1.0.# 运行容器dockerrun-d--nameshop-app-p8080:8080 shop-app:1.0Docker部署是当前主流方案后续会专门展开讲解。十、完整部署checklist上线前逐项检查避免遗漏□ 环境检查 □ JDK版本与开发环境一致 □ MySQL/Redis等中间件已就绪 □ 防火墙端口已开放 □ 服务器时区正确timedatectl set-timezone Asia/Shanghai □ 打包 □ mvn clean package -Pprod -DskipTests □ 检查target目录下jar包是否生成 □ 确认application-prod.yml中数据库地址/密码正确 □ 上传 □ scp上传jar包到服务器 □ 确认目录权限 □ 启动 □ 配置systemd service文件 □ systemctl daemon-reload systemctl start shop-app □ systemctl enable shop-app开机自启 □ 验证 □ systemctl status shop-app状态为active □ curl http://localhost:8080/actuator/health返回UP □ Nginx反向代理配置完成并测试 □ 浏览器访问域名验证接口正常 □ 监控 □ Prometheus已配置抓取目标 □ Grafana仪表盘数据正常 □ 告警规则已配置从打包到部署到验证每个环节都有坑。按checklist走一遍该检查的检查到位上线就不会手忙脚乱。部署这件事没有捷径就是细节到位、流程规范。