Architectural Deployment

Launch your Zero-Trust operations center in minutes. Choose between the highly-available orchestration stack or minimal standalone binaries.

High Availability Docker Deployment

This is the required architecture for Production SOC environments. Running the unified compose stack strictly wraps the Node.js Host, automatically injecting a heavily pooled PgBouncer Sidecar for massive scale, and running schema upgrades asynchronously inside an ephemeral isolated Migrator Container.

# 1. Clone the master repository and drop into the directory
git clone https://github.com/Cyber-Sec-Space/openticket.git
cd openticket

# 2. Deploy the isolated containers with detatched threads
docker-compose up -d --build

Safe Array Migration

Upgrading from legacy v0.5.x environments into the v1.0.0-rc.1 Edge layout? Use the idempotent production pipe to map old user schemas to the new strictly typed plugin permission arrays.

git pull origin main
npm run migrate:prod

Bare-Metal Automated Setup

Prefer running Node natively on your network interface bypassing Docker sockets completely? OpenTicket provides an interactive setup script that automatically provisions your variables, installs dependencies, and synchronizes the Edge Full-Text Search database explicitly without manual intervention.

# 1. Clone the repository
git clone https://github.com/Cyber-Sec-Space/openticket
cd openticket

# 2. Run the interactive setup wizard
chmod +x setup.sh
./setup.sh

# Hint: For headless CI/CD, bypass prompts dynamically:
# ./setup.sh --non-interactive

# 3. Boot the native development server
npm run dev

Pre-compiled Standalone Binaries (v1.0.0-rc.1)

For operations wishing to bypass massive node_modules compilations on isolated internal VPCs entirely, OpenTicket explicitly generates tightly minified Next.js .next/standalone targets attached to GitHub releases. This dramatically cuts dependency audit surfaces.

Production Only: The standalone build does not contain Prisma CLI logic. You must have already mitigated and structured your target database beforehand via an external script or CI/CD deployment ring.

# 1. Download & Verify the v1.0.0-rc.1 encapsulated build
wget https://github.com/Cyber-Sec-Space/openticket/releases/download/v1.0.0-rc.1/openticket-standalone-v1.0.0-rc.1.tar.gz
echo "709d78529e7ef54a090dcbb761fe1b35f26336b2626dcf74fbae962ea8ecd2ef *openticket-standalone-v1.0.0-rc.1.tar.gz" | shasum -a 256 --check

# 2. Extract minified application locally
tar -xzf openticket-standalone-v1.0.0-rc.1.tar.gz
cd openticket-standalone

# 3. Supply environmental variables externally
cp .env.example .env

# 4. Boot via Node's native cluster limits
node server.js