> For the complete documentation index, see [llms.txt](https://deploydocs.coronasafe.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://deploydocs.coronasafe.network/awsecr.md).

# Build and push docker image

Our EKS deployment consists of running containers with docker images of the care project. The images will be served from a private container registry service provided by AWS called Elastic Container Registry (ECR). To setup the repositories for your care frontend and backend images, head over to AWS ECR console and create a new repository **each** for the backend and frontend.

## Build image

To build the docker image of the care project, first clone the repositories:

`$ git clone https://github.com/coronasafe/care`\
`$ git clone https://github.com/coronasafe/care_fe`

Inside the directory of the project you want to build, use the docker build command for building your required images.

Eg.: If you are in the backend folder, run `$ docker build -t care:latest .`

After the creation of the image, you can verify it by running `$ docker images`

The following branches are used for dev and production

**Care Backend ( care )** : 

master -> Development Branch

production -> Stable Production Branch

**Care Fron End ( care\_fe )** 

develop -> Development Branch

master -> Stable Production Branch

**Always use stable production builds in production, Keep the fork in sync every 3 days.**

**Always merge the development branch and test before merging production.**

## Push the image to AWS ECR

* Visit the ECR console.
* Select the repository you want to push your image to.
* On the top right corner, you should be able to find `View push commands`
* Follow the steps there to push your docker image to AWS ECR.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://deploydocs.coronasafe.network/awsecr.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.