John Cardinal
91e8f54074
The upgrade overview page has a section for upgrades from 8.2.4 or older, and the 8.3.1 changelog section opens with a line pointing to it (the "new version available" notice links to the newest section); the release procedure's version bump now carries that line into each new section. Both Linux upgrade scripts first check for the .NET 10 ASP.NET Core runtime and stop with nothing changed if it is missing (tested on devtest: present, dotnet not found, only an older runtime). The desktop script's download now uses curl -f, as the server's does since case 4727, so a failed download stops before files are removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.6 KiB
AyaNova linux desktop platform upgrade
The linux desktop upgrade process involves replacing the AyaNova program files with the latest version and restarting the AyaNova server.
These instructions assume the original installation steps were followed without changes and Ubuntu or compatible distro was used, if you had to make changes or have an alternative distro adjust accordingly.
Expired Maintenance plan
If you do not have an active Maintenance plan updating will BREAK your AyaNova application.
1. Backup
Before proceeding, make a backup of the database and the attachment files and store it in a safe place.
If you do not have a fresh backup there will be no way to recover from potential data loss or damage.
2. Stop the AyaNova server
To shut down the AyaNova server cleanly use the AyaNova web app form accessed from Server Operations -> Server State and the menu item Shut down server.
Alternatively you can hard shut down AyaNova using the ctrl-c key combination in the terminal console window where AyaNova is running however this is not recommended.
2.5. Pre-upgrade step
Only if your current AyaNova version is older than 8.3.0 there is an extra step before the normal upgrade process.
8.3.0 switched to .NET 10 LTS from the prior used .NET 8 LTS (8.2.0 to 8.2.4), so the .NET 10 runtime must be installed first.
From a terminal window run the following commands:
sudo apt-get update && sudo apt-get upgrade && \
sudo apt-get install -y aspnetcore-runtime-10.0
On Ubuntu 24.04 and 26.04 the .NET 10 runtime comes from Ubuntu's own package archive. On Ubuntu 22.04 first add the Ubuntu .NET backports package repository with sudo add-apt-repository ppa:dotnet/backports.
If there is an issue or error break apart the commands and execute each one individually to find the error.
After this step has completed you can continue with the normal upgrade process in the next step.
3. Upgrade
upgrade script
The following shell script will automatically remove the old AyaNova files, download and unzip the latest AyaNova files then start the server. It first checks that the .NET 10 runtime is installed and stops without changing anything if it is not (see the pre-upgrade step above). If the download fails, it also stops before any files are removed.
From a terminal window run the following commands:
cd /opt/ayanova && \
{ dotnet --list-runtimes | grep -q '^Microsoft.AspNetCore.App 10\.' || { echo "The .NET 10 runtime is not installed: do the pre-upgrade step first. Nothing was changed."; false; }; } && \
sudo curl -fO https://www.ayanova.com/download/ayanova-linux-x64-desktop.zip && \
sudo rm *.dll && \
sudo rm -r ./resource && \
sudo rm -r ./wwwroot && \
sudo unzip -o ayanova-linux-x64-desktop.zip -x "config.json" && \
sudo chmod 777 ./AyaNova && \
sudo ./AyaNova
If there is an issue or error break apart the commands and execute each one individually to find the error.
From 8.3.0 the Chrome report rendering engine is downloaded into a report-browser folder under the data directory instead of the program folder. After upgrading from an earlier version any old Chrome and ChromeHeadlessShell folders in the AyaNova program folder are no longer used and can be removed.
AyaNova should restart on it's own and perform any database schema updates if required automatically.
Open the login form in your browser and after a short delay you should see the new version number at the bottom of the login form.