Just as the previous chapter we’ll add the API repo on Seed and deploy it to our environments.

Click Add an App again, and select your Git provider. This time, select the API repo.

Select Add an App in Seed

Select the notes-api service from the list of services.

Select serverless service to add

The environments for our API repo are identical to our resources repo. So instead of manually configuring them, we’ll copy the settings.

Select Copy Settings tab, and select the resources app. Then hit Add a New App.

Set app settings from resources

The API app has been created. Now, let’s add the other services. Head over to the Pipeline tab.

Create an App in Seed

Click Add a service to add the billing-api service at the services/billing-api path. And then repeat the step to add the notify-job service at the services/notify-job path.

Added all services in Seed

Next, click on Manage Deploy Phases.

Hit Manage Deploy Phases screenshot

Again you’ll notice that by default all the services are deployed concurrently.

Default Deploy Phase screenshot

Since the billing-api service depends on the notes-api service, and in turn the notify-job service depends on the billing-api service, we are going too add 2 phases. And move the billing-api service to Phase 2, and the notify-job service to Phase 3. Finally, click Update Phases.

Edit Deploy Phase screenshot

Now let’s make our first deployment.

Show services are deploying in dev stage

You can see the deployments were carried out according to the specified deploy phases.

Just as before, promote dev to prod.

Select Promote in dev stage

Hit Promote to Production.

Promote dev stage to prod stage

Now we have the API deployed to both dev and prod.

Show services are deployed in prod stage

Now that our entire app has been deployed, let’s look at how we are sharing environment specific configs across our services.