Offline & Air-Gapped

Vender Components is built for closed networks. Because the installer mirrors the entire catalog into your own registry, pipelines never need to reach the public internet.

Enabling offline mode

Set VENDER_OFFLINE to true to guarantee that no component attempts network egress:

variables:
  VENDER_OFFLINE: "true"

In offline mode, any component that would make an external call fails fast at creation time instead of hanging in an air-gapped runner.

Mirroring the catalog

The installer handles mirroring for you, but you can refresh the mirror at any time:

sh install.sh --refresh --path 'common/'

This re-pulls every component, workflow, and template into your registry under the path you chose during installation.

Recommended topology

For air-gapped environments we recommend a dedicated mirror project:

1. Create a common/ group in your internal GitLab.
2. Run the installer pointing Vender Path at that group.
3. Reference components by your internal FQDN in every pipeline.

Air-gapped teams run the full catalog with zero outbound connectivity — the same components, hardened the same way, entirely behind your firewall.

Verifying an offline install

Run the built-in doctor command to confirm every asset resolves locally:

sh install.sh --doctor

A healthy install reports 0 unresolved references.