When you're building a modern web app, authentication is one of the first things to set up—and Clerk makes it incredibly fast. By default, your app starts with a development instance so you can test and build quickly. But to go live securely, you'll need a production instance.
Not sure when or how to switch? Let's walk through the differences and steps.
Related: Dev vs Prod Environment Guide
Dev instances are optimized for speed:
Production instances are secure by design:
This setup reduces the risk of cross-site scripting and improves trust with your users.
Before anything else, secure the domain where users will log in. Clerk uses this domain for identity verification and security. Related: Using Clerk with Custom Domains
Clerk gives you a helpful checklist after creation.
Clerk provides DNS entries for:
See docs: Custom Domain DNS Setup
Each Clerk instance has its own key (Located under Configure > API Keys):
pk_live_ (publishable)sk_live_ (secret)Replace your .env values with the new production keys.
Docs: Environment Variables Reference
Clerk uses shared credentials in dev—but in production, you must register your app with each identity provider.
For example, when using Google:
Detailed walkthrough: Google OAuth with Clerk
Also see the full OAuth guide for other providers.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。