You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is how I got it working, would like to have to confirmation on this:
Install IIS
Install the .Net Core hosting bundle: https://aka.ms/dotnetcore-2-windowshosting
Install Tug
Create a site in IIS and point it to C:\Program Files\Tug\Server
Change application pool to No Mananged Code
Copy the web.config files from C:\Program Files\Tug\Server\bin to C:\Program Files\Tug\Server
Modify line 7 from <aspNetCore processPath=".\Tug.Server.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" /> to <aspNetCore processPath=".\bin\Tug.Server.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
Test out Tug, haven't played with it further yet.
@affieuk directions reflect the current best practices for fronting ASP.NET Core app with IIS. This is true up to .NET Core 2.0.
Using the instructions above will install a bridging component that proxies from the IIS process to the Kestrel process that's actually hosting and running the Tug server (that's the hosting bundle).
In the upcoming .NET Core 2.1 release, there will be a second option that allows for in-process support, so IIS process will actually spin up a .NET Core runtime in-process. Early indications are that it will perform about 7x better.
Activity
FLeven commentedon Feb 21, 2018
Yes, I also feel a bit lost here. Some windows dockerfiles would be nice, this would ease the setup for a testrun.
rhys-intelliflo commentedon Feb 22, 2018
+1 for a dockerfile
affieuk commentedon Mar 14, 2018
This is how I got it working, would like to have to confirmation on this:
Install IIS
Install the .Net Core hosting bundle: https://aka.ms/dotnetcore-2-windowshosting
Install Tug
Create a site in IIS and point it to
C:\Program Files\Tug\ServerChange application pool to
No Mananged CodeCopy the web.config files from
C:\Program Files\Tug\Server\bintoC:\Program Files\Tug\ServerModify line 7 from
<aspNetCore processPath=".\Tug.Server.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />to<aspNetCore processPath=".\bin\Tug.Server.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />Test out Tug, haven't played with it further yet.
rhys-intelliflo commentedon Mar 14, 2018
Thanks @affieuk will give this a go
ebekker commentedon Mar 14, 2018
@affieuk directions reflect the current best practices for fronting ASP.NET Core app with IIS. This is true up to .NET Core 2.0.
Using the instructions above will install a bridging component that proxies from the IIS process to the Kestrel process that's actually hosting and running the Tug server (that's the hosting bundle).
In the upcoming .NET Core 2.1 release, there will be a second option that allows for in-process support, so IIS process will actually spin up a .NET Core runtime in-process. Early indications are that it will perform about 7x better.
FLeven commentedon Jun 24, 2018
Install the .Net Core -> 2.1.1 is available
Install Tug -> The PS5 Version, as outlined int he pre-release deployment HOWTO ?