Best practices for Heroku deploy if you have an actual build process?

Problem

I have a build process involving templating and file copying, which produces what I would like to deploy to Heroku.

But Heroku requires to push your source from a git repository.

What I currently see as my only option is to have a separate git repository, that only holds my build history. My project is a NodeJS server application.

Is there a better approach?

Thanks.

Problem courtesy of: Nikolay Tsenkov

Solution

I have create a grunt-init project template that simplifies the develop-build-deploy cycle of NodeJS server apps deployed on Heroku.

Here it is: https://github.com/nicroto/grunt-init-heroku

This will allow you to have a single repository for your server & client apps, AND do actual build work.

I am basically creating an ignored by git build dir, which I synch-up with your Heroku app. And of course scaffold the project with sample init, build and deploy scripts.

I hope this will be helpful to the community. :)

Solution courtesy of: Nikolay Tsenkov

Discussion

There is currently no discussion for this recipe.

This recipe can be found in it's original form on Stack Over Flow.