heroku-buildpack-monorepo

by envato

GitHub Readme.md

This is a fork of an existing builpack. This buildpack has been forked to ensure that we can have better understanding and control over what the buildpack accesses, and what operations it performs, specifically around accessing the environment directory. We decided to fork the buildpack rather than point at a specific sha to ensure that the buildpack is still available in the case of the target repository being removed.


Heroku Multi Procfile buildpack

Imagine you have a single code base, which has a few different applications within it... or at least the ability to run a few different applications. Or, maybe you're Google with your mono repo?

In any case, how do you manage this on Heroku? You don't. Heroku applications assume one repo to one application.

Enter the Monorepo buildpack, which is a copy of heroku-buildpack-multi-procfile except it moves the target path in to the root, rather than just the Procfile. This helps for ruby apps etc.

Usage

  1. Write a bunch of Procfiles apps and scatter them through out your code base.
  2. Create a bunch of Heroku apps.
  3. For each app, set APP_BASE=relative/path/to/app/root, and of course: heroku buildpacks:add -a <app> https://github.com/lstoll/heroku-buildpack-monorepo
  4. For each app, git push git@heroku.com:<app> master

Note: If you already have other buildpacks defined, you'll need to make sure that the heroku-buildpack-monorepo buildpack is defined first. You can do this by adding -i 1 to the heroku buildpacks:add command.

Authors

Andrew Gwozdziewycz apg@heroku.com and Cyril David cyx@heroku.com and now Lincoln Stoll lstoll@heroku.com