一. 安装Chrome浏览器和插件

如何安装谷歌浏览器这里就不做说明了，主要说明下插件如何安装。

打开>更多工具>扩展工具，这里说明这三个

正常把插件拖进来即可，如若不行，点击左上方的加载已解压的扩展程序，将文件后.cxy缀名改成.rar，然后解压，选择该文件即可

IDM是一个多线程的下载工具，安装后如何集成到谷歌浏览器呢？

3. 添加谷歌的打开软件即可
   
   

   )

二. 安装JDK配置环境变量

jdk一般使用1.8版本，无脑下一步安装即可

1. 配置环境变量

1. 首先鼠标右击"计算机" ，选择"属性" ，然后选其中的"高级系统设置"。

2. 点击进入选择“高级”中的“环境变量”，然后进入环境变量编辑界面。

3. 在“系统变量”中新建"JAVA_HOME"变量，点击“新建”并设置参数(

   变量名输入：JAVA_HOME

   变量值指的是实际的安装路径比如：C:\Program Files\Java\jdk1.8.0_181。

   )。然后点击确定。

4. 在“系统变量”中，我们找到path变量，需要点击“编辑”，然后进入path变量的编辑界面。（在变量值最后面加上“;%JAVA_HOME%\bin;%JAVA_HOME%\jre\bin”）最后点击确定。

5. 在“系统变量”中新建"CLASSPATH"变量，点击“新建”并设置参数(

   变量名输入：CLASSPATH

   变量值键入：.;%JAVA_HOME%\lib\dt.jar;%JAVA_HOME%\lib\tools.jar;

   )。然后点击确定。

6. 测试打开cmd命令窗口，输入java出现很多东西表示配置成功

java1.5版本之后可不需要设置classpath

三. 安装idea2020

网上教程很多 我参考的是

IntelliJ IDEA 2020.3.3激活破解教程（亲测激活至 2099 年，长期更新）

四. 配置maven

1. 下载并配置环境变量

1. 到Maven官网下载

2. 选择左侧Download

3. 点击箭头所指的链接进行下载

4. 下载完成后，选择一个路径进行解压

5. 然后配置path环境变量,如图

• 系统变量:MAVEN_HOME = F:\dev\apache-maven-3.6.1

• 系统变量:path = %MAVEN_HOME%\bin

6. 然后win+R 运行cmd 输入 mvn -version，如图所示则配置成功

2. 配置setting文件

1. 在F:\dev\apache-maven-3.6.1\conf下可以找到settings文件，打开(嫌麻烦的直接看最后一步)

2. 找到第52行，这里是maven默认的仓库

3. 我们复制第53行

   <localRepository>/path/to/local/repo</localRepository>
   

   将它拿到注释外并将中间的内容改成你需要的路径，如图

4. 因为国外的服务器下载jar包很慢所以我们改为阿里云服务器（大约在150行左右），这两个仓库建议第一个)

   <!-- 阿里云仓库 -->
   <mirror>
       <id>alimaven</id>
       <mirrorOf>central</mirrorOf>
       <name>aliyun maven</name>
       <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
   </mirror>
   或者
   <mirror>
       <id>nexus-aliyun</id>
       <mirrorOf>*</mirrorOf>
       <name>Nexus aliyun</name>
       <url>http://maven.aliyun.com/nexus/content/groups/public</url>
   </mirror>
   

5. 如图，要夹在两个mirrors标签之间

6. 在最后配置jdk，也要夹在两个profiles标签之间(我这里使用的为jdk8)

   <!-- java版本 --> 
   <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>
   

7. 配置完成，在命令行输入mvn help:system测试，看到下载链接里面是ailiyun的链接表示配置成功

8. 嫌麻烦的直接复制配置文件的内容即可,不过路径还是要改(参考第3步)

   <?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>/path/to/local/repo</localRepository>
     -->
       <localRepository>F:/repository</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.
      |-->
   
       <!-- mirror
    <mirrors>
        | 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>
     </mirrors>
        -->
       <!-- 阿里云仓库 -->
       <mirrors>
           <mirror>
               <id>nexus-aliyun</id>
               <mirrorOf>*</mirrorOf>
               <name>Nexus aliyun</name>
               <url>http://maven.aliyun.com/nexus/content/groups/public</url>
           </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.
      |
      |-->
       <!-- profile
    <profiles>
        | 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>
   
       -->
       <profiles>
           <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>
   

五. 虚拟机安装

首先需要安装包和一个Linux镜像

安装过程也是一直点下一步就行，完了有激活码这里我从网上找的可以使用

UY758-0RXEQ-M81WP-8ZM7Z-Y3HDA

VF750-4MX5Q-488DQ-9WZE9-ZY2D6

UU54R-FVD91-488PP-7NNGC-ZFAX6

YC74H-FGF92-081VZ-R5QNG-P6RY4

YC34H-6WWDK-085MQ-JYPNX-NZRA2

1. Linux如何切换到root用户

在虚拟机上安装Linux后，由于进入的时候不是root所以一些操作会受到限制

1. 打开Linux系统控制台，当提示权限不足时输入：sudo passwd root，按回车键。

2. 提示需要输入密码，此时需要的密码是Linux系统登录密码，输入时没有任何提示，输完直接回车键。

3. 请输入新的UNIX密码，现在要输入你想设置的root密码，屏幕不会显示输入数字，输完回车键。

4. 请重新输入新的UNIX密码，把root密码再次输入一次，按回车键。

5. 出现passwd：密码更新成功，就表示root密码设置成功了。

6. 现在我们验证下root密码有没有设置成功，输入：su，回车，当出现账号加当前路径#的时候就表示已经进入root控制状态了（可观察下图和上图账号名称，是不一样的），普通账号状态为是XX:~$。

控制台下输入密码时，光标不会有任何提示，屏幕也不会显示密码，输入密码直接回车就可以。

2. Linux安装redis

参考我之前写的这篇文章

Redisd的介绍,安装,客户端

3. Linux安装docker

参考我之前写的这篇文章

Docker(1)-Docker的安装-常用命令

4. Linux安装tomcat

参考文章

Linux系统下Tomcat8的安装详解(带图解)

六. 其他问题

1. 端口被占用导致启动失败解决

1. 换端口
2. 杀死端口

第一种

讲下如何杀死一个端口

windows+r输入cmd并打开

输入netstat -ano

找到8081端口，记住对应的PID:6052

输入taskkill /pid 6052 -f

第二种

根据端口找到PID

netstat -aon|findstr “8081”

输入taskkill /pid 1860 -f

2. U盘提示文件太大不能拷贝

Windows+r输入cmd

在终端输入命令convert k:/fs:ntfs命令按回车（注意k是指当前U盘在你电脑的盘符）：

命令执行成功如下：

然后重新拷贝就可以了。

3. 激活Office中登录界面加载缓慢

找到网络，属性中修改dns为4.2.2.1

详情参考microsoft账户无法登陆怎么办？

改完就可以流畅登微软的东西了。登完微软的记得改回来，不然玩不了其他