Recommended Patterns for Centralized Configuration Management in Effect and Next.js
Slightly related to the previous message, I was curious whether there are recommended patterns when handling config across the entire app. In my Next.js frontend for example I do like to use https://env.t3.gg which consolidates all variables into a single object and has an explicit list of required environment variables. With the default Config in Effect every single service hardcodes its used configuration and I was wondering whether something more centralized makes more sense.
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
