Keeping Coduva up to date
Coduva checks for new versions itself and notifies you. It does not install the update on its own: installation starts only when you click the Install and restart button, and only officially released packages whose signature has been verified are installed.
Closed beta: the update server is not live yet
In-app updates are ready in version 0.2.0, but the updates.coduva.dev server where updates will be published is not live yet. Until it is, checks return no result and the Check for updates button shows "Could not reach the update server". This is expected; Coduva and your services are not affected. During the beta, install new versions manually.
When are checks made?
- About 20 seconds after Coduva opens, it runs the first check; this does not slow down startup.
- After a successful check, the next one is at least 24 hours later. Even if Coduva stays open in the tray for days, it checks at most once a day.
- If the server cannot be reached (for example, you are offline), it retries after 6 hours. This is not treated as an error and is not written to the event log.
- There is one channel: Stable.
When a new version is available
A new version appears in three places:
| Where | What you see |
|---|---|
| Bottom-right corner | A Coduva x.y.z is available notification balloon, with the text "Install it from Settings › Updates." |
| Status bar | An Update: x.y.z badge. Clicking it opens the Updates card on the Settings screen |
| Settings › Updates | The Coduva x.y.z is available heading, your installed version and release date, with Release notes |
The same version is reported only once per session.
Installing the update
- In the Updates card under Settings › Updates, click Install and restart.
- The package downloads; progress shows on the button (Downloading… 42%).
- The package signature is verified. If the signature does not match, installation does not start and an error is reported.
- Running project processes (queue worker, scheduler, Vite) are stopped.
- Coduva closes. The installer shows only a progress window and does not ask you anything. When installation finishes, Coduva reopens.
Nginx and MariaDB keep running during the update, so your sites stay up. After the update, restart the stopped project processes from the project's Processes tab.
Your settings, projects, components and databases are not affected by the update.
Configuration in a new version
If the new version changes the Nginx, PHP or MariaDB configuration templates, Coduva regenerates the configuration on first launch and reloads the running Nginx without interruption. You do not need to restart the services manually.
Security
- Signed packages only. Every package is signed with Coduva's signing key; the public key needed for verification is included in the app. A package whose signature does not match is not installed.
- The signature is tied to the version. The signature also covers the package's version number, so a signed package from an older version cannot be presented as a newer one.
- HTTPS only. Checks and downloads are made only over
https://updates.coduva.dev. - No installation without approval. Coduva only checks in the background; download and installation start with your click.
What does the check send?
A check is a single HTTPS request for the file https://updates.coduva.dev/stable/latest.json. The address and the request contain no information about your Coduva version, your computer, your projects or your usage. As with any web request, the server sees only your IP address.
When you install an update, the package is downloaded from https://updates.coduva.dev/stable/<version>/. Details: Security and privacy.
Turning off automatic checks
Turn off the Check for updates automatically toggle in the Updates card under Settings › Updates. After that, Coduva performs no checks on its own. You can check manually at any time with the Check for updates button.
The bottom line of the card shows Installed version, Channel and Last check.
Manual update
Until the update server goes live, or if you have turned off automatic checks, you can install a new version manually:
- Get the installer for the new version (
Coduva_<version>_x64-setup.exe). When general distribution starts, packages will be published on the download page. - Close Coduva: right-click the tray icon and select Quit.
- Run the package. It installs over the existing installation and does not require administrator permission.
Your settings (%APPDATA%\Coduva), components, projects and databases (C:\Coduva) stay as they are. The program itself is in the %LOCALAPPDATA%\Coduva folder.
Components
The versions of Nginx, PHP, MariaDB and the other components come from the component list inside Coduva. A new Coduva version may change this list, but a Coduva update does not change installed components automatically. See Components.
For changes, see the Release notes page.