Detailed explanation of publishing ASP.NET Core program to Linux production environment

This article mainly introduces in detail the release of ASP.NET Core programs to the Linux production environment. It has certain reference value. Interested friends can refer to it.

In this article we will introduce how to deploy ASP.NET Core applications on Ubuntu 14.04 Server. We will put the ASP.NET Core application behind a reverse proxy server, which will forward requests to our Kestrel server. In addition to this, we will ensure that our web application is started as a daemon. We need to configure a process management tool to help us recover the program when it crashes to ensure high availability.

Chapter:

• Preparation

• Copy your application

• Configure a reverse proxy server

• Monitor our application

• Start our application

• Observation log

• Making our application secure
  

Preparation

1. Use a standard account with sudo permissions to access Ubuntu 14.04 Server;

2. ASP.NET Core application.

Copy your application

Run dotnet publishPackage your ASP.NET Core application into a Self-Contained directory (publish directory, the program in this directory will be uploaded to the server and run). What is a self-contained (Self-Contained) program? Please refer to my article:

.NET Core application types (Portable apps & Self-contained apps). Before operation, upload all programs in the publish directory to the directory specified by the server through FTP tools (WinSCP, etc.). Next we run our program. For details on how to run the program, please refer to this article: Create a Self-Contained console application using .NET Core 1.0.

Configure a reverse proxy server

For dynamic web applications, reverse proxy is a very common setting. The reverse proxy terminates the current request and forwards the request to the backend ASP.NET Core application.

Why use a reverse proxy server

Kestrel as a web server is very good at handling dynamic content, but it is not as mature as those of the web Servers are also fully functional, including: IIS, Apache or Nginx. The reverse proxy server can offload some work from the HTTP server, including static content processing, caching, compression, and SSL. The reverse proxy server can be deployed on a dedicated server or in the same cluster as the HTTP server. In this example we will use Nginx as the reverse proxy server and deploy it on the same machine as the HTTP server.

Install proxy server

sudo apt-get install nginx

Install Nginx

sudo service nginx start

Start Nginx

Configure Nginx

Edit file: /etc/nginx/sites -available/default is as follows:

server {
 listen 80;
 location / {
  proxy_pass http://localhost:5000;
  proxy_http_version 1.1;
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection keep-alive;
  proxy_set_header Host $host;
  proxy_cache_bypass $http_upgrade;
 }
}

Listens on port 80, the default port of HTTP; the HTTP version used by the proxy is: HTTP 1.1; the original request is forwarded to: http://localhost:5000.

After the above configuration is completed, use the following command to verify whether the configuration file syntax is correct:

sudo nginx -t

If the configuration syntax is not If there is a problem, restart Nginx to make the configuration take effect:

sudo nginx -s reload

Monitor our web application

Nginx will forward the request to your Kestrel server, But Kestrel is not like IIS on Windows, it does not manage your Kestrel process, in this article we We will use the supervisor to start our application and recover itself when the system starts or when the process crashes.

Install supervisor:

sudo apt-get install supervisor

Configure supervisor:

/etc/supervisor/ conf.d/hellomvc.conf (a new file)

[program:hellomvc]
command=/usr/bin/dotnet /var/aspnetcore/HelloMVC/HelloMVC.dll
directory=/var/aspnetcore/HelloMVC/
autostart=true
autorestart=true
stderr_logfile=/var/log/hellomvc.err.log
stdout_logfile=/var/log/hellomvc.out.log
environment=ASPNETCOREENVIRONMENT=Production
user=www-data
stopsignal=INT

Restart supervisord

sudo service supervisor stop
sudo service supervisor start

Start our web application

In this case, because we use supervisor to manage our application, the application will be automatically started by supervisor . When the operating system starts, the supervisor is started as a daemon using a System V initialization script. After the supervisor starts, it will start your application.

Observation log

supervisord log

sudo tail -f /var/log/supervisor/supervisord.log

Our own application log

tail -f /var/log/hellomvc.out.log

Original translation: Publish to a Linux Production Environment
Author: Sourabh Shirhatti

The above is the detailed content of Detailed explanation of publishing ASP.NET Core program to Linux production environment. For more information, please follow other related articles on the PHP Chinese website!