GalaxyGate Docs

Appearance

Registry credentials ​

Some Apps run from a private container image, and the panel needs a login to pull it. A registry credential is the username and password or token we use to authenticate to a private container registry, fetch the image, and deploy your App. Public images need no credential.

Open the page from Security in the sidebar, then Registries. It lives at the /apps/credentials route.

Add a credential ​

Select New credential on the list page. This navigates to a dedicated New Registry Credential page, not a popup, with Save and Cancel buttons at the bottom. Fill in the login for your registry:

  • Registry. A dropdown where you pick the registry. The choices are Docker Hub (docker.io), GitHub Container Registry (ghcr.io), GitLab Container Registry, and Custom.... For the presets, the host is filled in for you and cannot be edited.
  • Registry host. A free-text field that appears only when you choose Custom... in the dropdown. Enter the host of your private registry here.
  • Username. The account the panel authenticates as.
  • Password / token. The secret that account uses. The field accepts either a password or a token. A scoped token with read access to the images is safer than a full password.

When you are done, select Save to store the credential, or Cancel to go back without saving.

The Registry Credentials page with the New credential button circled
Add a credential from Security then Registries (New credential, circled).

Before you add anything ​

With no credentials saved, the page shows an empty state reading No registry credentials configured. That is expected on a new workspace. Your first credential appears in the list once added.

Use a scoped, read-only token

Give the panel a token that can only read the images it needs to pull. It never needs to push, and a read-only token limits the damage if the credential is ever exposed.

Manage a saved credential ​

Each credential in the list has three actions:

  • Test validates the stored credentials against the registry, so you can confirm they still work.
  • Edit opens the credential so you can update its details.
  • Delete removes the credential from your workspace.

Where these get used ​

Saved credentials are used when you deploy an App that pulls a private image. If no matching credential exists, the pull fails and the deployment does not start, so add the credential first.

Install an app on a server