docs: Add comprehensive air-gapped deployment guide

- Add detailed air-gapped deployment section to CONTRIBUTING.md
- Include three deployment options: Git repos, private registries, vendored modules
- Add air-gapped deployment note to README.md
- Expand examples with air-gapped usage patterns
- Document offline module support and requirements

Fixes air-gapped deployment documentation gaps for registry.coder.com

CONTRIBUTING.md

@@ -355,6 +355,103 @@ terraform test -verbose
 
 ---
 
+## Contributing
+
+---
+
+## Air-Gapped and Offline Deployments
+
+For customers deploying Coder in air-gapped or network-restricted environments without access to `registry.coder.com`, there are several approaches to use registry modules:
+
+### Option 1: Local Git Repository (Recommended)
+
+The most common approach is to mirror registry modules in an internal Git repository:
+
+1. **Download modules** from [registry.coder.com](https://registry.coder.com) while connected to the internet
+2. **Store modules** in your internal Git repository with the same directory structure:
+   ```
+   internal-registry/
+   ├── modules/
+   │   ├── code-server/
+   │   ├── cursor/
+   │   └── vscode-web/
+   └── templates/
+   ```
+3. **Reference modules** using Git source addresses in your templates:
+   ```tf
+   module "code_server" {
+     source   = "git::https://your-internal-git.com/coder-modules.git//modules/code-server"
+     version  = "1.0.19"  # Use Git tags for versioning
+     agent_id = coder_agent.example.id
+   }
+   ```
+
+### Option 2: Custom Terraform Registry
+
+Set up a private Terraform registry mirror:
+
+1. **Configure a private registry** (such as Terraform Enterprise or Artifactory)
+2. **Mirror modules** from the public registry to your private registry
+3. **Update templates** to use custom source addresses:
+   ```tf
+   module "code_server" {
+     source   = "your-registry.com/coder/code-server/coder"
+     version  = "1.0.19"
+     agent_id = coder_agent.example.id
+   }
+   ```
+4. **Configure `.tfrc`** file to point Terraform to your private registry
+
+### Option 3: Vendored Modules
+
+Include modules directly in your template repositories:
+
+1. **Download modules** and include them in your template repository
+2. **Reference with relative paths**:
+   ```tf
+   module "code_server" {
+     source   = "./modules/code-server"
+     agent_id = coder_agent.example.id
+   }
+   ```
+
+### Air-Gapped Requirements
+
+When deploying in air-gapped environments, ensure:
+
+- **Terraform binary** is included in PATH (cannot download from releases.hashicorp.com)
+- **Custom source addresses** are configured for all external dependencies
+- **Telemetry and update checks** are disabled:
+  ```bash
+  coder server --telemetry=false --update-check=false
+  ```
+- **External database** is configured (cannot download PostgreSQL from repo1.maven.org)
+
+### Module Offline Support
+
+Many registry modules support offline operation:
+
+```tf
+module "code_server" {
+  source   = "registry.coder.com/coder/code-server/coder"
+  version  = "1.0.19"
+  agent_id = coder_agent.example.id
+  offline  = true  # Prevents downloading from external sources
+}
+```
+
+Check individual module documentation for offline-specific configuration options.
+
+### Additional Resources
+
+- [Coder Offline Deployment Guide](https://coder.com/docs/install/offline)
+- [Terraform Module Sources](https://developer.hashicorp.com/terraform/language/modules/sources)
+- [Custom Terraform Registry Setup](https://developer.hashicorp.com/terraform/enterprise/registry)
+
+---
+
+## Contributing
+
 ## Submitting Changes
 
 1. **Fork and branch:**

README.md

@@ -23,6 +23,8 @@ More information [about Coder Modules can be found here](https://coder.com/docs/
 
 The easiest way to discover new modules and templates is by visiting [the official Coder Registry website](https://registry.coder.com/). The website is a full mirror of the Coder Registry repo, and it is where .tar versions of the various resources can be downloaded from, for use within your Coder deployment.
 
+> **Air-Gapped Deployments**: For customers in network-restricted environments, see our [air-gapped deployment guide](./CONTRIBUTING.md#air-gapped-and-offline-deployments) for options to use registry modules without internet access.
+
 Note that while Coder has a baseline set of requirements for allowing an external PR to be published, Coder cannot vouch for the validity or functionality of a resource until that resource has been flagged with the `verified` status. [All modules under the Coder namespace](https://github.com/coder/registry/tree/main/registry/coder) are automatically verified.
 
 ### Getting started with modules

examples/modules/README.md

@@ -69,3 +69,37 @@ module "MODULE_NAME" {
   offline  = true
 }
 ```
+
+### Example 4: Air-Gapped Deployment with Git Source
+
+For air-gapped environments, reference modules from internal Git repositories:
+
+```tf
+module "code_server" {
+  source   = "git::https://internal-git.company.com/coder-modules.git//modules/code-server?ref=v1.0.19"
+  agent_id = coder_agent.example.id
+  offline  = true  # Prevent external downloads
+}
+```
+
+### Example 5: Air-Gapped Deployment with Local Path
+
+Vendor modules directly in your template repository:
+
+```tf
+module "code_server" {
+  source   = "./modules/code-server"  # Relative path to vendored module
+  agent_id = coder_agent.example.id
+}
+```
+
+### Example 6: Private Registry
+
+Use a private Terraform registry for air-gapped deployments:
+
+```tf
+module "code_server" {
+  source   = "private-registry.company.com/coder/code-server/coder"
+  version  = "1.0.19"
+  agent_id = coder_agent.example.id
+}