miniperplx/env/server.ts
simplr-sh 186bd3c2cc Refactor environment variable handling and improve API key management
- Introduced `client.ts` and `server.ts` for structured environment variable management using `@t3-oss/env-nextjs`.
- Updated references to environment variables in various files to use the new `clientEnv` and `serverEnv` objects.
- Enhanced the `next.config.mjs` file to validate environment variables during build.
- Added new dependencies: `@t3-oss/env-nextjs` and `jiti` for improved environment handling.
- Cleaned up imports and ensured consistent usage of environment variables across the application.
2025-01-06 10:28:54 +05:30

25 lines
853 B
TypeScript

// https://env.t3.gg/docs/nextjs#create-your-schema
import { createEnv } from '@t3-oss/env-nextjs'
import { z } from 'zod'
export const serverEnv = createEnv({
server: {
ELEVENLABS_API_KEY: z.string().min(1),
TAVILY_API_KEY: z.string().min(1),
EXA_API_KEY: z.string().min(1),
TMDB_API_KEY: z.string().min(1),
YT_ENDPOINT: z.string().min(1),
FIRECRAWL_API_KEY: z.string().min(1),
OPENWEATHER_API_KEY: z.string().min(1),
SANDBOX_TEMPLATE_ID: z.string().min(1),
GOOGLE_MAPS_API_KEY: z.string().min(1),
MAPBOX_ACCESS_TOKEN: z.string().min(1),
AZURE_TRANSLATOR_KEY: z.string().min(1),
AZURE_TRANSLATOR_LOCATION: z.string().min(1),
TRIPADVISOR_API_KEY: z.string().min(1),
AVIATION_STACK_API_KEY: z.string().min(1),
CRON_SECRET: z.string().min(1),
},
experimental__runtimeEnv: process.env,
})