Installation
CVN PSA installs with one script, install.sh. It runs as root on a fresh Ubuntu or Debian server, installs everything the app needs and asks you a short list of questions.
Run the installer
-
Sign in to your account at account.cvntechnologies.com and open your CVN PSA licence.
-
Download
install.sh, or copy the one-line install command shown there. -
Copy the script to your server and run it as root:
sudo bash install.sh -
Answer the questions (listed below). The installer checks each answer before it moves on.
-
When it finishes, open your domain in a browser and sign in as the superadmin you created. Continue with First login and setup.
What it checks first
- The operating system is Ubuntu 22.04+ or Debian 12+. Anything else stops the install with a clear message.
- The server has enough CPU, memory and disk space.
- Which prerequisites are already installed, so it only adds what is missing.
What it asks for
| Question | Notes |
|---|---|
| Licence key | Redeemed against your account. This binds the licence to your domain. |
| Domain | The production domain your team and clients will use. |
| Database | Existing database credentials, or let the installer create the database and user. |
| First superadmin | Name, email and password. You are asked to set up two-factor sign-in at first login. |
| Company branding | Company name, logo and colours. Editable later in the admin portal. |
| Email (SMTP) | Host, port, encryption and credentials. The installer sends a test message. |
| Timezone and currency | The timezone drives every SLA calculation, so set it correctly. |
| Let's Encrypt | Optional. Gets and renews a free certificate for your domain. |
What it installs
- PHP 8.4 and extensions, MariaDB, Nginx and Redis where needed.
- Services for the queue worker and the websocket server.
- A cron entry that runs the scheduler every minute. Email-to-ticket, SLA checks, billing runs, reminders, backups and monitoring sync all depend on it.
- The prebuilt release bundle, with its PHP dependencies and built assets already included.
Re-running and failures
- The installer is safe to run again on the same server, for example after you fix a wrong answer.
- Every step is written to a log file. If something fails, the installer cleans up what it started and tells you where the log is.
Unattended installs
For scripted deployments, run the installer with --unattended and an answers file holding the same values the questions ask for. Keep that file private: it contains your database and SMTP passwords.