(2/4) .NET Core Web API + Vue By Linux and Windows 部署方案知识点总结

# 安装Git 工具
  $ sudo yum -y install git

# 设置安装源
  $ sudo rpm -Uvh https://packages.microsoft.com/config/centos/7/packages-microsoft-prod.rpm
# 安装dotnet-sdk-3.1 
  $ sudo yum install dotnet-sdk-3.1 
# 安装dotnet-sdk-5.0
  $ sudo yum install dotnet-sdk-5.0
# 安装dotnet-sdk-6.0 
  $ sudo yum install dotnet-sdk-6.0
# 检查版本
  $  dotnet --list-sdks

# 进入目录home
  [root@nine ~]# cd /home

# 安装wget
  $  yum -y install wget

# 下载nodejs12.18版本，此版本为编译好的版本，源码编译太多坑，很容易报错
  [root@nine home]# wget https://nodejs.org/dist/v12.18.3/node-v12.18.3-linux-x64.tar.gz

# 解压下载好的node.js包到/usr/local/node-v12.18.3-linux-x64目录下
  [root@nine home]# tar xf node-v12.18.3-linux-x64.tar.gz -C /usr/local/

# 进入usr 目录
  [root@nine home]# cd /usr/local/

# 移动解压好的nodejs到nodejs文件夹
  [root@nine local]# mv node-v12.18.3-linux-x64/ nodejs

# 将目录软链接到全局环境下（命令后面的/usr/local/bin/node是固定的）
  [root@nine local]# ln -s /usr/local/nodejs/bin/node /usr/local/bin
  [root@nine local]# ln -s /usr/local/nodejs/bin/npm /usr/local/bin

# 这样安装好了以后使用npm安装的包(比如：ionic serve)，使用包的命令时可能会提示找不到命令，没关系，在用户目录下终端执行下面命令(固定写法)：
  [root@nine admin]# echo -e "export PATH=$(npm prefix -g)/bin:$PATH" >> ~/.bashrc && source ~/.bashrc

# 检查安装情况，检查版本
  [root@nine local]# node -v  
  v12.18.3

# Eg：
  [root@nine local]# cd /home/code/admin
  [root@nine admin]# npm install
  [root@nine admin]# npm run build

FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-buster-slim AS base 
WORKDIR /app
COPY . . 
EXPOSE 80
ENTRYPOINT ["dotnet", "XXXX.dll","-b","0.0.0.0"]

#简单注释一下：
#FROM：意思是我们的项目源镜像是哪个；
#WORKDIR：镜像的工作目录；
#COPY：复制文件（将Dockerfile所在目录下文件复制到镜像中的工作目录中）
#EXPOSE：容器要开放的端口（我们用.NETCORE的80端口）
#ENTRYPOINT：为容器启动后要执行的命令 （这里将执行dotnet XXXX.dll命令）  xxx改为自己的项目名称

# 进入项目目录
  $ cd /home/core/
# 生成项目
  $ dotnet build
# 发布项目
  $ dotnet publish -o /home/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1

👇-------------------执行效果(预览，部分删减)-------------------👇
Microsoft (R) Build Engine version 16.8.0+126527ff1 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.
  Determining projects to restore...
  Restored /home/core/FD.GenerationTemplate/FD.GenerationTemplate.csproj (in 365 ms).
  Restored /home/core/FD.Redis/FD.Redis.csproj (in 364 ms).
  Restored /home/core/FD.CloudHisCoreApi/FD.CloudHisCoreApi.csproj (in 15.93 sec).
  FD.GenerationTemplate -> /home/core/FD.GenerationTemplate/bin/Debug/netcoreapp3.1/FD.GenerationTemplate.dll
  FD.Redis -> /home/core/FD.Redis/bin/Debug/netcoreapp3.1/FD.Redis.dll
  FD.CloudHisCoreApi -> /home/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1/FD.CloudHisCoreApi.Views.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:46.53
Microsoft (R) Build Engine version 16.8.0+126527ff1 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.

  Determining projects to restore...
  All projects are up-to-date for restore.
  FD.Model -> /home/core/FD.Model/bin/Debug/netcoreapp3.1/FD.Model.dll
  FD.Services -> /home/code/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1/
  FD.CloudHisCoreApi -> /home/code/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1/Microsoft (R) Build Engine version 16.8.0+126527ff1 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.

  Determining projects to restore...
  Restored /home/core/FD.GenerationTemplate/FD.GenerationTemplate.csproj (in 365 ms).
  Restored /home/core/FD.Services/FD.Services.csproj (in 5.16 sec).
  FD.CloudHisCoreApi -> /home/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1/FD.CloudHisCoreApi.Views.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)
👆-------------------执行效果(预览)-------------------👆

# 拉取代码
  $ git pull;
# 清除发布文件的文件夹，确保文件生成都是全新文件
  $ rm -rf .release;
# 生成项目
  $ dotnet build;
# 发布项目
  $ dotnet publish -o /home/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1;
# 复制文件到我们定义好的目录
  $ cp -r /home/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1 .release;
# 提示信息
  $ echo "Successfully!!!! ^ please see the file .release";

# 注：莫吧中文注释复制到批处理中，请直接复制下面这一段
  👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇
  git pull;
  rm -rf .release;
  dotnet build;
  dotnet publish -o /home/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1;
  cp -r /home/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1 .release;
  echo "Successfully!!!! ^ please see the file .release";
  👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆

# 进入项目目录
  $ cd /home/core/
# 执行批处理命令
  $ ./project.release.sh

👇-------------------执行效果(预览，部分删减)-------------------👇
[root@nine .release]# cd /home/core/
[root@nine core]# ./project.release.sh
Microsoft (R) Build Engine version 16.8.0+126527ff1 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.

  Determining projects to restore...
  Restored /home/core/FD.GenerationTemplate/FD.GenerationTemplate.csproj (in 365 ms).
  Restored /home/core/FD.Redis/FD.Redis.csproj (in 364 ms).
  Restored /home/core/FD.CloudHisCoreApi/FD.CloudHisCoreApi.csproj (in 15.93 sec).
  FD.GenerationTemplate -> /home/core/FD.GenerationTemplate/bin/Debug/netcoreapp3.1/FD.GenerationTemplate.dll
  FD.Redis -> /home/core/FD.Redis/bin/Debug/netcoreapp3.1/FD.Redis.dll
  FD.Model -> /home/core/FD.Model/bin/Debug/netcoreapp3.1/FD.Model.dll
  FD.IRepository -> /home/core/FD.IRepository/bin/Debug/netcoreapp3.1/FD.IRepository.dll
  FD.Common -> /home/core/FD.Common/bin/Debug/netcoreapp3.1/FD.Common.dll
  FD.CloudHisCoreApi -> /home/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1/FD.CloudHisCoreApi.dll
  FD.CloudHisCoreApi -> /home/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1/FD.CloudHisCoreApi.Views.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:46.53
Microsoft (R) Build Engine version 16.8.0+126527ff1 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.

  Determining projects to restore...
  All projects are up-to-date for restore.
  FD.Model -> /home/core/FD.Model/bin/Debug/netcoreapp3.1/FD.Model.dll
  FD.Redis -> /home/core/FD.Redis/bin/Debug/netcoreapp3.1/FD.Redis.dll
  FD.Redis -> /home/code/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1/
  FD.Services -> /home/code/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1/
  FD.CloudHisCoreApi -> /home/code/core/FD.CloudHisCoreApi/bin/Debug/netcoreapp3.1/
Successfully!!!! ^ please see the file .release
👆-------------------执行效果(预览)-------------------👆

# 进入发布文件内
  $ cd /home/core/.release
# 测试项目 dotnet FD.CloudHisCoreApi.dll
  $  dotnet FD.CloudHisCoreApi.dll
👇-------------------执行效果(预览)-------------------👇
Last login: Fri Mar 25 11:07:34 2022 from oraybox.lan
[root@nine ~]# cd /home/core/.release
[root@nine .release]# dotnet FD.CloudHisCoreApi.dll
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
      No XML encryptor configured. Key {fcd46988-fb0f-400a-80d6-c461f77a3a05} may be persisted to storage in unencrypted form.
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://localhost:5000
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: https://localhost:5001
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /home/core/.release
👆-------------------执行效果(预览)-------------------👆

可以看到已经正常的监听了5000端口，这里要注意一下，我们在Program.cs文件中，需要配置这样：

.UseUrls("http://*:5000")

Ctrl+C to shut down

# 根据Dockerfile构建镜像
  $ docker build -t jamnine/api .
  -t 镜像名字
  .  所有文件，记得这个点

👇-------------------执行效果(预览)-------------------👇
[root@nine .release]# docker build -t jamnine/api .
Sending build context to Docker daemon  33.92MB
Step 1/5 : FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-buster-slim AS base
 ---> 28de0d96c539
Step 2/5 : WORKDIR /app
 ---> Running in 2fd50bc363b8
Removing intermediate container 2fd50bc363b8
 ---> 95a8b5d87bda
Step 3/5 : COPY . .
 ---> a4880e87ba57
Step 4/5 : EXPOSE 80
 ---> Running in f37fdd29bf1b
Removing intermediate container f37fdd29bf1b
 ---> a6195692236a
Step 5/5 : ENTRYPOINT ["dotnet", "FD.CloudHisCoreApi.dll","-b","0.0.0.0"]
 ---> Running in 4211700fb07b
Removing intermediate container 4211700fb07b
 ---> e3022ca40b3b
Successfully built e3022ca40b3b
Successfully tagged jamnine/api:latest
👆-------------------执行效果(预览)-------------------👆

# 查看镜像
  $  docker images
👇-------------------执行效果(预览)-------------------👇
[root@nine .release]# docker images
REPOSITORY                             TAG                 IMAGE ID            CREATED             SIZE
jamnine/api                            latest              e3022ca40b3b        3 minutes ago       241MB
mcr.microsoft.com/dotnet/aspnet        5.0-buster-slim     c535cc5fb113        16 months ago       205MB
👆-------------------执行效果(预览)-------------------👆

这里有了两个镜像，一个是我们的镜像ID为e3022ca40b3b，大小241M的项目文件，一个是我们Dockerfile的源镜像。

# 生成容器（临时）
  $  docker run -it -p 8081:8081 jamnine/api
👇-------------------执行效果(预览)-------------------👇
[root@nine core]# docker run -it -p 8081:8081 jamnine/api
warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
      Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
      No XML encryptor configured. Key {9d54979d-a5f5-47d0-b965-02e902a0820f} may be persisted to storage in unencrypted form.
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://[::]:80
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /app
👆-------------------执行效果(预览)-------------------👆

# 恭喜！看到这段没报错信息，容器生成成功，Ctrl+C to shut down退出当前进程，查看下有哪些容器：
  $  docker ps -a
  # -a   查看所有容器 
👇-------------------执行效果(预览)-------------------👇
[root@nine core]# docker ps -a
CONTAINER ID        IMAGE                                        COMMAND                  CREATED              STATUS                      PORTS                                           NAMES
583f20c5c996        jamnine/api                                  "dotnet FD.CloudHisC…"   About a minute ago   Exited (0) 11 seconds ago                                                   strange_ardinghelli
👆-------------------执行效果(预览)-------------------👆

# 运行容器
  $  docker start 583f20c5c996

👇-------------------执行效果(预览)-------------------👇
[root@nine core]# docker start 583f20c5c996
583f20c5c996
[root@nine core]# docker ps
CONTAINER ID        IMAGE                  COMMAND                  CREATED             STATUS              PORTS                                           NAMES
583f20c5c996        jamnine/api            "dotnet FD.CloudHisC…"   7 minutes ago       Up 57 seconds       80/tcp, 0.0.0.0:8081->8081/tcp                  strange_ardinghelli
👆-------------------执行效果(预览)-------------------👆
状态已经是运行中了，那怎么测试接口是否正常了呢，继续往下走
测试接口 
#  curl命令
  $  curl http://localhost:8081/api/blog

至此，恭喜你，Docker部署NetCore基本已经搞定了，如果你想看看容器内的日志信息。

# 查看日志
  $  docker logs 583f20c5c996
👇-------------------执行效果(预览)-------------------👇
[root@nine core]# docker logs 583f20c5c996
warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
      Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
      No XML encryptor configured. Key {9d54979d-a5f5-47d0-b965-02e902a0820f} may be persisted to storage in unencrypted form.
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://[::]:80
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /app
👆-------------------执行效果(预览)-------------------👆

#  查看所有镜像 
  $  docker images
#  删除一个imageid的镜像
  $  docker rmi [IMAE_ID]
#  删除所有镜像
  $  sudo docker rmi $(docker images -q)
#  查看所有容器运行状态
  $  docker ps -a
  $  docker container ls -all
#  删除一个containerid的容器(实例)
  $  docker rm 6f0c67de4b72
#  删除所有容器
  $  docker rm $(sudo docker ps -a -q)
#  查看指定时间后的日志，只显示最后100行：
  $  docker logs -f -t --since="2019-06-08" --tail=100 CONTAINER_ID
#  查看某时间之后的日志：
  $  docker logs -t --since="2019-06-08" CONTAINER_ID
#  查看某时间段日志：
  $  docker logs -t --since="2019-06-08" --until "2019-06-09" CONTAINER_ID
#  查看最近30分钟的日志:
  $  docker logs --since 30m CONTAINER_ID
#  停止容器 
  $  docker stop 5ab35ebcb6e2
# 删除容器 
  $  docker rm  5ab35ebcb6e2
#  删除镜像 
  $  docker rmi 7567a38d491c
# 启动容器 
  $  docker start  685cb02f53

# 设置基础镜像
FROM nginx
# 定义作者
MAINTAINER nine
# 将dist文件中的内容复制到 /usr/share/nginx/html/ 这个目录下面
COPY dist/  /usr/share/nginx/html/
COPY nginx.conf /etc/nginx/nginx.conf
RUN echo "Asia/shanghai" > /etc/timezone
RUN echo 'echo init ok!!'

worker_processes auto; 

events {
    worker_connections  1024;
}

http {
    include       mime.types;
    default_type  application/octet-stream;

    gzip  on;
    gzip_min_length 5k; 
    gzip_buffers 4 16k; 
    gzip_comp_level 8; 

    sendfile        on;

    keepalive_timeout  600;

    client_max_body_size   20m;

    server {
        listen       80;
        server_name  localhost;

        location / {
          root   /usr/share/nginx/html;
          index  index.html index.htm;
          try_files $uri $uri/ /index.html;
        }

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

.DS_Store
node_modules

# local env files
.env.local
.env.*.local

# Log files
npm-debug.log*
yarn-debug.log*
yarn-error.log*

#  进入代码目录
  $  cd /home/vue
# 依赖手脚架
  $  npm install
# 发布文件
  $  npm run build
#  拷贝文件到dist目录下，dockerfile和nginx.conf,我这里是在dockerfile目录下放了这两个文件
#  具体根据自己项目情况
  $  cp -r docker/dockerfile/* dist

#  进入打包好的发布文件目录
  $  cd dist/
# 构建容器
  $  docker build -t admin/dev .

#   构建容器
$ docker run --name admindev -v /etc/localtime:/etc/localtime -itd -p 6000:80 admin/dev
#  -v /etc/localtime:/etc/localtime 这里是挂载服务器时间
# -itd 生成容器返回ID，比起上面多了个d
# -p 宿主机6000映射容器80端口

这个方案如果是个人的话，需要在开发环境安装Docker，
本地都打包好，推送镜像到仓库，个人的话做这个有点多余
其实本质就是把自己的电脑当服务器使用，最后服务器只是生成一下容器启动

但这个方案在公司内还是比较常见的，
公司发布组打包发布测试好的镜像统一推送分发，维护实施人员进行创建容器即可
保持了镜像统一

没有最好的方案，只有最适合，都是取舍

这个方案的话，个人更没必要了
公司内部的话，生成文件放到服务器，由实施运维人员去服务器打包等等，还有一点应用场景

反正这三种方案，你懂什么原理即可，再怎么变，都万变不离其中

1.获取代码 2.生成项目发布文件
3.创建镜像 4.创建容器

始终都是这四个步骤，只是不同的方式去实现这几个过程