Configuring a private repository

You can configure the App Host to use your private repository as the app repository.

This procedure applies only when the App Host 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.

Log in with an account that has sudo and perform the following:
  1. At the App Host system, add the private repository self-signed cert (domain.crt) to the trust certificates. 
    cp <cert_file> /etc/pki/ca-trust/source/anchors
update-ca-trust extract

    If it is a certificate chain, add the root certificate to trusted certs.

  2. If the private repository DNS name cannot be resolved, add the domain to /etc/hosts:
    192.168.xxx.1 <registry_dns_name>
  3. Configure the App Host 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 username; you are prompted for the password.
    manageAppHost registry --registry <registry_URL> --user <username>

If you wish to mirror the apps in the quay.io repository, see Mirroring quay.io repository.

When you populate your repository, you can add apps from the Apps tab in the SOAR Platform.

If at a later time, you want to reconfigure your App Host to use the public repository, enter the following command:
manageAppHost registry --registry=quay.io