You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(auth): drop bannedEmails; gate AppConfig on isHosted
- Remove the bannedEmails denylist entirely (better-auth banning + blockedSignupDomains cover the cases).
- Move isAppConfigEnabled into feature-flags.ts and gate it on isHosted, so AppConfig is hosted-only; self-hosted/OSS always uses the env-var fallback and never constructs the AWS client.
S3_FORCE_PATH_STYLE: z.string().optional(),// Force path-style addressing (MinIO/Ceph RGW). Defaults to false (AWS S3, R2). Coerced via envBoolean at the consumption site
224
224
225
225
// Dynamic config - AWS AppConfig (hosted source of truth for signup/login gating lists; unset => env-var fallback)
226
-
APPCONFIG_APPLICATION: z.string().optional(),// AppConfig application id/name. When set with APPCONFIG_ENVIRONMENT, gating lists come from AppConfig instead of env vars
226
+
APPCONFIG_APPLICATION: z.string().optional(),// AppConfig application id/name. On hosted deployments, when set with APPCONFIG_ENVIRONMENT, gating lists come from AppConfig instead of env vars
227
227
APPCONFIG_ENVIRONMENT: z.string().optional(),// AppConfig environment id/name. Profile name is an app-side constant ('access-control'), not an env var
0 commit comments