OneApps

OneApps is a service workspace for launching trusted media, music, food, travel, shopping, payment, and learning platforms from one focused directory. It opens official destinations only; it does not proxy or clone third-party services.

What changed since last version

• Product-oriented OneApps identity and responsive dark workspace UI
• Searchable service directory and collection browsing
• Database-backed saved services, launch history, and click events
• Redirect telemetry recorded without delaying the user redirect
• Admin-only category and service onboarding with HTTPS URL validation
• Activity-query indexes for favorites, recents, and analytics

Stack

• Next.js 14 / React 18
• NextAuth credentials provider for local development
• Prisma + PostgreSQL
• Node.js 20+

Run locally

1. Install prerequisites

• Node.js 20 or newer
• PostgreSQL 16 or newer

2. Install dependencies

cd C:\projects\OneApps
npm ci

3. Configure the environment

Copy the template and update the connection string:

Copy-Item apps\web\.env.example apps\web\.env.local

Set a secure NEXTAUTH_SECRET before using any non-local environment.

4. Create the database schema

npm run db:generate
npm run db:migrate -- --name oneapps_workspace

5. Start the app

npm run dev

Open http://localhost:3000.

Local development accounts

• Directory owner: mukul@example.com / Password@123
• Member: user@example.com / Password@123

These credentials exist only to support local development. Replace the credential provider with your identity provider before production.

Operational notes

• DATABASE_URL absent: catalog browsing uses the local catalog fallback; personalization and telemetry are disabled.
• DATABASE_URL configured: the first local sign-in creates/updates the corresponding workspace user record, then saved services, recent launches, and click events persist to PostgreSQL.
• Generate and apply Prisma migrations as part of your deployment flow; do not use prisma db push for production releases.
• The redirect route accepts only catalog entries stored by the app. Admin onboarding accepts HTTPS URLs only.

Validation

npm run db:generate
npm run build

The repository intentionally leaves container definitions and CI/CD ownership to the deployment workflow.