8

We have a solution with this structure.

  • OurApp.Web (mvc 3 project with controllers, views)
  • OurApp.Api (mvc 3 project with wcf web api service classes)
  • OurApp.Domain (entities, repositories, unit of work, etc)
  • OurApp.Tests (tests)

We want to use a dns structured like this:

http://www.ourapp.com points to OurApp.Web

http://api.ourapp.com points to OurApp.Api

We want to host on AppHarbor.

How can we do this?

Troels Thomsen
  • 11,361
  • 4
  • 28
  • 29
nacho10f
  • 5,816
  • 6
  • 42
  • 73

1 Answers1

12

AppHarbor currently only supports deploying one application from any given repository. One option might be to fold the API into the web project. I did this for a non-web API WCF service here.

Another option is to maintain two AppHarbor applications, and use solution files named according to what application you want deployed for that application. That is, OurApp.Web.sln contains the Web project and any supporting projects and, OurApp.Api.sln references the API project and any supporting projects. Read more about AppHarbor solution file convention.

(disclaimer, I'm co-founder of AppHarbor)

friism
  • 19,068
  • 5
  • 80
  • 116
  • 2
    +1 for looking for a solution file named as the application's slug (and the ".sln" suffix). Never knew that. Only knew about appharbor.sln. #LOVE – Korayem Mar 02 '12 at 20:04