Protected deployment

Install and upgrade ExamNova

Install a fresh copy safely, lock the installer, and upgrade only after verification and recovery preparation.

Platform ownerHosting administrator

Who does thisPlatform owner

Before you startAll requirements pass and the empty database is confirmed

Successful outcomeA locked, working installation with a verified administrator login

Update and recovery flow. A release is verified and backed up before migration; database recovery uses a tested backup rather than reverse migrations.

What this means in plain language

A fresh installation creates the application tables and first administrator. An upgrade changes an existing installation. Never treat these as the same operation, and never use a failed install as permission to erase an unknown database.

Step-by-step

Upload application files outside the public webroot and place only the packaged public files in the domain’s public directory.
Open /install and authorize the installer with the supplied one-time installer secret.
Enter application identity, canonical URL, time zone, and first-institute information.
Enter the dedicated database credentials and run the connection test. Confirm the exact database name before continuing.
Configure mail now or select the documented deferred option; never invent production credentials.
Create the first administrator with a unique password and record the account owner.
Run setup, review every reported step, finish the installer, and confirm that the installer lock was created.
Sign in, open the dashboard, send a test message, and complete the post-install smoke checklist.

Installer application settings step — **Live seeded-demo screen.** The owner sets the canonical application identity.

Installer database configuration step — **Live seeded-demo screen.** The database connection is tested before migrations.

Installer completion step — **Live seeded-demo screen.** The installation is locked after successful setup.

Installer environment review — **Live seeded-demo screen.** The owner confirms the application environment before entering protected connection details.

Installer mail configuration — **Live seeded-demo screen.** Provider-neutral mail fields are checked without exposing a real password.

Installer first administrator — **Live seeded-demo screen.** The owner creates the first accountable administrator instead of a shared login.

Installer final review — **Live seeded-demo screen.** A final summary gives the owner one last chance to verify the target before setup runs.

How to know it worked

The login page opens at the canonical HTTPS URL.
The first administrator can sign in and sees the expected institute.
Reopening /install redirects away from the setup flow.
The dashboard, queue, scheduled work, mail test, and private file access pass smoke testing.

Common mistakes

Running the installer against an occupied schema.
Leaving debug mode enabled in production.
Applying an update before verifying its signature, compatibility, and backup.

If something goes wrong

For a failed fresh install, read the exact failing step and logs before retrying.
If the URL redirects incorrectly, verify the canonical URL and proxy configuration.
If an update fails after migration, use the documented backup restore path; do not guess reverse SQL.

Privacy and security: Installer secrets, database credentials, administrator passwords, update tokens, and backups are confidential. Screenshots must redact them.

What to do next

Complete first login, authentication, mail, and security configuration before importing real assessment data.