Configuration

Qpoint Proxy offers two flexible management approaches, catering to different deployment needs and preferences: through a local YAML configuration or via the cloud control plane. Both methods are supported for all installations.

Local

This method utilizes a local proxy-config.yaml file to configure the proxy settings directly on the container. This approach is beneficial for scenarios requiring precise, file-based configuration control, particularly when deploying in environments where direct file manipulation is feasible.

Docker Command:

docker run \
   -p 10080:10080 \  # MIDDLEWARE
   -p 10443:10443 \ 
   -p 18080:18080 \  # TRANSPARENT
   -p 18443:18443 \ 
   us-docker.pkg.dev/qpoint-edge/public/qpoint:head \
   proxy \
   --log-level=error \
   --qpoint-config ./proxy-config.yaml

Cloud Connected

Alternatively, the proxy can be managed remotely via the Qpoint cloud control plane. This option is ideal for users who prefer centralized management through a control plane API, offering ease of configuration and scalability across multiple proxies without the need to directly access each deployment.

Docker Command:

docker run \
   -p 10080:10080 \  # MIDDLEWARE
   -p 10443:10443 \ 
   -p 18080:18080 \  # TRANSPARENT
   -p 18443:18443 \ 
   us-docker.pkg.dev/qpoint-edge/public/qpoint:head \
   proxy \
   --log-level=error \
   --registration-token=$TOKEN