Integrations

ioenv syncs environment variables directly to your deployment platforms. Configure integrations from the project settings page in the dashboard.

Cloudflare Workers

Sync variables as Cloudflare Worker secrets.

1. Navigate to Project Settings → Integrations.
2. Click Connect Cloudflare.
3. Authorize ioenv with your Cloudflare API token.
4. Select the Worker to sync with.
5. Choose which environment to sync (e.g., prod).

Variables are pushed to Cloudflare on every update. Secrets are decrypted server-side before being sent to the Cloudflare API.

Vercel

Sync variables to a Vercel project.

1. Navigate to Project Settings → Integrations.
2. Click Connect Vercel.
3. Authorize ioenv via the Vercel integration.
4. Select the Vercel project.
5. Map ioenv environments to Vercel environments (dev → Development, staging → Preview, prod → Production).

Docker / Compose

Generate a .env file for Docker Compose:

ioenv pull --env=dev --format=env > .env
docker compose up

Or inject directly:

ioenv inject --env=dev -- docker compose up

GitHub Actions

Use the ioenv CLI in your CI workflow:

- name: Install ioenv
  run: npm install -g @ioenv/cli

- name: Pull env
  run: ioenv pull --env=prod
  env:
    IOENV_TOKEN: ${{ secrets.IOENV_TOKEN }}

Set IOENV_TOKEN as a GitHub Actions secret. The CLI uses this token for non-interactive authentication.

Kubernetes

Generate a Kubernetes Secret manifest:

ioenv pull --env=prod --format=k8s-secret --name=app-secrets

Output:

apiVersion: v1
kind: Secret
metadata:
  name: app-secrets
type: Opaque
data:
  API_URL: aHR0cHM6Ly9hcGkuaW50ZXJuYWw=
  DB_HOST: ZGIuY2x1c3Rlci5sb2NhbA==

Apply with kubectl apply -f.