add-setting-env

Configure user settings with environment variables by creating domain-specific TypeScript files in src/envs/<domain>.ts that expose server configuration, then merge those values into your user store. This centralizes defaults across deployment and self-hosting environments, eliminating manual configuration errors.

Define environment-based defaults by creating typed server config files, extending your GlobalServerConfig type, and implementing getServerGlobalConfig to assemble values from environment variables. This approach scales across dev, staging, and production while keeping configuration discoverable and version-controlled.

Update .env.example alongside your TypeScript config files and user store integration, enforcing YAML frontmatter with name and description fields. This keeps documentation authoritative and deployable teams aligned on required variables and their purposes.

Yes. Merge domain server settings into your user store by updating the action layer in src/store/user/slices/common/action.ts to apply environment-configured defaults. This lets you preserve existing store structure while layering server-side configuration on top.

Yes. Extend packages/types/src/serverConfig.ts to include your domain in GlobalServerConfig, then implement typed getter functions like get<Domain>Config in your env file. This ensures type safety and prevents configuration drift across your codebase.