DevLink

DevLink is a small profile hub for developers: links, skills, and a clean public profile page.

Features

• Auth
  • Email + password (credentials)
  • Optional OAuth (GitHub, Google) if env vars are set
• Dashboard
  • Edit username, display name, bio, skills, avatar URL
  • Add/remove links
  • View basic analytics (views, clicks)
• Public profile
  • GET /u/:username
  • Tracked links via GET /l/:linkId (click count + redirect)

Tech

• Next.js (App Router)
• NextAuth
• Prisma + Postgres
• Tailwind CSS

Getting started

1) Install dependencies

npm install

2) Start Postgres (recommended)

docker compose up -d

This repo maps the container's 5432 to host 5433 to avoid conflicts with an existing local Postgres.

3) Configure env

Create .env (or copy from .env.example) and fill in at least:

• DATABASE_URL
• NEXTAUTH_SECRET

Optional (enables OAuth buttons):

• GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET
• GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET

4) Setup database

npx prisma migrate dev

Optional seed data:

npm run db:seed

Seeded credentials:

• Email: demo@devlink.local
• Password: password123

5) Run dev server

npm run dev

Open:

• http://localhost:3000
• Create an account at http://localhost:3000/login

Routes

• GET /dashboard (authenticated)
• GET /u/:username (public)
• GET /l/:linkId (public tracked redirect)

Notes / tradeoffs

• Link click tracking is done via a server redirect route (/l/:linkId) so it works without client JS.
• OAuth is optional to keep local setup simple.

Architecture

• src/app contains all Next.js routes (pages, API, server actions).
• src/components contains reusable UI components.
• src/lib contains helpers (auth, Prisma, rate limit, validators).
• prisma/schema.prisma defines the database models.

Contributing

• Use feature branches and pull requests.
• Write tests for new features or bug fixes.
• Run npm run lint and npm test before submitting.
• Document any new endpoints or major changes in README.
• For issues or questions, open a GitHub issue.

Security

• Sessions use NextAuth with JWT.
• Passwords use bcrypt hashes.
• Public routes include /u/:username, /l/:linkId, and discover endpoints.
• Rate limiting uses an in-memory store. It only limits per server instance.
• Login callbackUrl only accepts relative paths.

Deployment

• Hosting targets Vercel.
• Required env vars are DATABASE_URL and NEXTAUTH_SECRET.
• Optional env vars enable OAuth: GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET.
• Use a managed Postgres database in production.