ASP. NET Core "full release, comes with runtime" to Jexus

First, before reading the notice

1. This article belongs to the "full release", published without Visual Studio2015 Update3, and comes with the release process of the runtime

2. You do not need to install the. Net Core SDK under Linux

3.jexus version: 5.8.2

4. Server: centos7.1

Second, manual release steps

1. Create a new ASP. NET core application using VisualStudio2015 Update3

2. Locate the "Project.json" in the project root directory

2.1 Disable "type"

2.2 Note "Scripts" node

2.3 Add "runtimes" node, centos7.1 server

2.4 cmd into the engineering root directory

CD/D Project Catalogue

2.5 Restore Package

dotnet Restore

2.6 Release

dotnet publish-r CentOS. 7-x64

2.7 Previewing a catalog after manual publishing

\bin\debug\netcoreapp1. 0\centos. 7-x64\publish

2.8 Test run self-host work condition

cd/var/www/defaultdotnet CoreApp.dll

Third, integrated into the Jexus site, as the Jexus process background run

Tell me why:
The advantages of using Jexus to consolidate ASP. NET Core:
1) Support multi-site, the same port can support any number of ASP.
2) application start, stop, restart and site start, stop, restart and other operations consistent, no need to manually manage the ASP.
3) with application crash after automatic restart function, for enterprise-class uninterrupted operation protection;
4) has a higher performance advantage than the reverse proxy.

5) Provide the same HTTP environment parameters as IIS.

3.1 Installing jexus5.8.2

CD/tmpwget linuxdot.net/down/jexus-5.8. 2-x64. Tar . GZ tar zxvf jexus-5.8. 2-x64. Tar . GZCD Jexus/CD siteconf/VI Default

3.2 Adding AppHost

(Jexus author introduces apphost)

The configuration format for Apphost is:
apphost={cmdline= application command line; approot= Application working directory; port= application HTTP Listening port}, where:
"CmdLine" means the command line that launches the application, such as: Dotnet/var/www/site1/app.dll;
"AppRoot" indicates the application working directory, such as:/var/www/site1;
"Port" indicates the listening port used by this HTTP application, such as: Asp.core (the default port is 5000).

3.3 Copy the published program to the server (\BIN\DEBUG\NETCOREAPP1. 0\centos.7-x64\publish\), I'm using WINSCP.

3.4 Configure execution permissions (emphasis)

cd/var/www/chmod a+x Coreapp
Ls

After authorization:

3.5 Start Jexus

Cd.. /. /jws start

3.6 Observing the ASP. NET Core Port condition

sudo netstat-lntp

3.7 The release to this one with runtime is complete, the test is OK (Access port: 80, forwarded by Jexus completion port to 5000)

Iv. Exchange of Learning

. NET Core & Owin AC Group: 199281001

linuxdot.net AC Group: 102732979

ASP. NET Core "full release, comes with runtime" to Jexus