前幾天部署了一個網站,原來我一直是發佈完成之後,通過ftp把文件上傳上去,有幾個大佬給我說了多階段構建,此時我就不需要發佈再搞了,直接將項目添加docker支持。 #See https://aka.ms/containerfastmode to understand how Visual Studi ...
前幾天部署了一個網站,原來我一直是發佈完成之後,通過ftp把文件上傳上去,有幾個大佬給我說了多階段構建,此時我就不需要發佈再搞了,直接將項目添加docker支持。
#See https://aka.ms/containerfastmode to understand how Visual Studio uses this Dockerfile to build your images for faster debugging. FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-buster-slim AS base WORKDIR /app EXPOSE 80 FROM mcr.microsoft.com/dotnet/core/sdk:3.1-buster AS build WORKDIR /src COPY ["amusinghoS.App/amusinghoS.App.csproj", "amusinghoS.App/"] COPY ["amusinghoS.Entity/amusinghoS.EntityData.csproj", "amusinghoS.Entity/"] COPY ["amusinghoS.Shared/amusinghoS.Shared.csproj", "amusinghoS.Shared/"] COPY ["amusinghoS.Services/amusinghoS.Services.csproj", "amusinghoS.Services/"] COPY ["amusinghoS.Redis/amusinghoS.Redis.csproj", "amusinghoS.Redis/"] RUN dotnet restore "amusinghoS.App/amusinghoS.App.csproj" COPY . . WORKDIR "/src/amusinghoS.App" RUN dotnet build "amusinghoS.App.csproj" -c Release -o /app/build FROM build AS publish RUN dotnet publish "amusinghoS.App.csproj" -c Release -o /app/publish FROM base AS final WORKDIR /app COPY --from=publish /app/publish . ENTRYPOINT ["dotnet", "amusinghoS.App.dll"]
其中最重要的就是那幾個COPY ,只要是和你這個項目有依賴的,統統打包,構建成一個鏡像。
然後就是Nginx了,配置文件如下。那個埠對準1314的埠必須是docker的外網埠!
worker_processes 1; events { worker_connections 1024; } http { include mime.types; default_type application/octet-stream; sendfile on; keepalive_timeout 65; server { listen 80; server_name localhost; error_page 500 502 503 504 /50x.html; location / { proxy_pass http://39.104.53.29:1314; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection keep-alive; proxy_set_header Host $http_host; proxy_cache_bypass $http_upgrade; } } }
此時訪問39.104.53.29 就可以訪問到docker對外開放的1314 對內5001的網站了。