AppHarbor supports lib and src style folder structures

I’m currently using AppHarbor on a small freelance piece of work and I must say I’m seriously impressed, all the usual things are making me happy, the simplicity of pushing code from a Git repothe execution of tests and pushing of code live (i.e. continuous integration in the cloud) and not to mention the support for SQL Server and MySQL.

This is hopefully the first of a few posts about my recent experiences  with www.appharbor.com, as their tagline says “Azure done right”.

I’m currently using AppHarbor on a small freelance piece of work and I must say I’m seriously impressed, all the usual things are making me happy, the simplicity of pushing code from a Git repothe execution of tests and pushing of code live (i.e. continuous integration in the cloud) and not to mention the support for SQL Server and MySQL.

However the thing that impressed me recently was the way it all “just works”, after starting with a basic “Hello World” app I decided to restructure my source control tree and start pushing some more serious code up.  I changed from a simple single solution folder to some thing more akin to how I like to structure my projects:

Post1-AppHarborFolderStructure

As you can see I have nice ‘lib’ and ‘src’ folders, now the AppHarbor getting started guide states that you need to create your Git repository in the ‘pathtomyapplication’.  As you can see above this isn’t the case in my example above, my repo is created right up in the ‘~DevelopmentAYH.CHP’ folder, the .sln file for the solution is down in ‘DevelopmentAYH.CHPtrunksrc’.  I was unsure whether this was going to work, but pressed on and ran:

[code language=”bash”]$ git push appharbor master[/code]

Much to my delight AppHarbor didn’t sniff, it simply enumerated my repo and found the one and only .sln file and built it, see the latest successful build here:

Post1-AppHarborBuild

So don’t be scared of trying something different, the guys at www.appharbor.com seem to have most things covered.