Apps only configuring a private repository

You can configure the Edge Gateway to use your private repository as the app repository.

This procedure applies only when the Edge Gateway system is not in an air gap environment. The procedure to configure an air gap private repository are included in the air gap installation procedures.

On the Edge Gateway system, add the private repository self-signed cert (domain.crt) to the trust certificates:
```
cp <path_to_certificate> /etc/pki/ca-trust/source/anchors &&
update-ca-trust extract
```
Note: if it is a certificate chain, add the root certificate to trusted certificates.
If the private repository DNS name cannot be resolved, add the domain to /etc/hosts:
```
192.168.xxx.1 <registry_domain_name>
```
Configure the Edge Gateway registry to use the private repository. You need to enter the URL to the repository, also called a registry. If the private repository requires authentication, use the --user option to enter the account user name, and you are prompted for the password.
```
manageAppHost registry --registry <registry_domain_name> --user <username>
```

If you want to mirror the Orchestration & Automation apps in the quay.io repository, see Apps only mirroring quay.io repository.

After you populate your repository, you can add apps from the Apps tab in the Orchestration & Automation application.

Note: If you later want to reconfigure your Edge Gateway to use the public repository, enter the following command:

manageAppHost registry --registry=quay.io