Stable redirect URL for a public file/share to always point to the latest uploaded VZDUMP archive (Proxmox)

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.

We are using a Nextcloud-hosted VZDUMP archive for automated Proxmox VM installation scripts.
At the moment the script depends on a fixed file URL, for example:
https://download.kafit.se/public.php/dav/files/8w43PHG3cKoz5ZK/vzdump-qemu-999-2026_07_07-11_56_12.tar.zst

This is fragile because every new backup upload changes the filename and therefore breaks the script. We need a stable URL that always points to the newest archive.

The old tteck Nextcloud VM script was based on a TurnKey Linux image. Unfortunately that approach is now so outdated that the VM no longer starts reliably, which is why we are currently building a new version based on the newer Proxmox VM workflow.

Because of that, a stable redirect URL for the current VZDUMP archive would be especially helpful for keeping the new automation maintainable.

Describe the solution you'd like
It would be great if Nextcloud could provide a permanent URL or redirect alias for a public file/share that always points to the latest uploaded file in a folder, or to a designated “current” file.

For example, a stable endpoint like /latest.tar.zst could always redirect to the newest backup archive.

Describe alternatives you've considered

• Manually updating the script URL after every backup upload (may every week?)
• Using an external web server or reverse proxy to maintain a stable redirect
• Hosting the file outside Nextcloud and updating it via automation (bad idea..)

Additional context
This is used for Proxmox VM installation scripts that download a preinstalled Nextcloud VM backup

A stable redirect would make the automation much more reliable and avoid unnecessary maintenance.

Current DEV Script with hardcoded URL:
https://github.com/community-scripts/ProxmoxVED/blob/main/vm/nextcloud-vm.sh

Start with vm/nextcloud-vm.sh, which contains the current hardcoded public archive URL, and review how the script downloads the backup. Compare that workflow with the requested stable endpoint or redirect alias. Done means a public URL can consistently retrieve the latest designated VZDUMP archive without manually updating the script.