main
is created, Release will select RepoB develop
and RepoC bug-1
because those are the default and tracking branch, respectively.feature-1
is created, Release will select RepoB develop
and RepoC feature-1
because those are the default and matching heuristic branch, respectively.feature-2
is created, Release will select RepoB feature-2
and RepoC bug-1
because those are the matching heuristic branch and tracking branch respectively.rails_postgres_redis
repository.api
service has options for STATIC
(because a package.json) was found or DOCKER
(because a Dockerfile was found). Since this is a Rails server, we'll pick docker.GENERATE APP TEMPLATE
button to move onto the next screen.docker-create-react-app
repository.app
that will be our frontend. This repository is configured to run in Docker (was the name a give away?) so we'll again select DOCKER
.GENERATE APP TEMPLATE
button to move onto the next screen.frontend
application, we want to also import the backend
application as well. We'll click SAVE & CONTINUE
and move on to adding an environment variable to ensure the two applications can talk to each other.<SERVICE_NAME>_INGRESS_URL
when the service is exposed to the internet. Remember we selected DOCKER
for our api
service when we created the backend
application and it was exposed on public port 443. This means we'll have an environment variable named API_INGRESS_URL
. When using App Imports, the ingress environment variables for backend
are shared with frontend
. What we need to do is add a mapping from API_INGRESS_URL
to the correct environment variable on the frontend. The environment variable we need to map to is REACT_APP_BACKEND_API
which can be found in the api.js file of the repository.Edit
button in the Default Environment Variables section.frontend
application will receive the value of API_INGRESS_URL
as the environment variable REACT_APP_BACKEND_API
. Click Save
to close the Default Environment Variables
modal and then the START BUILD & DEPLOY
button.Deploy 3345
we'll be taken to the Deploy page to see the progress.backend
application and two are for the frontend
application. This is great news! Our App Import worked and has been successfully deployed.GO TO ENVIRONMENT
button so we can view the URLs and ensure that the frontend
can talk to the backend
.backend
application is shown in the Namespace
section and the URL for our frontend
application is in the Hostname URLs
section. Clicking on the app
link takes us to our live Release environment.Create New Users
button to trigger a background job (utilizing Sidekiq and Redis) to create them. After a short wait, the API to retrieve the users is called again.