Move from a wiki-style install

The community wiki’s Linux installation guide keeps user data in ~/foundryuserdata and runs Foundry with pm2. To move to foundry-ops, install fresh and copy only your user data across.

1. Install foundry-ops in a new container, with the same Foundry version as the old server or a newer one.

2. In the new container, stop Foundry:

   systemctl stop foundryvtt

3. Copy the old Data/ and Config/ folders from ~/foundryuserdata on the old server into /var/lib/foundryvtt/ in the container, replacing the ones there.

4. Give them to the foundry user and start Foundry:

   chown -R foundry:foundry /var/lib/foundryvtt
   systemctl start foundryvtt

5. Check Config/options.json. An old dataPath or port there overrides nothing, but proxySSL and hostname come across as they were, so make sure they suit the new setup.

foundry-ops follows the wiki guide’s steps, with a few differences:

Wiki guide	foundry-ops	Why
pm2 under a user with sudo	A systemd unit and a foundry system user without sudo	Native to a container; nothing needs sudo while it runs.
nvm for Node.js	NodeSource packages, with the version read from Foundry’s package	Survives updates. Foundry 14 needs Node.js 24, and earlier versions break on it.
~/foundry and ~/foundryuserdata	/opt/foundryvtt/app and /var/lib/foundryvtt	The community-scripts convention, and the data path is easy to mount separately.
Caddy on the same host	Your own reverse proxy	Homelabs usually run one already (optional Caddy is planned).
A fixed path to main.js	Found at each start by the launcher	It moved between Foundry 12, 13 and 14.
UPnP on	UPnP off	A container shouldn’t open ports on your router.

See Layout for where everything is.