Skip to main content

​
What this covers

This page is for the RLink application (dazedmind/rlink), not this Mintlify documentation site. Use it when you want a minimal path from clone to running dashboard.

​
1. Clone and install

git clone https://github.com/dazedmind/rlink.git
cd rlink
npm install
Use npm only (the repo ships package-lock.json).

​
2. Configure environment

Create a .env file in the project root. You need at minimum a Neon DATABASE_URL, NEXT_PUBLIC_APP_URL, BETTER_AUTH_SECRET (32+ characters), and email keys if you exercise mail flows. See Getting started for the full variable table and explanations.

​
3. Apply the database schema

npx drizzle-kit migrate
For a throwaway local database only, npx drizzle-kit push is faster—never use push against production.

​
4. Run the app

npm run dev
Open http://localhost:3000/login. The authenticated area lives under /home/* and relies on ProtectedRoute plus session cookies from Better Auth.

​
Common pitfalls

  • NEXT_PUBLIC_APP_URL mismatch — Must match the origin you use in the browser (including http vs https and no stray trailing slash). Wrong values break auth cookies and redirects.
  • Missing auth tables — If login fails with database errors, confirm migrations ran and db/auth-schema.ts tables exist in Neon.
  • Resend not configured — Password reset and campaign email need RESEND_API_KEY / RESEND_FROM; without them, mail-dependent flows fail at runtime.

​
Next steps

Introduction

Product overview and stack

Getting started (full)

Prerequisites, scripts, and verification

Architecture

How CMS, CRM, and IAM fit together

Authentication

Better Auth, sessions, and 2FA