Infrastructure¶

All ObsidianPalace infrastructure is managed by Terraform, following the directories-over-workspaces pattern. State is stored in Terraform Cloud.

Directory Structure¶

terraform/
├── environments/
│   └── prod/
│       ├── versions.tf     # Terraform Cloud backend, provider versions
│       ├── provider.tf     # Google provider configuration
│       ├── variables.tf    # Root variables (pass-through to module)
│       ├── main.tf         # Module instantiation + health check
│       ├── outputs.tf      # Root outputs
│       └── backend.tf      # Commented-out GCS backend alternative
└── modules/
    └── obsidian_palace/
        ├── versions.tf     # Module provider requirements
        ├── variables.tf    # Module input variables
        ├── apis.tf         # GCP API enablement
        ├── secrets.tf      # Secret Manager resources + IAM
        ├── network.tf      # Static IP, firewall rules
        ├── compute.tf      # Service account, persistent disk, GCE instance
        ├── registry.tf     # Artifact Registry Docker repository
        └── outputs.tf      # Module outputs

Resources Provisioned¶

APIs Enabled¶

Secret Manager¶

Four secrets are created, each with IAM bindings granting the GCE service account roles/secretmanager.secretAccessor:

Networking¶

Compute¶

DNS¶

DNS is managed at your domain registrar, not via GCP Cloud DNS. You create a single A record pointing your domain at the static IP output by Terraform.

Artifact Registry¶

Post-Deploy Health Check¶

The root module includes a check {} block that validates the service is reachable after deployment:

check "health" {
  data "http" "health" {
    url = "https://YOUR_DOMAIN/health"
    retry {
      attempts     = 3
      min_delay_ms = 5000
    }
  }

  assert {
    condition     = data.http.health.status_code == 200
    error_message = "ObsidianPalace health endpoint did not return 200."
  }
}

Startup Sequence¶

The GCE instance runs a startup script (COS-compatible -- no apt-get) that:

1. Mounts the persistent disk at /mnt/disks/data (formats on first boot)
2. Creates data directories (vault, chromadb, obsidian-config, letsencrypt)
3. Pulls secrets from Secret Manager via the gcloud Docker image (COS has no gcloud on the host)
4. Runs certbot in Docker for Let's Encrypt SSL (first boot only)
5. Symlinks certificates to a stable path the container's nginx config expects
6. Configures Docker auth for Artifact Registry (writes config to the data disk since COS root is read-only)
7. Pulls and starts the Docker container with all env vars and volume mounts
8. Writes a cert renewal script to the data disk for scheduled execution