Location>code7788 >text

Net 5.0 WebAPI Released for Linux Systems

Popularity：615 ℃/2024-08-30 23:43:35

X. Preamble

This article describes the process of deploying a WebAPI project on CentOS 7.

net 5.0 environment, then create a sample project and publish it to CentOS with some notes, and finally add the dotnet command to the system's self-starting services.

I. Linux environment preparation

1.1 centos online installation of .net 5.0

The first line of command is to add the package source and the second line of command is to install the .Net Core version of the package
First, configure the repository:
sudo rpm -Uvh /config/centos/7/
Then, execute the install command, one or the other:

sudo yum install dotnet-sdk-5.0 -y
sudo dnf install dotnet-runtime-5.0 -y
# When you use the dnf command, you will get the error [sudo: dnf: command not found].
# This error indicates that you do not have the dnf package manager installed on your system, you can install dnf support manually: sudo yum install dnf

1.2 CentOS Online Installation of .net 5.0

Direct execution commands:
sudo dnf install dotnet-sdk-5.0

1.3 Check if the installation was successful

View the current version: dotnet --version;
See details: dotnet --info.

[root@localhost ~]# dotnet --info
.NET SDK (reflecting any ):
 Version:   5.0.408
 Commit:    da985e2a23

Runtime Environment:
 OS Name:     centos
 OS Version:  7
 OS Platform: Linux
 RID:         centos.7-x64
 Base Path:   /usr/share/dotnet/sdk/5.0.408/

Host (useful for support):
  Version: 5.0.17
  Commit:  6a98414363

.NET SDKs installed:
  5.0.408 [/usr/share/dotnet/sdk]

.NET runtimes installed:
   5.0.17 [/usr/share/dotnet/shared/]
   5.0.17 [/usr/share/dotnet/shared/]

To install additional .NET runtimes or SDKs:
  /dotnet-download
[root@localhost ~]#

II. Sample Project Creation and Release

2.1 Create a test project

Simply create a test project below:.

option (Enable OpenAPI support) is checked to add support for the swagger framework by default.

Run it straight away and see the target effect:

http://localhost:58268/swagger/

http://localhost:58268/WeatherForecast

2.2 Publishing steps

Select Publish to File System:

Then find the distribution folder: (you need to upload all the files in this folder to the CentOS server)

\bin\Release\net5.0\publish

Upload it to the /home/ folder on CentOS. (The upload method is omitted)）

Third, the service opens and configures the self-start

3.1 Service Enablement

First, put Swagger's configuration in the file:

public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
    if (())
    {
        ();
    }
    // The following two lines, which were inside the if, are placed outside so that Swagger can be loaded regardless of the environment
    (); ("c => ("/swagger/vt"))
    (c => ("/swagger/v1/", " v1"));;

    ().

    ();

    (endpoints =>
    {
        ();
    });
}

Also, file , note the two configuration items in the following remarks:

{
  "$schema": "/",
  "iisSettings": {
    "windowsAuthentication": false,
    "anonymousAuthentication": true,
    "iisExpress": {
      "applicationUrl": "http://localhost:25863",
      "sslPort": 0
    }
  },
  "profiles": {
    "IIS Express": {
      "commandName": "IISExpress",
      "launchBrowser": true,
      "launchUrl": "swagger",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development"
      }
    },
    "": {
      "commandName": "Project",
      "dotnetRunMessages": "true",
      "launchBrowser": true,
      // Configuring Path Parameters，typical example：http://localhost:5000/swagger
      // The path to be added to the swagger access only
      "launchUrl": "swagger",
      "applicationUrl": "http://localhost:5000",
      "environmentVariables": {
        // Environment Variable Configuration，When the service starts，The corresponding environment variables must be added"Development"
        "ASPNETCORE_ENVIRONMENT": "Development"
      }
    }
  }
}

Try opening the service directly using the dotnet command:

 dotnet /home// - "http://*:5000" --environment Development

3.2 Configure the service as a system self-starter

Under the /etc/systemd/system/ path, add a new file with the following contents:

# Unit file description, webapi is the service filename
[Unit]
Description= service

# Service configuration parameters
[Unit] Description= service # Service configuration parameters
Type=simple
GuessMainPID=true

# Path to the location of the self-starting project
WorkingDirectory=/home/
StandardOutput=journal
StandardError=journal

# Commands to start the project
# Start the project with dotnet, so add the dotnet path /usr/bin/ followed by the configuration parameters for the dotnet commands
ExecStart=/usr/bin/dotnet /home// --Urls=http://*:5000
Restart=always
RestartSec=30

[Install]
WantedBy=

Commands related to operation services:

# Start
systemctl start
# View current status
systemctl status
# Restart
systemctl restart
# View all started services
systemctl list-units --type=service

# Set up a bootloader
systemctl enable
# Disable bootup
systemctl disable

Finally, you can execute the reboot command to verify the service after restarting the server.

Reference:https://blog./u_15050718/4565015   /u010476739/article/details/116710199     /Dominic_W/article/details/133277301                        

<Previous Next>