Taskline

Tasks, in a line.

Taskline is a self-hosted, Linear-inspired project-management application built with Next.js, PostgreSQL, Prisma, Auth.js, and React. Issues, projects, teams, cycles, initiatives, triage, saved views, members, invitations, notifications, comments, and attachments are persisted in PostgreSQL/local storage.

The supported production shape is a small, single-workspace, single-instance deployment. Taskline is not yet a multi-tenant SaaS or a horizontally scalable service. See DEPLOY.md and SECURITY.md before putting it on a network.

What works

• Credentials authentication (with optional TOTP two-factor and passkeys), invite-only registration, and ADMIN/MEMBER/GUEST authorization
• Issue, project, initiative, cycle, team, member, label, view, and triage flows — including comment edit/delete, issue relations, PR links, estimates, custom workflow statuses, milestones, and issue templates
• Comments, activity, subscriptions, in-app notifications (delete/snooze, per-user preferences, optional SMTP email delivery), and attachments
• Live updates: an SSE stream (/api/events) pings clients on issue and comment changes so open workspaces re-hydrate within a second, with the polling interval kept as a fallback
• Global keyboard shortcuts: c (new issue), ? (shortcut help) and g-prefixed navigation chords, mirroring the command palette hints
• Inbound GitHub webhook (/api/integrations/github/webhook, GITHUB_WEBHOOK_SECRET): pull requests are linked to issues mentioned by identifier in the title, body or branch name, and merged PRs optionally move the issue to a Done state (workspace setting, on by default)
• Local code reviews: paste a unified diff, discuss per file, approve or request changes
• Workspace agent (AI chat with persisted conversations) backed by any OpenAI-compatible endpoint — degrades to a clear "not configured" state
• Personal API keys, admin-generated password-reset links, and global session revocation
• Settings surfaces: labels, notifications, AI, templates, statuses, project labels/updates, documents, releases, SLAs, pulse analytics, asks/customer requests (intake into triage), emojis, initiatives overview
• Docker/Compose deployment, health checks, migrations, CI, security headers, backup/restore helpers, cycle snapshots, and basic abuse throttling

Reviews have no VCS integration (paste-a-diff local flow), and third-party SaaS integrations beyond the inbound GitHub webhook intentionally do not ship in this build.

Local development

Requirements: Node 22, pnpm 10, and PostgreSQL 14+.

cp .env.example .env
pnpm install
pnpm exec prisma migrate deploy
pnpm create-admin you@example.com 'a-strong-password'
pnpm dev

Open http://localhost:3000. Do not run pnpm db:seed against a production database; it creates demonstration accounts and content.

Docker Compose

Set POSTGRES_PASSWORD, AUTH_SECRET, and AUTH_URL in .env, then run:

docker compose up -d --build

Set a strong BOOTSTRAP_SECRET to create the first admin through /sign-up or POST /api/bootstrap. Keep SIGNUP_MODE=invite and invite everyone else from the Members page.

Back up the Compose database and attachment volume with:

pnpm backup

Detailed proxy, restore, and operational instructions live in DEPLOY.md.

Quality checks

pnpm exec tsc --noEmit
pnpm lint
pnpm exec prettier --check .
pnpm test
pnpm build
pnpm audit --prod

Database integration tests require TEST_DATABASE_URL pointing to a disposable, migrated PostgreSQL database. CI provisions one automatically.

Architecture

• app/ — pages, route handlers, and auth-protected workspace layout
• lib/api/*.server.ts — server-side domain and persistence logic
• lib/api/*.ts — client DTO adapters and HTTP calls
• store/ — hydrated Zustand caches and optimistic mutations
• prisma/ — schema, migrations, and optional demonstration seed
• components/ — product UI; legacy mock-data/ modules still provide display types, icon registries, and seed fixtures

Read AI_GUIDE.md before making structural changes.