Basic environment configuration
Please purchase the domain name and server by yourself first
Create an application instance based on cloud server ecs, select the system image as ubuntu 16.04, and run it on this machine Connect remotely through ssh and perform related configurations
ssh
... sudo apt-get update sudp apt-get upgrade sudo apt-get autoremove sudo apt-get clean
Install and configure nginx
sudo apt-get install nginx sudo service nginx start sudo gedit /etc/nginx/sites-available/default
Configure the default file and configure the following node information at the end of the file
# virtual host configuration for example.com # # you can move that to a different file under sites-available/ and symlink that # to sites-enabled/ to enable it. # server { listen 80; # 网站文件的目标位置 root /home/hippie/website/wwwroot; # 网站域名 server_name your website name; 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; proxy_set_header x-forwarded-for $proxy_add_x_forwarded_for; proxy_set_header x-forwarded-proto $scheme; } }
Detect configuration and update
sudo nginx -t sudo nginx -s reload
Install dotnetcore
Please refer to the official website for the latest installation instructions: .netcore download
Deployment process
Open visualstudio2017, right-click the project to be published, click publish, and refer to the figure below for relevant configuration.
Click the save button and perform the publish operation. Then upload the publish folder to the corresponding location on the server. After the upload is successful, execute dotnet run app.dll
If nothing unexpected happens, at this time, you can use ip or Your website domain name is used for access.
Create a daemon process
After performing the above operations, our program still cannot run for a long time, so we need to manage our website through a daemon process
sudo apt-get install supervisor sudo vim /ect/supervisor/conf.d/website.conf
Configure website.conf file
[program:website] #要执行的命令 command=/usr/bin/dotnet attention.dll #命令执行的目录 directory=/home/hippie/website #环境变量 environment=aspnetcore__environment=production #进程执行的用户身份 user=www-data stopsignal=int #是否自动启动 autostart=true #是否自动重启 autorestart=true #自动重启间隔 startsecs=1 #标准错误日志 stderr_logfile=/var/log/website.err.log #标准输出日志 stdout_logfile=/var/log/website.out.log
At this time, we execute the following command to start the daemon process
sudo supervisorctl shutdown && sudo supervisord -c /etc/supervisor/supervisord.conf supervisorctl shutdown sudo service supervisor start
Okay, at this time you can try to close the remote connection for website access. If If you can access it normally, it means your configuration has taken effect.
The above is the detailed content of How to deploy DoNetCore to Alibaba Cloud with Nginx. For more information, please follow other related articles on the PHP Chinese website!

NGINXUnit can be used to deploy and manage applications in multiple languages. 1) Install NGINXUnit. 2) Configure it to run different types of applications such as Python and PHP. 3) Use its dynamic configuration function for application management. Through these steps, you can efficiently deploy and manage applications and improve project efficiency.

NGINX is more suitable for handling high concurrent connections, while Apache is more suitable for scenarios where complex configurations and module extensions are required. 1.NGINX is known for its high performance and low resource consumption, and is suitable for high concurrency. 2.Apache is known for its stability and rich module extensions, which are suitable for complex configuration needs.

NGINXUnit improves application flexibility and performance with its dynamic configuration and high-performance architecture. 1. Dynamic configuration allows the application configuration to be adjusted without restarting the server. 2. High performance is reflected in event-driven and non-blocking architectures and multi-process models, and can efficiently handle concurrent connections and utilize multi-core CPUs.

NGINX and Apache are both powerful web servers, each with unique advantages and disadvantages in terms of performance, scalability and efficiency. 1) NGINX performs well when handling static content and reverse proxying, suitable for high concurrency scenarios. 2) Apache performs better when processing dynamic content and is suitable for projects that require rich module support. The selection of a server should be decided based on project requirements and scenarios.

NGINX is suitable for handling high concurrent requests, while Apache is suitable for scenarios where complex configurations and functional extensions are required. 1.NGINX adopts an event-driven, non-blocking architecture, and is suitable for high concurrency environments. 2. Apache adopts process or thread model to provide a rich module ecosystem that is suitable for complex configuration needs.

NGINX can be used to improve website performance, security, and scalability. 1) As a reverse proxy and load balancer, NGINX can optimize back-end services and share traffic. 2) Through event-driven and asynchronous architecture, NGINX efficiently handles high concurrent connections. 3) Configuration files allow flexible definition of rules, such as static file service and load balancing. 4) Optimization suggestions include enabling Gzip compression, using cache and tuning the worker process.

NGINXUnit supports multiple programming languages and is implemented through modular design. 1. Loading language module: Load the corresponding module according to the configuration file. 2. Application startup: Execute application code when the calling language runs. 3. Request processing: forward the request to the application instance. 4. Response return: Return the processed response to the client.

NGINX and Apache have their own advantages and disadvantages and are suitable for different scenarios. 1.NGINX is suitable for high concurrency and low resource consumption scenarios. 2. Apache is suitable for scenarios where complex configurations and rich modules are required. By comparing their core features, performance differences, and best practices, you can help you choose the server software that best suits your needs.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

Dreamweaver CS6
Visual web development tools

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment