Angular

An Angular app compiles to static files that run in the browser, so it has no process.env at runtime and every value it ships is public. Inject configuration at build time and keep real secrets on a server.

Local development and builds

Angular reads configuration from src/environments/environment.ts, which is baked in when the app is built. To use Enkryptify values, run Angular under ek run and generate that file from the injected variables. A small script keeps values out of source control:

scripts/set-env.ts

import { writeFileSync } from "node:fs";

writeFileSync(
  "src/environments/environment.ts",
  `export const environment = {
  production: false,
  apiBase: "${process.env.API_BASE ?? ""}",
};\n`,
);

Generate the file before serving or building:

# Develop
ek run -- node scripts/set-env.ts && ek run -- npm start

# Build
ek run -- node scripts/set-env.ts && ek run -- ng build

Anything compiled into an Angular bundle is visible in the browser. Only inject non-sensitive configuration this way; call a backend for anything that needs a real secret.

Deploying

Run the build under ek run so your configuration is present, then deploy the static output. If your host builds the app, use a sync to provide those variables there. For an Angular app with a Node SSR server, the server reads secrets directly from process.env.

NuxtUse Enkryptify secrets in your Nuxt app, locally and in production

Integrations

Native Syncs

Framework Guides

Local development and builds

Deploying

​Local development and builds

​Deploying

Local development and builds

Deploying