For AI agents: a documentation index is available at /llms.txt. A markdown version of this page is available at /guide/self-hosted/install/deployment-options.md.
Deployment options
Containers or a traditional Apache/Nginx install — what each involves and how to choose.
Orangescrum Enterprise ships two supported deployment models. Both run the same application; they differ in how you manage the runtime.
A docker-compose.yml and Dockerfiles are provided. You get a known-good PHP
build, the reporting stack wired up, and a migration story that is mostly
moving volumes.
PHP-FPM behind Apache or Nginx, PostgreSQL as a system service. Choose this when your organisation standardises on VMs and configuration management rather than containers.
#Choosing
Pick Docker if…
You want the shortest path to a correct runtime, you plan to use the Advanced Dashboard (which needs Superset and its own database), or you expect to migrate between servers. The backup and migration procedure is written for this model.
Pick traditional if…
You have existing Apache/Nginx and PostgreSQL infrastructure, hardened OS images, or a policy against containers. Everything works — you just own more of the runtime.
Can I mix them?
Yes. A common arrangement is the application in containers with PostgreSQL as an external managed database, so backups and failover are handled by your existing database tooling.
#What differs in practice
| Docker | Traditional | |
|---|---|---|
| PHP version and extensions | In the image | You install and maintain them |
| PostgreSQL | Container or external | System service or external |
| Advanced Dashboard (Superset) | Included in the stack | Deployed separately by an admin |
| Upgrades | Pull images, run migrations | Pull code, composer install, build assets, run migrations |
| Backup | Volumes plus pg_dump | Filesystem plus pg_dump |
| Migration | Move volumes and secrets | Rsync files, restore database |
Superset is not optional for reporting
The OS Report / Advanced Dashboard module only appears once Superset is installed and connected to your Orangescrum data. On a traditional install an administrator has to deploy it; the container stack includes it.
#Version guidance
The two models have historically carried different documented floors:
| Component | Current prerequisites | Older traditional-install guidance |
|---|---|---|
| PostgreSQL | 16.10 or above | 12 or above |
| PHP | Bundled in image | 8.2 or above |
Deploy against the current prerequisites
Target PostgreSQL 16.x unless Orangescrum support specifies otherwise for your licence and version. The lower floor reflects older releases, not a recommendation for a new install. Full detail in Prerequisites.
#Before you install
Meet the prerequisites
Hardware, OS, PostgreSQL and network. See Prerequisites.
Point your domain at the server
The hostname is baked into generated links.
Have your licence email ready
The installer validates it before it will proceed.
Have SMTP details ready
Mail is configured during the install, not afterwards in the UI.
#The package
Exact commands, migration specifics and environment-tuned troubleshooting ship as the Installation & Upgrade Guide included with your package. This section covers the shape and the operational procedures; where the two disagree, your package guide is authoritative for your version.