NestJS yana ba da pakage @nestjs/config don sarrafa configuration da kuma variables na environtment a cikin tsari mai inganci, wanda ke amfani da nau'i, da wanda zai iya a jera daidai. Yana karawa .env files, yana bada daidai config, kuma yana sa ƙididdiga ya ji dadi ta dukkan app ta hanyar injectable ConfigService.
import { ConfigModule } from "@nestjs/config";
@Module({
imports: [
ConfigModule.forRoot({
isGlobal: true, // available app-wide without re-importing
envFilePath: ".env",
validationSchema: Joi.object({ // validate env vars at startup (fail fast)
DATABASE_URL: Joi.string().required(),
PORT: Joi.number().default(3000),
JWT_SECRET: Joi.string().required(),
}),
}),
],
})
export class AppModule {}
ConfigModule.forRoot() yana karawa environment variables (daga .env + process environment) kuma — ainihin — zai iya bada daidai su tare da schema (Joi), don haka ba jiya config ko ba jiya configuration zai bugi app a startup tare da bayani mai sarari maimakon kain iko a runtime.
@Injectable()
export class DatabaseService {
constructor(private configService: ConfigService) {} // inject ConfigService
connect() {
const url = this.configService.get<string>("DATABASE_URL");
const port = this.configService.get<number>("PORT", 3000); // with a default
}
}
A badilai na karanta process.env kai nan daidai, kuna jera ConfigService kuma kiran get() — wanda ya dace da nau'i, wanda zai iya bincike, kuma tsakiya.
// config/database.config.ts — group related config with registerAs
export default registerAs("database", () => ({
host: process.env.DB_HOST,
port: parseInt(process.env.DB_PORT, 10),
}));
// load it: ConfigModule.forRoot({ load: [databaseConfig] })
// access it: configService.get("database.host")
Yamitacce sun haɗa da alamomi masu alaƙa kuma sun kasance config organized kamar yadda yake girma.
✗ process.env scattered everywhere → hard to test, no validation, stringly-typed
✓ ConfigService → injectable (mockable in tests), validated at startup, typed,
centralized — the structured NestJS way
✓ Keep secrets in .env (GITIGNORED) — commit a .env.example documenting required vars
✓ In production, inject config via the platform's env vars / secret manager
✓ Validate at startup so misconfiguration fails immediately with a clear message
Sarrafa configuration daidai ita ce mahimmi don kowane aikace-aikacen gaida — Faɗin database URLs, API keys, ports, asirra, kuma feature flags aminci kuma mabambanta a cikin environments (dev, staging, production).
NestJS's @nestjs/config yana ba da tsarin, nau'in hanya don yi haka, kuma fahimtar shi ita ce mahimmi a kullum.
Manyan ƙima kaɗan karashi karone karashi kaɗan ba zaɓi ba ne karashi karashi gida: injectable ConfigService yana sa config mai bincike (mockable a cikin bincike) kuma tsakiya; bada daidai a startup (tare da Joi schema) yana kama nahan ba jiya configuration ko ba jiya ko ba shi daidai tamkar haka nan haka nan, ainihin haka cikin bayyani maimakon nah haka cikin runtime kowane gida; kuma yamitacce sun kasance config organized.
Tare da kyauta-waje kyauta dama sarrafa process.env kai nan, wannan yana ba da safe, portable, validated configuration.
Sanin yaya za a saita ConfigModule, jera kuma amfani ConfigService, kuma bada daidai config ita ce mahimmi don gina production-ready NestJS aikacen kuma yana nuna na baje back-end aiki.