Open evgenyb opened 10 years ago
Octopus Deploy has chosen to host it as a Windows Service. The main benefit with this is that the user don't have to have IIS on his machine. I think it's more flexible. There are some edge-cases that we might get into if we try to install it into IIS. E.g. special top-level configuration. The same might be a disadvantage in some cases. I'm guessing special certificate rules for hosting on HTTPS. Not sure what dangers lurks out there...
To answer the questions:
Agree! We will focus on Windows Service hosted version first.
Here are some links that I found. Not sure how relevant they are (2 years old), but at least some analyses was done... http://www.tugberkugurlu.com/archive/why-am-i-not-using-nancyfx-instead-of-asp-net-mvc-web-api http://blog.jonathanchannon.com/2012/12/19/why-use-nancyfx/
If you haven't started yet, tonight I will branch out and will try to implement the same api call-stack with Katana.
As I see it there are 2 possible ways how user can install Configuratron to his environment.
Both Nancy and Katana can be hosted as self-hosted windows service (for instance with TopShelf) or hosted under IIS.
Technically it's possible to organise projects like
where core.api will contain either apicontrollers or nancy modules and *.host projects will be a placeholders for core.api + infrastructure code.
So I want to challenge us with the following 2 questions: