Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IIS Examples #89

Open
rhys-intelliflo opened this issue Feb 21, 2018 · 6 comments
Open

IIS Examples #89

rhys-intelliflo opened this issue Feb 21, 2018 · 6 comments

Comments

@rhys-intelliflo
Copy link

Is there any documentation or a walk through to configuring IIS to host tug specifically?

@FLeven
Copy link

FLeven commented 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
Copy link
Author

+1 for a dockerfile

@affieuk
Copy link

affieuk commented 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\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.

@rhys-intelliflo
Copy link
Author

Thanks @affieuk will give this a go

@ebekker
Copy link
Collaborator

ebekker commented 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
Copy link

FLeven commented 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 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants