better-auth-best-practices

To set up Better Auth, create an auth.ts file with your chosen ORM adapter like Prisma or Drizzle, set the required BETTER_AUTH_SECRET and BETTER_AUTH_URL environment variables, and run the @better-auth/cli migrate command to generate the database schema.

Better Auth sessions disappear after restarts if they are stored in memory instead of a persistent database or secondary storage. Configure a compatible database adapter or use a secondary storage solution like Redis to persist session data across server restarts.

Yes, Better Auth supports OAuth providers alongside email and password authentication. You can configure social OAuth sign-in within your auth.ts file and use plugins to extend or tree-shake additional authentication methods as needed for your application.

You need to run the @better-auth/cli migrations whenever you initially set up your database schema or after modifying your auth configuration by adding plugins or changing adapters. Use the CLI migrate and generate commands to ensure your database structure matches your auth setup.

The best way to secure Better Auth cookies for production is to enforce secure cookie flags, implement rate limiting, and configure pre and post action hooks. You should also verify the GET /api/auth/ok health endpoint returns a status of ok before deploying.

Yes, you can use Redis as secondary storage for Better Auth sessions to balance security and performance. Configuring secondary storage allows you to offload session persistence from your primary database while maintaining secure, session-backed authentication.