一. 安裝Chrome瀏覽器和插件

如何安裝谷歌瀏覽器這里就不做說明了必盖，主要說明下插件如何安裝。

打開>更多工具>擴展工具颊亮，這里說明這三個

正常把插件拖進來即可剔宪，如若不行拂铡，點擊左上方的加載已解壓的擴展程序，將文件后.cxy綴名改成.rar葱绒，然后解壓和媳，選擇該文件即可

IDM是一個多線程的下載工具，安裝后如何集成到谷歌瀏覽器呢哈街？

3. 添加谷歌的打開軟件即可
   
   

   )

二. 安裝JDK配置環(huán)境變量

jdk一般使用1.8版本，無腦下一步安裝即可

1. 配置環(huán)境變量

1. 首先鼠標右擊"計算機" 拒迅，選擇"屬性" 骚秦，然后選其中的"高級系統(tǒng)設置"。

2. 點擊進入選擇“高級”中的“環(huán)境變量”璧微，然后進入環(huán)境變量編輯界面作箍。

3. 在“系統(tǒng)變量”中新建"JAVA_HOME"變量，點擊“新建”并設置參數(shù)(

   變量名輸入：JAVA_HOME

   變量值指的是實際的安裝路徑比如：C:\Program Files\Java\jdk1.8.0_181前硫。

   )胞得。然后點擊確定。

4. 在“系統(tǒng)變量”中屹电，我們找到path變量阶剑，需要點擊“編輯”跃巡，然后進入path變量的編輯界面。（在變量值最后面加上“;%JAVA_HOME%\bin;%JAVA_HOME%\jre\bin”）最后點擊確定牧愁。

5. 在“系統(tǒng)變量”中新建"CLASSPATH"變量素邪，點擊“新建”并設置參數(shù)(

   變量名輸入：CLASSPATH

   變量值鍵入：.;%JAVA_HOME%\lib\dt.jar;%JAVA_HOME%\lib\tools.jar;

   )。然后點擊確定猪半。

6. 測試打開cmd命令窗口兔朦，輸入java出現(xiàn)很多東西表示配置成功

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

三. 安裝idea2020

網(wǎng)上教程很多 我參考的是

IntelliJ IDEA 2020.3.3激活破解教程（親測激活至 2099 年，長期更新）

四. 配置maven

1. 下載并配置環(huán)境變量

1. 到Maven官網(wǎng)下載

2. 選擇左側Download

3. 點擊箭頭所指的鏈接進行下載

4. 下載完成后磨确，選擇一個路徑進行解壓

5. 然后配置path環(huán)境變量,如圖

• 系統(tǒng)變量:MAVEN_HOME = F:\dev\apache-maven-3.6.1

• 系統(tǒng)變量: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>
   

   將它拿到注釋外并將中間的內(nèi)容改成你需要的路徑摆舟，如圖

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. 嫌麻煩的直接復制配置文件的內(nèi)容即可,不過路徑還是要改(參考第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鏡像

安裝過程也是一直點下一步就行胡野，完了有激活碼這里我從網(wǎng)上找的可以使用

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系統(tǒng)控制臺痕鳍，當提示權限不足時輸入：sudo passwd root硫豆，按回車鍵。

2. 提示需要輸入密碼笼呆，此時需要的密碼是Linux系統(tǒng)登錄密碼熊响，輸入時沒有任何提示，輸完直接回車鍵诗赌。

3. 請輸入新的UNIX密碼汗茄，現(xiàn)在要輸入你想設置的root密碼，屏幕不會顯示輸入數(shù)字铭若，輸完回車鍵洪碳。

4. 請重新輸入新的UNIX密碼，把root密碼再次輸入一次叼屠，按回車鍵瞳腌。

5. 出現(xiàn)passwd：密碼更新成功，就表示root密碼設置成功了镜雨。

6. 現(xiàn)在我們驗證下root密碼有沒有設置成功嫂侍，輸入：su，回車，當出現(xiàn)賬號加當前路徑#的時候就表示已經(jīng)進入root控制狀態(tài)了（可觀察下圖和上圖賬號名稱挑宠，是不一樣的）菲盾，普通賬號狀態(tài)為是XX:~$。

控制臺下輸入密碼時痹栖，光標不會有任何提示亿汞，屏幕也不會顯示密碼，輸入密碼直接回車就可以揪阿。

2. Linux安裝redis

參考我之前寫的這篇文章

Redisd的介紹,安裝,客戶端

3. Linux安裝docker

參考我之前寫的這篇文章

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

4. Linux安裝tomcat

參考文章

Linux系統(tǒng)下Tomcat8的安裝詳解(帶圖解)

六. 其他問題

1. 端口被占用導致啟動失敗解決

1. 換端口
2. 殺死端口

第一種

講下如何殺死一個端口

windows+r輸入cmd并打開

輸入netstat -ano

找到8081端口疗我，記住對應的PID:6052

輸入taskkill /pid 6052 -f

第二種

根據(jù)端口找到PID

netstat -aon|findstr “8081”

輸入taskkill /pid 1860 -f

2. U盤提示文件太大不能拷貝

Windows+r輸入cmd

在終端輸入命令convert k:/fs:ntfs命令按回車（注意k是指當前U盤在你電腦的盤符）：

命令執(zhí)行成功如下：

然后重新拷貝就可以了。

3. 激活Office中登錄界面加載緩慢

找到網(wǎng)絡南捂，屬性中修改dns為4.2.2.1

詳情參考microsoft賬戶無法登陸怎么辦吴裤？

改完就可以流暢登微軟的東西了。登完微軟的記得改回來溺健，不然玩不了其他