Learn how to setup Ergomake if you need to spin-up previews with multiple repos
frontend
repository which sends requests to a backend
repository.
In that case, if you want your pull-requests on the frontend
repository to include an instance of the backend
application, you can reference it on your compose as if it was in an external folder, as shown in the example below.
.ergomake
folder, every pull-request in the frontend
repository will build the Dockerfile
in the backend
repository and include it in your preview environment.
If you want your back-end repository to include the frontend
repository, you’ll have to commit a similar compose file to the backend
repository. This time, however, you’ll refer to the frontend
repo as an external folder, as shown below
main
, if an eponymous branch does not exist.
my-feature
. If those changes depend on changes from the back-end which haven’t yet been merged, you can push a branch called my-feature
to your back-end repository too.
Then, when you open your front-end pull-request, the preview environment will use the back-end changes from my-feature
instead of main
.