Connect & .env

Open My Impulse → your project → Connect. Every bundled service contributes its credentials to a single, copyable .env:

# Database
DATABASE_URL=postgres://app:••••@db.my-app.impulse:5432/app

# Object storage (S3-compatible)
S3_ENDPOINT=https://s3.dfw.impulse
S3_ACCESS_KEY=AKIA••••••••
S3_SECRET_KEY=••••••••••••

# Cache (Redis-compatible)
REDIS_URL=rediss://default:••••@cache.my-app.impulse

# Auth
AUTH_URL=https://auth.my-app.impulse
AUTH_ANON_KEY=eyJhbGci••••

Values stay masked in the dashboard until you reveal them; rotate any credential from the service’s page and the Connect tab updates immediately.

Framework wiring

• Next.js / Node — process.env.DATABASE_URL with pg, postgres, or Prisma; any S3 SDK against S3_ENDPOINT.
• Laravel — map to DB_*, AWS_* (S3-compatible), REDIS_URL in config/.
• Django / Rails — standard database-URL parsing; boto3 / aws-sdk with a custom endpoint.

Every value uses open protocols, so no Impulse-specific client library is ever required.