Build your knowledge space.
Install Arkivel, connect PostgreSQL, choose your deployment settings, and keep the operational boundary explicit.
Installation
Arkivel requires Node.js, PostgreSQL, and an object store only when you enable file uploads.
git clone https://github.com/mohammed-alsalhi/arkivel.git
cd arkivel
npm install
cp .env.example .env
npx prisma db push
npm run devConfiguration
Set DATABASE_URL, an ADMIN_SECRET, and NEXT_PUBLIC_BASE_URL. Brand copy, logos, layouts, registration, discussions, and uploads are environment-driven.
Use ARKIVEL_SITE_MODE=product only for a database-free public product and documentation deployment. Omit it for a working wiki.
Authentication
A production wiki must define ADMIN_SECRET. Missing admin configuration intentionally leaves local development open and must not be used on a public wiki deployment.
Multi-user installs can add viewer, editor, and admin accounts through Arkivel's database-backed session system.
Deployment
Vercel is the native path for the current Next.js application. Back up PostgreSQL and review npx prisma db push as a separate release operation; application builds run npm run build and never mutate the schema or use --accept-data-loss.
Use separate deployment projects—and separate databases—for independent Arkivel instances. The same public Git repository can remain the source for all of them.