Updating from the web interface
Once Voiplix is installed, new versions are installed the same way, from inside the product — no terminal needed. Here is how you're told about one, what happens when you start it, and how long it takes.
How you find out
When a newer version is available, administrators see a banner pointing at System update. You can also check directly at any time: in the sidebar, go to System > System update and select Check for updates.
If nothing newer is published, the page simply says System is up to date. If there is a newer version, the same card shows it — along with when it was published and which channel it's on — and starting the update is one more click away.
What you'll see while it runs
The update reports its own progress on the System update page as it goes, one labelled step at a time, in this order:
| # | Step |
|---|---|
| 1 | Downloading the new version… |
| 2 | Checking the download… |
| 3 | Unpacking the new version… |
| 4 | Keeping this server's own settings… |
| 5 | Checking that this server is ready… |
| 6 | Installing the parts the new version needs… |
| 7 | Preparing the database client… |
| 8 | Backing up the database before changing it… (only if this release changes the database) |
| 9 | Updating the database… |
| 10 | Building the new version — this takes a few minutes… |
| 11 | Saving a copy of the current version… |
| 12 | Switching to the new version… |
| 13 | Restarting the services… |
| 14 | Checking that everything is working… |
In plain terms: the update downloads and verifies the new release before touching anything, makes its own backups (see Backups before updates), only then switches over, and finally checks that the new version actually works — rolling back to the saved copy automatically if it doesn't.
How long it takes
Most updates finish in well under fifteen minutes. One that also changes the database, or needs a full rebuild of the application, takes longer — the step currently running (see the table above) is always visible, so you can tell it's progressing rather than stuck.
About the server restart
Many updates need a full server reboot afterward so that every service starts cleanly on the new version. The System update page has a Reboot automatically after every update setting: turned on, the server restarts by itself right after a successful update, with a short interruption while it comes back up. Turned off, you restart it yourself when convenient.
Before restarting the services, an update waits briefly for any calls currently in progress to finish, rather than cutting them off immediately — though it will not wait indefinitely.
If something goes wrong
If the new version fails its own final check, the previous version is switched back in automatically — nothing is lost, and the page tells you this happened. For what's saved beforehand to make that possible, see Backups before updates.
Reading the release history
The newest entry under Release notes is always open; every older version is a collapsed row with its own date — select one to read what changed in that release without leaving the page.
Check
After an update finishes, Installed version at the top of the System update page shows the new version number, and its entry in Release notes is marked "installed".