Springboot的项目部署(保姆式教程)

已于 2023-12-06 15:49:01 修改
阅读量454 收藏 5
点赞数 6
文章标签： spring boot 后端 java
于 2023-12-06 15:45:11 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/m0_56951095/article/details/134832805
版权

前提环境条件准备(主页有对应软件的教程安装)

jdk1.8 (建议1.8版本) 

maven3.6.3

idea-2021

mysql5.7(建议5.7版本)

复制项目根路径

打开idea, 选择项目 根路径

打开之后项目结构如下

配置maven

配置如下(改成自己的)

右下角的进度条代表依赖正在下载, 可以去对应的本地maven仓库查看是否下载了依赖(使用阿里云镜像下载会更快)

maven的settings文件配置(直接复制下面所以代码,覆盖现有的settings文件即可)

<?xml version="1.0" encoding="UTF-8"?>

<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you 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.
-->

<!--
 | This is the configuration file for Maven. It can be specified at two levels:
 |
 |  1. User Level. This settings.xml file provides configuration for a single user,
 |                 and is normally provided in ${user.home}/.m2/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -s /path/to/user/settings.xml
 |
 |  2. Global Level. This settings.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in
 |                 ${maven.conf}/settings.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -gs /path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ${user.home}/.m2/repository
  <localRepository>D:\develop\apache-maven-3.5.2\repository</localRepository>
  -->
 <localRepository>F:\babasuper\maven-resp</localRepository>
  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for
   | the parameter in question.
   |
   | Default: true
  <interactiveMode>true</interactiveMode>
  -->

  <!-- offline
   | Determines whether maven should attempt to connect to the network when executing a build.
   | This will have an effect on artifact downloads, artifact deployment, and others.
   |
   | Default: false
  <offline>false</offline>
  -->

  <!-- pluginGroups
   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
   |-->
  <pluginGroups>
    <!-- pluginGroup
     | Specifies a further group identifier to use for plugin lookup.
    <pluginGroup>com.your.plugins</pluginGroup>
    -->
  </pluginGroups>

  <!-- proxies
   | This is a list of proxies which can be used on this machine to connect to the network.
   | Unless otherwise specified (by system property or command-line switch), the first proxy
   | specification in this list marked as active will be used.
   |-->
  <proxies>
    <!-- proxy
     | Specification for one proxy, to be used in connecting to the network.
     |
    <proxy>
      <id>optional</id>
      <active>true</active>
      <protocol>http</protocol>
      <username>proxyuser</username>
      <password>proxypass</password>
      <host>proxy.host.net</host>
      <port>80</port>
      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
    </proxy>
    -->
  </proxies>

  <!-- servers
   | This is a list of authentication profiles, keyed by the server-id used within the system.
   | Authentication profiles can be used whenever maven must make a connection to a remote server.
   |-->
  <servers>
    <!-- server
     | Specifies the authentication information to use when connecting to a particular server, identified by
     | a unique name within the system (referred to by the 'id' attribute below).
     |
     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
     |       used together.
     |
    <server>
      <id>deploymentRepo</id>
      <username>repouser</username>
      <password>repopwd</password>
    </server>
    -->

    <!-- Another sample, using keys to authenticate.
    <server>
      <id>siteServer</id>
      <privateKey>/path/to/private/key</privateKey>
      <passphrase>optional; leave empty if not used.</passphrase>
    </server>
    -->
  </servers>

  <!-- mirrors
   | This is a list of mirrors to be used in downloading artifacts from remote repositories.
   |
   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
   | However, this repository may have problems with heavy traffic at times, so people have mirrored
   | it to several places.
   |
   | That repository definition will have a unique id, so we can create a mirror reference for that
   | repository, to be used as an alternate download site. The mirror site will be the preferred
   | server for that repository.
   |-->
  <mirrors>
    <!-- mirror
     | Specifies a repository mirror site to use instead of a given repository. The repository that
     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
     |
    <mirror>
      <id>mirrorId</id>
      <mirrorOf>repositoryId</mirrorOf>
      <name>Human Readable Name for this Mirror.</name>
      <url>http://my.repository.com/repo/path</url>
    </mirror>
	
	<mirror>
　　<id>repo2</id>
　　<mirrorOf>central</mirrorOf>
　　<name>Human Readable Name for this Mirror.</name>
　　<url>http://repo2.maven.org/maven2/</url>
	</mirror>-->
	
	<mirror>
      <id>AliMaven</id>
      <name>aliyun maven</name>
      <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
	  <mirrorOf>central</mirrorOf>
    </mirror>

  </mirrors>

  <!-- profiles
   | This is a list of profiles which can be activated in a variety of ways, and which can modify
   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
   | specific paths and repository locations which allow the build to work in the local environment.
   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is
   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a system property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
   | Finally, the list of active profiles can be specified directly from the command line.
   |
   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
   |       repositories, plugin repositories, and free-form properties to be used as configuration
   |       variables for plugins in the POM.
   |
   |-->
  <profiles>
    <!-- profile
     | Specifies a set of introductions to the build process, to be activated using one or more of the
     | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
     | or the command line, profiles have to have an ID that is unique.
     |
     | An encouraged best practice for profile identification is to use a consistent naming convention
     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
     | This will make it more intuitive to understand what the set of introduced profiles is attempting
     | to accomplish, particularly when you only have a list of profile id's for debug.
     |
     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
    <profile>
      <id>jdk-1.4</id>

      <activation>
        <jdk>1.4</jdk>
      </activation>

      <repositories>
        <repository>
          <id>jdk14</id>
          <name>Repository for JDK 1.4 builds</name>
          <url>http://www.myhost.com/maven/jdk14</url>
          <layout>default</layout>
          <snapshotPolicy>always</snapshotPolicy>
        </repository>
      </repositories>
    </profile>
    -->

    <!--
     | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
     | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
     | might hypothetically look like:
     |
     | ...
     | <plugin>
     |   <groupId>org.myco.myplugins</groupId>
     |   <artifactId>myplugin</artifactId>
     |
     |   <configuration>
     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
     |   </configuration>
     | </plugin>
     | ...
     |
     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
     |       anything, you could just leave off the <value/> inside the activation-property.
     |
    <profile>
      <id>env-dev</id>

      <activation>
        <property>
          <name>target-env</name>
          <value>dev</value>
        </property>
      </activation>

      <properties>
        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
      </properties>
    </profile>
    -->
	
	 <profile>
	  <id>jdk-1.8</id>
	  <activation>
		<activeByDefault>true</activeByDefault>
		<jdk>1.8</jdk>
	  </activation>
	  <properties>
		<maven.compiler.source>1.8</maven.compiler.source>
		<maven.compiler.target>1.8</maven.compiler.target>
		<maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
	  </properties>
	</profile>
  </profiles>

  <!-- activeProfiles
   | List of profiles that are active for all builds.
   |
  <activeProfiles>
    <activeProfile>alwaysActiveProfile</activeProfile>
    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
  </activeProfiles>
  -->
</settings>

爱改bug的小伟
关注
  • 6
    点赞
  • 踩
  • 5
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
SpringBoot项目部署
qq_48788523的博客
04-06 4423
SpringBoot的项目部署
springboot集成seata事务案例保姆式教程
qq_15794365的博客
07-02 450
Seata是一款开源的分布式事务解决方案，它诞生于阿里巴巴的分布式数据库中间件团队，原名Fescar（Fast & Easy Commit And Rollback）。Seata旨在为微服务架构下的应用程序提供高性能和高可靠的分布式事务处理能力，使得开发者能够在分布式系统中轻松实现全局事务的ACID（原子性、一致性、隔离性、持久性）特性。
SpringBoot 项目搭建（详细介绍+案例源码）
热门推荐
zzvar的博客
06-22 4万+
SpringBoot 项目搭建SpringBoot 项目整合源码SpringBoot 项目整合一、项目准备1.1 快速创建 SpringBoot 项目1.2 标准项目结构图如下1.3 添加springboot-parent1.4 添加 spring-boot-start-web1.5 添加 Lambok 依赖1.6 SpringBoot 打包插件1.7 添加 application.properties1.8 编写启动类App1.9 在 resources 创建static静态资源目录1.10 在 reso
新手快速部署Springboot 的Jar包 (图解-BuiId,Maven)
最新发布
键盘爱好者
07-05 293
先准备一个相对于的数据库依赖+ 数据库的任意库 + Yaml配置后 才能正常在IDEA中跑起来。配置好与本地/云端环境同样的环境，然后确定好版本等...(到底啦~vx公众号: wmcode 有更多精彩内容)(up使用的是 Apifox 接口测试软件)我的项目是SpringBoot2脚手架。我的后端Server接口是80。以上就 Maven 打包流程.以上就 BuiId打包流程.构建好后的就是以下效果了.执行到点击的那一个选项。直接双击这个就行了(
SpringBoot-项目部署
踏雨歌青春，诗酒趁年华
01-15 3950
本文讲解如何线上发布SpringBoot项目。项目部署可以通过将项目打成可执行的jar包或war包来实现，也可以使用容器化技术如Docker将项目部署到云平台中。在部署时需要注意配置文件的位置和启动参数的设置，同时确保目标环境中的Java版本与项目所需的Java版本一致。部署完成后，可以通过访问项目的URL或监控端点来进行访问和管理。
springboot 部署
w_wensan的博客
03-21 289
作者：https://my.oschina.net/watsonos/blog/1647708   springboot的应用打包默认是打成jar包，并且如果是web应用的话，默认使用内置的tomcat充当servlet容器，但内置的tomcat有时候并不满足我们的需求，当我们需要把springboot的jar应用打包成war包并在外部tomcat中部署时，默认的设置就需要更改了。        ...
Spring Boot 部署
flyingdream123的专栏
05-14 147
启动打包 ​​​​​​​ 将打包好的Jar文件复制到服务器上 进CMD命令行,启动应用程序，执行：Java -jartest-mybatis-0.0.1-SNAPSHOT.jar
springboot+thymeleaf+mybatis 员工管理系统（保姆式教程）
yyyy11119的博客
08-02 608
目录1、结果展示2、需求分析3、库表设计(概要设计)4、详细设计5、编码6、用户模块7、员工模块8、测试9、上线一、结果展示我就先把完成的效果放出来，具体实现在后面注册页面能动态实现验证码的切换验证,并且密码进行md5加密，可以上传员工头像更改员工信息可以选择是否重新上传头像还可以删除和退出退出登录，并进行判断避免误删需求分析分析这个项目含有那些功能模块用户模块注册登录验证码安全退出展示用户员工模...
推荐一个 Spring Boot 3 + Vue 3 的学习型开源项目，配备保姆级项目开发教程
ZzzzjQqqq的博客
05-26 1164
项目简介 novel 是一套基于时下最新 Java 技术栈 Spring Boot 3 + Vue 3 开发的前后端分离学习型小说项目，配备保姆级项目开发教程手把手教你从零开始开发上线一个生产级别的 Java 系统。由小说门户系统、作家后台管理系统、平台后台管理系统等多个子系统构成。包括小说推荐、作品检索、小说排行榜、小说阅读、小说评论、会员中心、作家专区、充值订阅、新闻发布等功能。 项目地址 后端项目（更新中）：GitHub｜码云 后端微服务版本项目（待更新）：GitHub｜码云 前端项...
非常全面的 SpringBoot 保姆级笔记，面面俱到，太牛了
m0_67698950的博客
08-30 160
本专栏共7个模块，28个节点，介绍 Spring Boot 框架所提供的系统开发解决方案以及源码分析。一、Spring Boot快速入门介绍 Spring 家族的整个生态系统和技术体系，通过系统分析通过 Spring Boot 构建一个完整 Web 应用程序的功能特性和开发流程。二、Spring Boot Web开发这部分详细介绍 Spring Boot 中最具特色的配置体系和自动配置机制，并详细给出如何使用、管理和定制配置项的实现方法。三、Spring Boot 数据访问。...
springboot部署
u014340331的博客
12-17 178
deploy热部署 热部署配置过程: 1、spring.thymeleaf.cache=false关闭页面缓存 2、xml中定义devtools org.springframework.boot spring-boot-devtools 在maven-plugin中增加 <configuration> <!--增加fork才允许热部署，fork交叉 --> <fork>true</
SpringBoot部署
Lovely-Zhang-1026的博客
03-28 5623
springboot依赖环境和版本新特性 需要依赖maven环境，和jdk1 .8及以上版本 SpringBoot所具备的特征有: (1)可以创建独立的Spring应用程序,并且基于其Maven或Gradle插件, 可以创建可执行的JARs和WARs; (2)内嵌Tomcat或Jetty等Servlet容器; (3)提供自动配置的"starter" 项目对象模型(POMS) 以简化Maven配置; (4)尽可能自动配置Spring容器; (5)提供准备好的特性,如指标、健康检查和外部化配置; (6)绝对没
springboot单体项目部署
m0_63040701的博客
11-15 344
注意：如果是单体项目的话，前端页面是和后端整合在一起的，我们需要配置一下页面的路径，不然打包成jar包后找不到文件位置。-- 复制jar包到docker容器指定目录 -->-- 从哪个包拷贝文件，target包 -->-- Dockerfile定义 -->-- 拷贝哪个文件 -->-- Docker路径 -->检查黑白名单是否有问题，是否需要更改。-- 镜像版本 -->-- 镜像名 -->http://ip:端口号/路径。查看端口是否为需要搭建的端口。查看数据库是否为线上数据库。这里采用maven构建。
springboot项目部署
u_525978的博客
09-27 1344
本次选择使用传统部署方式完成项目部署，并且所有资源皆在一台服务器上完成部署，由于是部署springboot项目，所以需要在云服务器上安装对应的JDK、数据库、“redis等等
部署springboot项目
wu可达的博客
08-23 1722
开发完了以后要部署，那么怎么部署呢？ 第一种：jar方式 注意是在springboot/target目录下生成一个jar文件 然后直接输入链接就可以访问了 第二种：war部署 哪种好？ 最近公司在做一些内部的小型Web应用时， 为了提高开发效率决定使用SpringBoot， 这货自带Servlet容器， 你在开发Web应用时可以直接在本地像运行控制台应用一样启动，省...
springboot集成mybatis保姆级教程
04-30
SpringBoot是一个非常流行的Java Web开发框架，而MyBatis则是Java开发中常用的ORM框架。在实际项目中，我们常常需要将两者结合起来使用。本文将为大家提供一个保姆级教程，详细讲解SpringBoot如何集成MyBatis。 一、引入相关依赖 在SpringBoot中集成MyBatis，需要在pom.xml文件中引入相关依赖。具体的依赖如下： <!-- MyBatis依赖 --> <dependency> <groupId>org.mybatis.spring.boot</groupId> <artifactId>mybatis-spring-boot-starter</artifactId> <version>2.1.1</version> </dependency> <!-- 数据库驱动依赖 --> <dependency> <groupId>com.h2database</groupId> <artifactId>h2</artifactId> <version>1.4.200</version> </dependency> 二、配置数据源 在集成MyBatis之前，需要先配置数据源。可以在application.yml文件中添加如下配置： # 数据库配置 spring: datasource: url: jdbc:h2:file:./data/test;DB_CLOSE_ON_EXIT=FALSE username: sa password: driver-class-name: org.h2.Driver 这里使用了h2数据库，并指定了特定的路径和用户名、密码。 三、配置Mapper 接下来需要配置Mapper。在创建Mapper之前，需要先创建Java实体类。例如，可以创建一个User实体类： public class User { private Integer id; private String name; private Integer age; /* 省略setter和getter方法 */ } 然后，可以创建对应的Mapper： @Mapper public interface UserMapper { @Select("select * from user where id = #{id}") User selectUserById(Integer id); @Insert("insert into user(name, age) values(#{name}, #{age})") int insertUser(User user); @Delete("delete from user where id = #{id}") int deleteUser(Integer id); @Update("update user set name = #{name}, age = #{age} where id = #{id}") int updateUser(User user); } 在这里我们使用了注解方式对Mapper进行配置。 四、配置MyBatis 在使用MyBatis之前，需要先进行配置。在application.yml文件中添加如下配置： # MyBatis配置 mybatis: mapper-locations: classpath:mapper/*.xml type-aliases-package: com.example.springbootmybatis.entity 这里指定了Mapper的XML文件位置和Java实体类所在的包路径。 五、在Controller中使用Mapper 最后，可以在Controller中使用Mapper。例如： @RestController public class UserController { @Autowired private UserMapper userMapper; @GetMapping("/user/{id}") public User selectUserById(@PathVariable("id") Integer id) { return userMapper.selectUserById(id); } @PostMapping("/user") public int insertUser(@RequestBody User user) { return userMapper.insertUser(user); } @DeleteMapping("/user/{id}") public int deleteUserById(@PathVariable("id") Integer id) { return userMapper.deleteUser(id); } @PutMapping("/user") public int updateUser(@RequestBody User user){ return userMapper.updateUser(user); } } 这里@Autowired注解注入了UserMapper，然后我们可以在方法中调用UserMapper的方法。 通过以上步骤，我们就成功地将MyBatis集成进了SpringBoot。在实际项目中，可以根据需要修改和扩展上述内容。
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值