Updating the Server/Client
Updating the application is a necessary task to add new features, correct security flaws, update packages to their latest versions, change packages that are no longer maintained or fix bugs.
Tip
The "Check for updates at startup" parameter must be enabled in the A.V.A.T.A.R Server and Client properties, so that updates are checked for on application startup.
For Windows platform only:
Check the PowerShell version, it must be 7.0 or higher.
Unfortunately, it is not possible to update the version supplied with Windows.
If the version is lower than 7.0, download the latest version of PowerShell and add the executable path in the field, as in the example above.
This message appears in the server or client interface when a new version is available:
Danger
If it's not already done, don't forget to make a backup copy of your plugins and property files before continuing (use the application's Backup/restore command).
An update is fully automatic and requires no manual action.
Click on the tab below according to the application you wish to update:
- Click on the "New X.XX version available!" message
-
In the message box, click on Update now!
-
A.V.A.T.A.R server closed
-
The PowerShell program starts (this may take a while, depending on the update type)
At the end of the update, the following message should appear in the PowerShell console
Warning
If this message does not appear, or if the server fails to start, an error has stopped the installation.
You can check the error on the terminal or in the app/tmp/update-<version>.log file. -
After restarting the Server manually, you can close the PowerShell console
- Click on the "New X.XX version available!" message
-
In the message box:
You have two possible choices:
- Update the client only
- Update all clients on the A.V.A.T.A.R network
- All clients will receive the update and run it automatically (clients must be connected)
Click your choice
-
A.V.A.T.A.R client closed
-
The PowerShell program starts (this may take a while, depending on the update type)
The update is in two parts:
- The first step starts (this may take a while, depending on the update type)
-
At the end of the first part, the following message appears in the PowerShell console
-
The client restarts and then closes
- A new PowerShell window opens and the second part of the update begins (this may take a while, depending on the update type)
-
At the end of the second part, the following message appears in the PowerShell console
Warning
If this message does not appear, or if the client fails to start, an error has stopped the installation.
You can check the error on the terminal or in the app/tmp/update-<version>-step1.log and app/tmp/update-<version>-step2.log files. -
After restarting the client manually, you can close the PowerShell console