Plan a company rollout

Install and operate your release

The customer release includes explicit Install, Start, Upgrade and Status commands through ./zublms. This initial installer targets the external-services profile: PostgreSQL, identity, OpenBao, the recovery journal, storage permissions and DNS must already be provisioned. It does not automatically adopt an existing development or VPS installation.

Install checks the target and runs setup in temporary containers. Start uses the existing installed release without applying migrations. Upgrade requires a verified recovery-checkpoint record, stops application traffic and workers, migrates, then checks the matching release. Status is read-only. Setup logs are retained privately even when temporary containers disappear.

A failed migration blocks ordinary startup; it does not delete data or silently roll back the database. Open the related Install, start & upgrade ZubLMS guide for the public command walkthrough. The full operator runbook is also supplied as docs/customer-installer.md. Automatic key-service unsealing and off-server backup creation remain separate operational work.

./zublms install --env-file /path/to/private/release.env --project zublms-example --plan

Define the pilot

1. Choose a company owner, learning owner and technical contact.
2. Agree learner numbers, required roles and company boundaries.
3. Select a small representative course set and a reference resource.
4. Agree measurable learning and operational acceptance criteria.

Test the whole journey

• Sign-in and sign-out, including company SSO if required.
• A learner taking a course on a phone and a desktop.
• An author publishing a new version without rewriting existing learning records.
• A manager assigning training and downloading an authorised report.
• An owner reviewing access and activity.
• Denied cross-company access and revoked permissions.
• Email delivery and recovery exercises once those capabilities are implemented and configured.

Agree what is included

Confirm integrations, content migration, branding, domains, mail, support hours, retention and recovery responsibilities in the rollout scope. Pricing and service terms are agreed separately; the website is not an automated subscription or billing portal.

The operator-only Platform console provides a searchable company directory and detail pages for profiles, policies, governance and support. Self-service company onboarding, subscription management and billing remain future work. Company settings manages the active company.