https://github.com/getdutchie/webpack-monorepo-buildpack
https://github.com/getdutchie/webpack-monorepo-buildpack
Last synced: 8 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/getdutchie/webpack-monorepo-buildpack
- Owner: GetDutchie
- Created: 2019-10-04T17:05:33.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2021-04-19T22:11:40.000Z (about 5 years ago)
- Last Synced: 2023-03-02T23:26:23.961Z (over 3 years ago)
- Language: Shell
- Size: 10.7 KB
- Stars: 0
- Watchers: 44
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# 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](https://github.com/heroku/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 https://github.com/lstoll/heroku-buildpack-monorepo`
4. For each app, `git push git@heroku.com: 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 and Cyril David and now Lincoln Stoll