Upload
Upload the buyer ZIP or repository build to the intended app folder.
Shared install flow
Install Any Ovion App
Use this once for common Laravel/cPanel deployment. Some Ovion apps add product-specific installer steps, archives, finish gates, or demo seeders; those differences are listed here instead of repeated in every app manual.
8typical installer checkpoints
Point Root
Set the domain/subfolder document root to the app public/ directory.
Database
Create a database and database user, then apply the credentials in the installer or .env.
Verify
Run migrations/seeders, storage link, mail test, scheduler, queue, and app health checks.
Installer Checklist
- Confirm server requirements and writable folders.
- Set app name, URL, timezone, locale, and environment.
- Enter database host, database name, username, and password.
- Run migrations and required seeders.
- Configure mail channels and send a test email.
- Create the first administrator account.
- Apply branding and public URL settings.
- Finish, clear cache, sign in, and run product-specific verification.
Useful Commands
php artisan storage:link
php artisan migrate --force
php artisan optimize:clear
php artisan queue:work --tries=3 --timeout=90
php artisan schedule:runApp-Specific Installer Differences
Keep the common server and database rules above, then apply the row for the product being installed. If a product has a different installer behavior, document it here instead of creating another repeated installation page.
| App | Installer or package difference | After-install checks |
|---|---|---|
| OvionDesk AI | Uses an 8-step installer for requirements, app settings, database configuration, migrations and seeds, channels, admin account, branding, and finish. cPanel demo uploads use a private root/public split with oviondesk-demo-site-root.zip outside public_html and oviondesk-demo-site-public.zip in the public demo folder. Generated ZIPs are rebuilt from the app package when needed instead of stored in this docs tree. |
After login, run Reset Demo Data when preparing a buyer demo. Confirm OpenAI credentials, widget domain setup, SMTP, email inbox, queue worker, knowledge training, Envato verification, billing plans, reports, and marketplace readiness proof. |
| RevenuePilot CRM | Uses a dedicated 8-step wizard: requirements, app settings, database configuration, migrations and seeds, channels/runtime, admin account, brand assets, and finish. Steps 3-4 can take time on shared hosting, so keep the browser open while the database connection, migrations, and seeders run. The wizard can generate APP_KEY, write runtime defaults, configure queue/cache/session choices, set mail/channel defaults, create the first admin, apply branding, and lock the installer. |
Open CRM System Health after login. Confirm scheduler, queue worker, failed jobs, migrations, storage, mail, AI provider activity, webhook verification, backups, restore rehearsal, installed lock state, Admin MFA policy, and unsafe environment flags. |
| AttendPro | Installer adds workforce-specific important settings before setup runs: company basics, timezone, currency, security, AI options, SMTP/Twilio channels, workforce defaults, attendance behavior, and payroll mode. The setup runner applies those settings after migrations and seeders so installer choices override seeded defaults. It also covers environment/license, database, first admin, branding, masked review, and finish. | Continue with first-time setup: master data, branches/departments, employees and users, attendance devices/imports, leave rules, rosters, payroll periods, reports, and employee portal checks. |
| SupportDesk | For cPanel, the buyer package is split into supportdesk-root.zip and supportdesk-public.zip. Extract the private root to the cPanel home folder and the public package under public_html/supportdesk. The packaged public index.php resolves the private app root with the two-folder layout. The installer writes .env, APP_KEY, database credentials, APP_URL, CENTRAL_DOMAINS, and TENANT_DOMAIN_SUFFIX; do not upload a local .env or install lock. |
Open /operations-center/post-install and /operations-center/go-live. Confirm app URL, storage, mail, queue, scheduler, permissions, deploy smoke, release acceptance, AI/provider readiness, departments, ticket setup, organizations, contracts, and automation rules. |
| SupportHub | Uses a built-in installer at /install while the installer lock is open. cPanel installs use supporthub-root.zip for the private app root and supporthub-public.zip under public_html/supporthub. The public entrypoint resolves the private root, and the installer writes .env, APP_KEY, database credentials, APP_URL, CENTRAL_DOMAINS, and TENANT_DOMAIN_SUFFIX. |
Open post-install and go-live checks. Confirm storage link, queue worker, scheduler, mail, app URL, roles, departments, ticket setup, organizations, support contracts, automations, report schedules, delivery diagnostics, and AI/provider readiness. |
| FlowOS Automation Hub | cPanel installs use flowos-automation-hub-root.zip in the private home folder and flowos-automation-hub-public.zip in public_html/flowos. The public entrypoint resolves the private flowos-app root. The installer creates .env, APP_KEY, database credentials, the public app URL, tenancy domain settings, and the installer lock. Do not upload a local .env, Node dependencies, tests, package notes, or source documentation. |
Confirm first admin login, tenant provisioning, mail, queue worker, minute scheduler, signed webhook behaviour, strict health, backups, restore proof, and the static manual redirect before enabling Operations or provider-backed flows. |
| Operix | Uses a two-ZIP cPanel layout: Operix-root.zip extracts to the private app root and Operix-public.zip extracts to public_html/Operix. Vendor is included for shared hosting. The fresh installer must start without a local .env or storage/app/installed. The public index points back to the private app root. GitHub FTP updates after the first upload must keep vendor, .env, storage runtime files, local databases, logs, tests, deployment scripts, and node_modules out of the update payload. |
The finish gate checks central schema currency, clinic essentials, mail defaults, distinct admin/doctor/receptionist accounts, first-clinic tenant bootstrap, and plan catalog. Warnings cover SSO, Twilio, AI provider credentials, docs evidence, and smoke status. Existing single-clinic deployments use a separate upgrade path before multi-clinic operation. |
| BookFlow | Ships two install archive choices: a root install archive when the hosting root points at the project, and a public_html/booking archive for subfolder installs. Archives include Composer vendor and .env.example, but not live .env, full docs, marketplace screenshots, cache profiles, logs, or uploaded demo storage. The installer should use the current browser host so live subfolder installs do not redirect back to localhost. Set APP_URL, CENTRAL_DOMAINS, and TENANT_DOMAIN_SUFFIX for the final live domain model. |
Use php artisan bookflow:install-fresh --seed-demo --force only for intentional demo setup. Verify Nimbus tenant data, storefront, vendor admin, customer dashboard, wallet/payment flows, demo mailbox, scheduled reports, AI receptionist, integrations, bookflow:health-check, and bookflow:preflight --json. |
| Metrivo AI | Uses the built-in installer after the server, database, writable storage, PHP extensions, and app URL are ready. The install flow uploads or places the project files, opens the installer, passes requirements checks, enters database and mail settings, creates the administrator account, finishes setup, and locks the installer. | Confirm admin login, dashboard access, settings, company/branch setup, roles, permissions, storage, mail, queue/scheduler, import/export, reports, POS, and installer lock state before adding production records. |