Implement layered environment configuration system

[jaypatrick]

Overview

This PR implements a layered environment configuration system using .envrc and direnv for automatic environment management based on git branches, with full GitHub Actions integration.

Changes

Environment File Structure

• .env - Base configuration shared across all environments (committed)
  • Non-sensitive defaults: PORT, COMPILER_VERSION, DENO_DIR
• .env.development - Development-specific configuration (committed)
  • Local SQLite database
  • Cloudflare Turnstile test keys (always passes)
• .env.production - Production configuration with placeholders (committed)
  • Template values only, actual secrets go in .env.local
• .env.local - Local overrides and secrets (NOT committed)
  • All API keys, database credentials, and sensitive data
• .env.example - Updated template with full documentation
• .envrc - Environment loading logic (committed)
  • Automatic branch-to-environment mapping
  • Loads layered configuration files

Loading Order

Environment variables are loaded in this order (later overrides earlier):

1. .env (base)
2. .env.$ENV (environment-specific)
3. .env.local (local overrides/secrets)

Branch-to-Environment Mapping

The .envrc automatically determines environment from git branch:

• main/master → production
• dev/develop → development
• Other branches → local

Wrangler Integration

• Updated wrangler.toml with environment-specific configurations
• Added [env.development] and [env.production] sections
• Environment variables loaded automatically during local dev
• Production secrets managed via wrangler secret put

GitHub Actions Integration

• Composite Action (.github/actions/setup-env)
  • Reusable action that mimics .envrc behavior
  • Automatically detects environment from branch
  • Loads .env and .env.$ENV files into workflow
  • Provides environment as output for conditional logic
• Updated CI Workflow
  • Added environment loading to test job
  • Added environment loading to deploy job
  • Variables automatically available to all workflow steps
• Comprehensive Documentation (.github/ENV_SETUP.md)
  • Usage examples and best practices
  • Security guidelines for production secrets
  • Debugging tips

Documentation

• Created .env.README.md with comprehensive setup instructions
• Created .github/ENV_SETUP.md for GitHub Actions usage
• Includes troubleshooting guide and security best practices
• Documents all available environment variables

Security Improvements

• Updated .gitignore to allow base config files while keeping secrets ignored
• Clear separation between committed config and local secrets
• Test keys for development, placeholders for production
• .envrc committed (contains no secrets, only loading logic)
• .env.local never committed (contains all secrets)

Testing

• ✅ Environment loads correctly on dev branch (development)
• ✅ Variables properly layered from base → env-specific → local
• ✅ Secrets remain in .env.local (not committed)
• ✅ GitHub Actions integration works with branch detection
• ✅ .envrc properly committed and loadable

Local Setup

# 1. Enable direnv (one-time setup)
brew install direnv
echo 'eval "$(direnv hook zsh)"' >> ~/.zshrc
source ~/.zshrc

# 2. Allow the .envrc file
direnv allow

# 3. Create your local secrets file
cp .env.example .env.local
# Edit .env.local with your actual secrets

# 4. Verify environment
echo $COMPILER_VERSION

GitHub Actions Usage

steps:
  - uses: actions/checkout@v4
  
  - name: Load environment variables
    uses: ./.github/actions/setup-env
  
  - name: Use variables
    run: echo "Version: $COMPILER_VERSION"

Wrangler Usage

# Local development (uses .env.local automatically)
wrangler dev

# Deploy to environments
wrangler deploy --env development
wrangler deploy --env production

Co-Authored-By: Warp agent@warp.dev

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	adblock-compiler	36bd709	Feb 03 2026, 09:16 PM

[jaypatrick]

@copilot fix the CI errors

[Copilot]

@jaypatrick I've opened a new pull request, #255, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

Pull request overview

Implements a layered environment configuration approach for local development and CI by introducing committed base/env-specific .env files, a direnv-driven .envrc, and a reusable GitHub Actions composite action to load environment variables based on the branch.

Changes:

• Added committed .env / .env.development / .env.production plus updated .env.example and new .env.README.md to document the layered configuration approach.
• Added .envrc for automatic branch-to-environment mapping and layered env loading via direnv.
• Added a composite action (.github/actions/setup-env) and wired it into CI to load env vars in GitHub Actions; updated wrangler.toml env sections.

Reviewed changes

Copilot reviewed 11 out of 12 changed files in this pull request and generated 11 comments.

Show a summary per file

File	Description
wrangler.toml	Adds env-specific sections and adjusts variable management; updates Hyperdrive local connection config.
.gitignore	Stops ignoring committed base env files while keeping local secrets ignored.
.github/workflows/ci.yml	Loads environment variables in CI jobs via the new composite action.
.github/actions/setup-env/action.yml	Composite action to detect environment from branch and load .env files into $GITHUB_ENV.
.github/ENV_SETUP.md	Documentation for using the composite action in workflows.
.envrc	direnv-based loader implementing branch-to-environment mapping and layered env loading.
.env	Base committed env defaults intended to be shared across environments.
.env.development	Development-specific env defaults (e.g., sqlite and Turnstile test keys).
.env.production	Production env template/defaults intended for main/master.
.env.example	Expanded template documenting available variables and setup.
.env.README.md	Repository-level documentation for the layered environment system.

[jaypatrick]

@copilot open a new pull request to apply changes based on the comments in this thread

[Copilot]

@jaypatrick I've opened a new pull request, #256, to work on those changes. Once the pull request is ready, I'll request review from you.

[jaypatrick]

@copilot fix the ci errors

[Copilot]

@jaypatrick I've opened a new pull request, #257, to work on those changes. Once the pull request is ready, I'll request review from you.