Skip to main content

Origin by Corvus - Production Installation Guide

Autonomous, Interactive & Zero-Touch Deployment Runbook​

Install Status Platform Support Security Level

Quantum Tiger (Morning Bay Technology Pvt. Ltd.)
Automated pre-flight checks, private Gitea PAT authentication, and self-healing deployment.

Docs Hub - User GUIDE - [SYNC] Updates - Backups


Installation Architecture​

The automated installer executes a 14-step verified deployment sequence:


60-Second Quick Start​

Deploy directly with a single terminal command:

Linux & macOS (Automated Curl-to-Bash)
curl -fsSL https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus/raw/main/install.sh | sudo bash

Interactive CLI: To run locally with full interactive control, clone the repo and execute:

chmod +x install.sh
sudo ./install.sh
Windows Server & Desktop (PowerShell Administrator)

Launch an elevated PowerShell prompt (Run as Administrator):

irm https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus/raw/main/install.ps1 | iex

Interactive CLI: Or run locally:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\install.ps1

Comprehensive Pre-Flight Checklist​

Before launching the installer, verify that your host environment meets the mandatory prerequisites:

  • CPU Architecture: 64-bit x86_64 (amd64) or aarch64 (arm64).
  • Host Sizing: Minimum 2 vCPUs and 4 GB RAM (4 vCPUs / 8 GB recommended for 250 active members).
  • Storage Volume: At least 20 GB free disk space on SSD/NVMe.
  • DNS Record: A domain or subdomain (e.g., chat.example.com) pointed to your server's public IP.
  • Perimeter Firewall: Ports 80 (TCP), 443 (TCP), 8443 (UDP/TCP) opened for inbound traffic.
  • Gitea PAT: A Personal Access Token from https://git.projectdefcorp.com with read:repository and read:packages.

Gitea Personal Access Token (PAT) Setup​

Origin by Corvus uses a single Personal Access Token for both downloading repository scripts and pulling container images:

Pre-Authorized Deployment Token​

For enterprise installations, Quantum Tiger provides a pre-authorized client deployment token:

  • Deployment Token: 073eb9a9bbdf4f7d33b50d4c7d0b53efd023392b
  • Scopes Granted: read:repository, read:packages
  • Endpoint: https://git.projectdefcorp.com

You can supply this token via the GITEA_PAT environment variable prior to execution:

# Linux / macOS
export GITEA_PAT="073eb9a9bbdf4f7d33b50d4c7d0b53efd023392b"
curl -fsSL https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus/raw/main/install.sh | sudo GITEA_PAT="$GITEA_PAT" bash

# Windows PowerShell
$env:GITEA_PAT = "073eb9a9bbdf4f7d33b50d4c7d0b53efd023392b"
irm https://git.projectdefcorp.com/Quantum-Tiger/Origin-By-Corvus/raw/main/install.ps1 | iex

How to Generate a Custom Organization Token:​

  1. Log in to https://git.projectdefcorp.com.
  2. Click your avatar → Settings → Applications → Generate New Token.
  3. Name the token: origin-production-deploy.
  4. Check only these two scopes:
    • - [x] read:repository
    • - [x] read:packages
  5. Click Generate Token and copy the resulting string immediately.

[!IMPORTANT] The installer prompts for this token once at the start of installation (if not supplied via GITEA_PAT) and securely uses it for both repository downloads and docker login. The token is never logged to disk or printed in output.


Interactive Operations CLI (Post-Installation)​

Once installed, running ./install.sh or .\install.ps1 without arguments launches the Operations & Deployment CLI:

====================================================================
Origin by Corvus - Operations & Deployment CLI
Quantum Tiger (Morning Bay Technology Pvt. Ltd.)
====================================================================

Please choose an action:
1) Install Origin by Corvus (Production Stack)
2) Run preflight diagnostics
3) Verify cryptographic checksums
4) Update to a new version
5) Rollback to previous version
6) Check deployment status & health
7) Create manual backup
8) Uninstall Origin by Corvus
9) Exit

Post-Installation Operations & Full-Lifecycle Management (The 5 Operational Layers)​

After running the initial installation, clients do not need to memorize disparate tools or write custom scripts. The installer itself (install.sh on Linux/macOS and install.ps1 on Windows) serves as a persistent, full-lifecycle operations CLI.

Post-installation operational activities can be performed through five distinct management layers:

Layer 1: Unified Operations CLI (install.sh / install.ps1)​

The client can navigate to their deployment directory and execute operations either interactively or via headless command-line subcommands.

A. Interactive Operations Menu​

Running the script without arguments opens an interactive terminal menu:

  • Linux & macOS:
    sudo ./install.sh
  • Windows Server / Desktop (PowerShell Administrator):
    .\install.ps1

B. Direct Headless Subcommands​

For automated administration, scheduled jobs, or terminal scripts:

Operational ActivityLinux & macOS CommandWindows PowerShell CommandDescription
Check Status & Healthsudo ./install.sh status.\install.ps1 statusProbes container states, exposed ports, and the /api/v4/system/ping health endpoint.
Run Diagnosticssudo ./install.sh diagnostics.\install.ps1 diagnosticsValidates CPU, RAM, disk space, Docker engine, Compose plugin, and firewall ports.
Verify Checksumssudo ./install.sh verify.\install.ps1 verifyValidates all installer scripts against SHA-256 signatures in checksums.sha256.
Update Versionsudo ./install.sh update v1.1.0.\install.ps1 update v1.1.0Automates database pre-backup, pulls image from Gitea registry, restarts stack, and auto-rolls back if health check fails.
Rollback Versionsudo ./install.sh rollback.\install.ps1 rollbackInstantly restores the previous container image and configuration backup.
Manual Backupsudo ./install.sh backup.\install.ps1 backupDumps PostgreSQL database (pg_dump) and compresses all persistent volumes into backups/.
Safe Uninstallsudo ./install.sh uninstall.\install.ps1 uninstallSafely stops containers, archives configuration, and offers to preserve or wipe data.
Help Screensudo ./install.sh help.\install.ps1 helpDisplays the command syntax and usage parameters.

Layer 2: Dedicated Convenience Commands (Linux PATH)​

During installation on Linux, dedicated helper scripts are installed directly into /usr/local/bin/ so administrators can run them from any directory:

  • Check Service Health:
    origin-status
  • Create Timestamped Backup:
    origin-backup
    Creates both a gzipped PostgreSQL dump (backups/manual-db-TIMESTAMP.sql.gz) and a full volume archive.
  • Apply Version Update:
    origin-update v1.1.0
  • Emergency Rollback:
    origin-rollback

Automated Daily Backups:​

The installer configures /etc/cron.d/origin-backup automatically on Linux:

  • Daily at 2:00 AM: Full database dump (backups/db_YYYY-MM-DD.sql.gz).
  • Weekly on Sundays at 3:00 AM: Full persistent volume backup (backups/volumes_YYYY-MM-DD.tar.gz).
  • Daily at 4:00 AM: Automatic retention cleanup deleting backups older than 30 days.

Layer 3: Direct Docker Compose Management​

Because Origin by Corvus is deployed via standard Docker Compose, administrators can also use standard Docker commands:

  • Stream Live Container Logs:
    # All services
    docker compose logs -f

    # Application server only
    docker compose logs -f origin

    # Database logs only
    docker compose logs -f origin-postgres

    # Reverse proxy / SSL ingress logs
    docker compose logs -f origin-nginx
  • Restart Services (Controlled Restart):
    # Restart only the application container without touching the database
    docker compose restart origin

    # Restart the full stack
    docker compose restart
  • Stop and Start the Deployment:
    # Stop services without deleting data
    docker compose down

    # Start services in the background
    docker compose up -d

Layer 4: In-Container CLI Management (mmctl)​

For command-line user management, team setup, and system configuration:

  • User Administration:
    # List all registered users
    docker exec -it origin mmctl --local user list

    # Create a new team member
    docker exec -it origin mmctl --local user create --email user@company.com --username john --password "SecurePassword123"

    # Reset a forgotten password
    docker exec -it origin mmctl --local user reset-password john --password "NewPassword456"

    # Promote user to System Administrator
    docker exec -it origin mmctl --local user make-admin john
  • Team & Channel Administration:
    # List all teams
    docker exec -it origin mmctl --local team list

    # List channels in a team
    docker exec -it origin mmctl --local channel list <team-name>
  • Direct Database Access:
    docker exec -it origin-postgres psql -U origin_user -d origin_db

Layer 5: Web-Based Management (System Console)​

For non-terminal administration, 100% of day-to-day operations can be managed graphically:

  1. Log in to https://your-domain.com as a System Administrator.
  2. Click the application grid icon in the top left and select System Console.
  3. Manage settings visually:
    • Email / SMTP: Configure outbound email notifications.
    • Origin Calls (WebRTC): Configure audio/video calling, WebRTC listening port (8443), and STUN/TURN credentials.
    • Origin Boards & Playbooks: Configure project boards and workflow automation.
    • Security & Authentication: Enforce Multi-Factor Authentication (MFA), password complexity, and session timeouts.
    • Compliance & Exports: Generate audit logs and data exports.

Automated CI/CD & Gitea Actions Workflows​

For automated deployment pipelines and container life-cycle management, Origin by Corvus integrates 13 enterprise Gitea Actions workflows:

  • Continuous Integration (ci.yml): Lints installers, Dockerfiles, Go server code, and TypeScript models.
  • Pull Request Quality Gates (pr-quality-gate.yaml): Enforces unit test coverage (>60%) and cryptographic signature integrity.
  • Coolify Deployment & Log Streaming (deploy.yaml): Deploys application containers to Coolify staging/prod and streams live build logs.
  • Multi-Architecture Publisher (docker-publish.yml): Publishes linux/amd64 and linux/arm64 images to the private Gitea container registry.
  • Public Documentation Site (docs-site.yaml): Builds and publishes Docusaurus documentation to docs.origin.projectdefcorp.com.
  • Emergency Rollback (rollback.yaml): Triggers automated rollbacks to verified release tags or commit SHAs.

For complete workflow parameters, triggers, manual dispatch options, and secret configurations, see the Gitea Actions Workflows Handbook.


Post-Installation & Administrator Onboarding​

1. Initial Web Access​

  1. Open your browser and navigate to https://your-domain.com.
  2. Complete the Initial Administrator Setup:
    • Provide email, username, and secure password for the first System Administrator.
    • Designate your workspace team name.

2. Configure Origin Modules (System Console)​

  1. Navigate to System Console → Origin Modules:
    • Origin Calls: Set WebRTC listening port (8443) and STUN/TURN credentials.
    • Origin Boards: Configure card attachments and workspace board sharing.
    • Origin Workflows: Set up team checklist runbooks.

3. Configure Outgoing Email Relay​

  1. In System Console → Email Settings:
    • Set SMTP Server hostname, port (587 STARTTLS or 465 TLS), and authentication credentials.
    • Send a test email to verify delivery.

Copyright © 2026 Origin by Corvus • Quantum Tiger (Morning Bay Technology Pvt. Ltd.). All rights reserved.