1.0.0-rc.1 · Release Candidate1 min read
Domain and URL Configuration
Configure public, admin, API, CORS, and callback URL boundaries using external operator-owned values.
Use NEXT_PUBLIC_APP_URL, NEXT_PUBLIC_API_URL, ADMIN_APP_URL, and CORS_ALLOWED_ORIGINS for URL and origin boundaries. Provider callback and return URLs are configured separately where the provider supports them.
URLs must be syntactically valid when the schema requires a URL. Real domains are deployment data and must not appear in public documentation. A URL setting does not provision DNS, TLS, reverse-proxy routes, or provider approvals.
Verification
Check the URL values from the running process, verify CORS against the intended web and admin origins, and exercise web, admin, API, and callback routing through the configured edge.
Related articles
Environment VariablesSource-verified runtime environment keys grouped by database, application, storage, mail, and provider concerns.DNS and Domain RequirementsPrepare public and administrative domain names without exposing production infrastructure in documentation.TLS RequirementsDocument the external TLS boundary for AutoCore without claiming a built-in certificate authority or deployment.