FlowOS Automation HubPlain-English product documentation

Server owner or platform administrator

Install FlowOS without guessing through the eight-step wizard

The installer is a controlled setup sequence, not a substitute for server preparation. Decide the public URL, central login domains, tenant-domain approach, database names, mail delivery, and first administrator before opening /install. Correct failed requirements instead of bypassing them.

Outcome
You will finish a clean installation and reach a secure first-login handoff.
For
Server owner or platform administrator
Time
30–60 minutes

Before you start

  • PHP 8.2 or later and required extensions.
  • A MySQL-compatible server and credentials allowed to create the central schema.
  • An HTTPS domain, writable storage, Composer dependencies, and compiled front-end assets.
  • A plan for one supervised queue worker and a scheduler that runs every minute.
Install FlowOS without guessing through the eight-step wizard diagram
Install FlowOS without guessing through the eight-step wizard — a text description is included inside the diagram and in the surrounding section.

#Step 1: verify server requirements

Open /install. The first screen checks PHP, extensions, folders, and environment readiness. Use “View full report” for the exact failing item. Folder permissions should be only as broad as your hosting environment requires; do not solve a write error by making the entire application world-writable.

#Steps 2–3: set identity, domains, and database

  1. Set the application name and the exact HTTPS base URL.
  2. Enter central domains used for platform and tenant-resolution decisions.
  3. Choose the intended tenant suffix or custom-domain model.
  4. Test the central database connection before saving it.
  5. Use a clean schema; do not point the installer at an unrelated database.

#Steps 4–7: services, channels, administrator, and brand

Configure required database setup, mail and optional channels, then create the first administrator with a unique password and recoverable email. Add brand assets that remain readable on light and dark surfaces. Optional providers can stay disabled until their credentials and callback URLs are ready.

#Step 8: finish and lock installation

Read the summary, complete migrations, lock the installer, and follow the first-login link. Confirm that revisiting /install no longer exposes setup actions. Store recovery information outside the web root and remove temporary archives.

Resolve every failed requirement before continuing. Capture details
Use the final HTTPS URL and deliberate central-domain values. Capture details
Test a clean central database connection before migrations. Capture details
Create a recoverable first platform administrator. Capture details
Preview readable brand assets before saving. Capture details
Lock the installer before the first production login. Capture details

#Common mistakes

  • Using an HTTP URL and planning to “fix HTTPS later.”
  • Using one database for central and tenant data.
  • Uploading a local .env containing development secrets.
  • Leaving the installer available after setup.

#Verify the result

  • All requirement checks pass.
  • The public URL and domains match DNS and SSL.
  • The installer is locked.
  • Central and tenant login behavior is ready to test.
Enlarged documentation screenshot