Install PCMO on your own domain

Prepare a new installation

Use a fresh directory and a new empty MySQL 8.0+ or MariaDB 10.6+ database. Check the full PHP and hosting requirements, enable HTTPS and include the release's .htaccess rules.

Do not extract over an existing workspace or import its schema manually. Confirm that private application directories return 403/404 when requested directly. The fresh installer is not an upgrade or migration tool.

Open browser setup

1. Complete preparation and genuine activation, then choose that active installation in your organisation's Product downloads and obtain the entitled signed product ZIP.
2. Configure ORBIT_LICENSE_CONFIG for web PHP to use the preparation directory's config.json. Preserve that same private identity; do not create another installation key during setup.
3. Extract the complete signed release, including its enclosing pcmo/ folder and hidden files.
4. Open /install.php on your PCMO HTTPS domain.
5. Use hosting File Manager to read storage/setup/setup-key.txt inside PCMO.
6. Paste that one-hour private key into the setup form.

After the separate licence-preparation step, database and owner setup use the browser. If the setup key expires before installation, remove only the uninstalled config/setup-key.php and storage/setup/setup-key.txt, then refresh setup. Never remove an installed configuration or lock to force setup.

Choose your owner

Enter the canonical URL, organisation, timezone, dedicated database details and a new owner account. Choose a 12–72 byte password. There is no default owner or password.

The installer refuses nonempty databases and existing configurations. On success it removes the setup-key files and locks itself. The optional starter checkbox creates generic teams and a generic template rather than customer work records.

Sign in with your owner and check the status of the already activated identity. If PCMO asks to prepare a new key, check the web PHP ORBIT_LICENSE_CONFIG setting and private-directory ownership first. Review local users, business settings and templates. SMTP and other external services need your own configuration.

Optional terminal setup

These commands remain available from the application directory as its PHP user:

php bin/install.php --check
php bin/setup-key.php

The second command prepares a private key for browser setup. The release's installation guide also documents advanced private JSON input. Keep passwords out of command arguments and remove temporary input files after use.

Back up the database, private storage and config/app.php together; retain the original application key. Follow the exact release's interrupted-setup instructions rather than resetting a database containing real work.