Deployment Quickstart
The guided installers prepare a Docker Compose deployment, generate the local environment file, select a free host port, pull the requested images, and start the services. Run the script that matches the host operating system.
Prerequisites
The Unix installer also uses OpenSSL to generate local secrets. Keep the generated .env file private and out of source control.
Choose a mode
The interactive default is Lite. There is no Standard command-line switch, and --no-prompt or -NoPrompt accepts defaults, including Lite. Use the interactive mode prompt when installing Standard.
See Deployment Modes before choosing Lite for an environment that may later need connectors or indexed knowledge.
Install
Use a neutral installation directory through INSTALL_PREFIX; the examples below create opencore_data beneath the directory where the script runs.
macOS or Linux
From the repository root:
Windows
From the repository root in PowerShell:
The installers prompt for deployment mode and image tag, create opencore_data/deployment/.env, use basic authentication for a new deployment, and generate the local authentication secret. Common inputs are:
On Unix, --no-wait returns after the containers start instead of waiting up to 600 seconds for health checks. Do not treat that return as proof that every service is ready.
Verify services
-
From the directory where you ran the installer, inspect the generated deployment:
-
Confirm the expected containers are running. Standard should include OpenSearch and the search/indexing workers; Lite intentionally omits them.
-
Open the URL printed by the installer. It starts at
http://localhost:3000and selects the next free port when 3000 is already occupied. -
Open
/auth/signupon that host to create the first account. The first created user receives administrator privileges.
Upgrade
Stop the current deployment with the same installation prefix before changing its image tag.
Return to deployment/docker_compose in the repository checkout before running these commands.
macOS or Linux
Windows
When the installer finds the existing .env, choose update, select the target tag, and repeat the original Lite or Standard selection. Floating tags are pulled and recreated; a pinned tag also causes the installer to obtain matching deployment configuration when downloads are enabled. Verify service health again after the restart.