Update and roll back

foundry-ops updates Foundry with the update command inside the container. Like the install, it downloads your own copy with a fresh Timed URL.

Update Foundry

Back up the container.
Open a shell in the container, from its Console in the Proxmox web interface or with pct enter <ctid> on the host, and run:
Terminal window
```
update
```
Check the installed version it shows, and answer whether to archive your user data first. It shows how much there is; the default is yes.
Paste a fresh Timed URL for the Node.js package, from Purchased Licenses on foundryvtt.com.
Wait while it updates. It installs the Node.js the new version needs, stops Foundry, archives your data if you said yes, swaps in the new version and starts Foundry again. It finishes by saying where the previous version is.

To update without prompts, set FOUNDRY_SOURCE to the Timed URL and FOUNDRY_BACKUP to yes or no (see Unattended install).

What an update keeps

The previous version, in /opt/foundryvtt/app.prev. There’s one slot: the next update replaces it.
An archive of your user data, if you said yes: Data/ and Config/ in /var/backups/foundryvtt/foundryvtt-data-<date>_<time>.tar.gz. Archives are not removed automatically, so delete old ones when you no longer need them.

Roll back the app

This puts the previous version of Foundry back. It doesn’t undo worlds the newer version has already migrated; for those, restore the container backup.

systemctl stop foundryvtt
mv /opt/foundryvtt/app /opt/foundryvtt/app.bad && mv /opt/foundryvtt/app.prev /opt/foundryvtt/app
systemctl start foundryvtt

After a rollback, /opt/foundryvtt/version still names the newer version, since the commands above don’t change it.