The Cloud Portal platform deploys the customer-facing LGF portal as a bench. It provides a purchase/catalog experience, host onboarding, and bench provisioning automation.

Deployment

  1. Select Cloud Portal from the platform dropdown.
  2. Enter a Bench Name.
  3. (Optional) Set the Listen Port.
  4. (Optional) Set Listen Protocol (HTTP/HTTPS) for the public hostname.
  5. (Optional) Set URL (host-only) if you want an explicit hostname.
  6. (Optional) Configure Reverse Proxy if you are placing the portal behind an external ingress.
  7. Click Create Bench.

Standard Fields

  • Bench Name: Unique identifier for the deployment.
  • Listen Port: External listener port (auto-allocated if not set).
  • URL: Host-only URL (no scheme, path, or port). Used for host routing and metadata.

Advanced Options

  • Listen Protocol: Public protocol for the bench hostname. When set to HTTPS and Let's Encrypt is enabled on the host, the system will attempt to issue a certificate for the bench hostname.
  • Reverse Proxy: Optional external ingress URL (if set, the bench is expected to be accessed via that URL).
  • Raw Port Access: Security-sensitive. Avoid unless you have a specific need.
  • OC Cloud API Base URL / Token: Optional at install time. Typically configured inside the portal after deployment.

Expected Result

  • The bench deploys and becomes reachable via the configured endpoint (port or hostname).
  • Portal setup can be completed from the UI (OIDC, RBAC, hosts, catalog).

Important Notes

  • If you want hostname-based access, configure RP_BASE_DOMAIN on the host and ensure DNS points to the host.
  • HTTPS requires a resolvable hostname and working HTTP-01 reachability (port 80) when using Let's Encrypt.