HomeInstallPrepare prerequisitesMirror the Coder Registry with JFrog Artifactory

Mirror the Coder Registry with JFrog Artifactory

On this page

This guide shows you how to use JFrog Artifactory to mirror the Coder Registry for air-gapped or restricted network deployments.

By configuring Artifactory as a Remote Terraform Repository, you can:

Proxy and cache all Coder modules automatically
Keep modules updated without manual synchronization
Support offline access once modules are cached

Prerequisites

JFrog Artifactory instance (Cloud or self-hosted)
Admin access to create repositories
Artifactory user token for Terraform authentication

Step 1: Create the Remote Terraform Repository

In Artifactory, go to Administration > Repositories > Remote
Select New Remote Repository and select Terraform as the package type
Configure the repository with these settings:

Setting Value
Repository Key coder-registry
URL https://registry.coder.com
Terraform Registry URL https://registry.coder.com
Select Create Remote Repository

Setting	Value
Repository Key	`coder-registry`
URL	`https://registry.coder.com`
Terraform Registry URL	`https://registry.coder.com`

Step 2: Verify the Repository Configuration

Test that Artifactory can proxy the Coder registry by querying the module versions API:

curl -u '<username>:<token>' \
  'https://<your-artifactory-host>/artifactory/api/terraform/coder-registry/v1/modules/coder/code-server/coder/versions'

You should see a JSON response listing all available versions of the code-server module.

Step 3: Configure Terraform CLI

Create or update your Terraform CLI configuration file to use Artifactory.

On Linux/macOS, create ~/.terraformrc. On Windows, create %APPDATA%\terraform.rc.

host "<your-artifactory-host>" {
  services = {
    "modules.v1" = "https://<your-artifactory-host>/artifactory/api/terraform/coder-registry/v1/modules/"
  }
}

credentials "<your-artifactory-host>" {
  token = "<your-artifactory-token>"
}

Replace:

<your-artifactory-host> with your Artifactory hostname (e.g., artifactory.example.com or mycompany.jfrog.io)
<your-artifactory-token> with your Artifactory access token with read permissions to the coder-registry repository

Note

The host block with services is required because Artifactory's global service discovery endpoint doesn't include the repository name in the modules path. This explicitly tells Terraform where to find modules in your specific repository.

Step 4: Update Template Module Sources

Update your Coder templates to use Artifactory instead of the public registry:

# Before: Direct from Coder registry
module "code-server" {
  source   = "registry.coder.com/coder/code-server/coder"
  version  = "1.4.2"
  agent_id = coder_agent.main.id
}

# After: Through Artifactory mirror
module "code-server" {
  source   = "https://<your-artifactory-host>/coder/code-server/coder"
  version  = "1.4.2"
  agent_id = coder_agent.main.id
}

Step 5: Configure the control plane or provisioners

For Coder to use the Artifactory mirror, configure the Terraform CLI on your control plane or external provisioners.

Create a secret with the Terraform configuration:

kubectl create secret generic terraform-config \
  --from-file=.terraformrc=./terraformrc \
  -n coder

Update your Helm values:

coder:
  volumes:
    - name: terraform-config
      secret:
        secretName: terraform-config
  volumeMounts:
    - name: terraform-config
      mountPath: /home/coder/.terraformrc
      subPath: .terraformrc
      readOnly: true
  env:
    - name: TF_CLI_CONFIG_FILE
      value: /home/coder/.terraformrc

Step 6: Point the template builder at your mirror

The template builder resolves module sources against registry.coder.com by default. To make it generate module source paths that point at your Artifactory mirror instead, set the CODER_TEMPLATE_BUILDER_REGISTRY_URL environment variable on your control plane:

CODER_TEMPLATE_BUILDER_REGISTRY_URL=<your-artifactory-host>

The value is a bare host, optionally with a port (for example, artifactory.example.com or mycompany.jfrog.io:8443). A leading http(s):// scheme and trailing slash are stripped, and a path, query, fragment, or credentials is rejected at server start.

Without this variable, the template builder still requires outbound access to registry.coder.com. For fully air-gapped deployments that cannot set a mirror, disable the builder instead with CODER_DISABLE_TEMPLATE_BUILDER=true. See Air-gapped Deployments for details.

Caching Behavior

Artifactory uses lazy caching, meaning modules are cached on first request. For fully air-gapped deployments, pre-warm the cache while connected to the internet:

Create a test template that references all modules you need
Run terraform init to trigger downloads
Verify modules appear in Artifactory under coder-registry-cache

Once cached, modules remain available even without internet connectivity.

Supported Namespaces

The Artifactory mirror supports all namespaces from the Coder registry:

Namespace	Description	Example Module
`coder`	Official Coder modules	`code-server`, `jetbrains-gateway`
`coder-labs`	Experimental modules	`cursor-cli`, `copilot`
Community	Third-party contributions	Various

All modules use the same source format:

source = "<your-artifactory-host>/<namespace>/<module>/coder"

Troubleshooting

Module not found errors

Verify your .terraformrc includes both the host block with services and the credentials block. The host.services configuration is required for Artifactory.

401 Unauthorized errors

Check that your Artifactory token is valid and has read access to the coder-registry repository.

Modules not caching

Ensure the remote repository URL is set to https://registry.coder.com and not other paths.

Next Steps

Air-gapped deployments

Run Coder in air-gapped, disconnected, or offline environments where all features remain supported.