Foundry Virtual Tabletop

[TheMeerkat]

@BrutalBirdie Thank you!

[TheMeerkat]

@LoudLemur There's higher standards for official apps. Right now, it's only really updated whenever I poke BrutalBirdie for one because the PF2E app needs the latest version to work.

[BrutalBirdie]

Updated the app to version 13.351.

• GitHub: https://github.com/BrutalBirdie/cloudron-foundryvtt/releases/tag/13.351
• Dockerimage: https://hub.docker.com/repository/docker/brutalbirdie/foundryvtt.cloudron.app/tags/0.1.1/sha256:3f1c96849458265eecb4edea58532f686eb644eda1f4533b3995bd007a9e7f9a

Update:

cloudron update --app $YOUR_APP_LOCATION --image brutalbirdie/foundryvtt.cloudron.app:0.1.1

[BrutalBirdie]

Updated the app to version 14.359

version 14.359 is still very fresh. If you use a lot of community modules they will probably break.
So only update to version 14.359 if you made sure your community modules are working for the new version.

---

You can now use the CloudronVersions.json to install the FoundryVTT Community App.
If you have installed the app in the old style, you won't get automatic updates and need to update the old style way.

• pull the GitHub repo: git pull git@github.com:BrutalBirdie/cloudron-foundryvtt.git && cd cloudron-foundryvtt
• cloudron update --app $YOUR_APP_LOCATION --image brutalbirdie/foundryvtt.cloudron.app:2.0.1

The easy way to "migrate" from the old installation style to the new community app style would be:

• update manually to the latest version
• create a backup
• download the backup config
• uninstall the app
• install the app from the app store with the CloudronVersions.json
• restore your backup

Now you should get automatic app updates when I release a new version.

[LoudLemur]

Hello, @brutalbirdie ! When you have a moment, it would be great if you could update the Foundry community package again, please.

Here's what a bump from 14.359 to 14.365 actually brings (it spans roughly three months of stable-channel fixes, ending with "Version 14 Stable 7" from July 15):

• 40+ bug fixes in the final release alone, concentrated in the areas that hurt during actual play: token/region interaction workflows, canvas visibility and wall collision detection, movement snapping during elevation changes, chat UI behavior, and audio/video device configuration (that last one matters for in-game voice/video between players).
• Quality-of-life features for GMs: multi-object dragging for tiles and drawings, refined keyboard movement (XY and elevation separated), and better occlusion handling.
• API improvements (compendium art mapping, new canvas/elevation methods, new hooks). This is the quiet big one: module authors target the current stable, so starting a fresh install on 14.365 means the module ecosystem you build your worlds on is tested against what you're running, and you avoid accumulating "works on newer builds" incompatibilities from day one.

The headline item of 14.365 is Apple/Windows installer code-signing, which only affects desktop installs.

[BrutalBirdie]

If you have the community app version installed a new update should be available soon.

[LoudLemur]

@BrutalBirdie Thanks! It installed beautifully

[LoudLemur]

Feedback notes for BrutalBirdie's Foundry VTT Cloudron package

Observations from a fresh 2.0.2 (Foundry 14.365) install on Cloudron 9.2.0, 2026-07-27.

Thank you for bumping to 14.365 the day before we installed!

What worked well

• Install via CloudronVersions.json versions-url was flawless: image pull, subdomain, proxy, health check all clean, first try.
• Websockets work out of the box through Cloudron's proxy (socket.io game sessions verified).
• Health check path / (returns 302 → /license or /join) is accepted fine by Cloudron.

Suggestions

1. Seed proxy settings on first run. A fresh install has hostname: null, proxySSL: false, proxyPort: null in /app/data/Config/options.json, so Foundry's invitation links point at an internal address. The start script could seed hostname=${CLOUDRON_APP_DOMAIN}, proxySSL=true, proxyPort=443 when options.json is first created, correct https invite links out of the box, zero user action.

2. Unauthenticated setup window. Until the owner sets an admin key and/or launches a world, /license and /setup are reachable by anyone on the public subdomain: a drive-by visitor could enter their license key, install/delete packages, or change server config. Options: generate a random admin key at first start (drop it in /app/data where the owner can read it via the Files view, and mention it in the README/post-install message), or at least document the exposure prominently.

3. Run as non-root. start.sh and the node process run as root (PID 1). Cloudron convention is to drop to the cloudron user (gosu) after fixing ownership; Foundry doesn't need root at runtime. Straightforward hardening win.

4. Disable UPnP. Default upnp: true is useless inside a Cloudron container (and can add startup noise/delay). Seed upnp: false alongside the proxy settings.

5. Memory guidance in the description. The 1.25G default is fine, an idle D&D5e world uses ~230MB, but a line in the package description telling users with big module-heavy worlds to raise the limit would preempt OOM confusion.

Data points

• Package manifest facts verified in practice: httpPort 30000, localstorage only, minBoxVersion 9.1.0 on box 9.2.0.
• Config/Data/Logs layout under /app/data works with Cloudron backups as-is; license survives restarts; a startup world (world option) survives restarts and relaunches automatically.

Why isn't this package an official application on Cloudron yet?

[BrutalBirdie]

HeyO @loudlemur

1. 
2. I get it, but also kinda don't care
   If someone installs the app and does not enter his license key and someone random does, just reinstall or reset the license.
   Since you need to pay for a license, and it is only allowed to be used on one server, entering your license key on a random server?
   If someone does that, you suddenly have a paid vtt. Only issue is other paid modules connected to the license itself.
3. 
4. 
5. 

@LoudLemur said:

Why isn't this package an official application on Cloudron yet?

Looks like your AI could not really explain that one ayy?
Missing tests but more importantly, to build the app you need a license for FoundryVTT.
Without a bought license you can't even download the application.
So every update, I have to log in to their website, download the zip and build the app manually.
The direct download is from the account page is token based, and every click is a one time download.
There is also the timed URL option for downloading, which is also bad since it is only valid for a certain time.
So package updates can't even be automated.
I even talked to the support of FoundryVTT if we could get an endpoint to always download without a license like their other partners https://foundryvtt.com/article/partnerships/, but the response was I'd have to apply for a partnership and when asked "how do I apply for a partnership?" they simply ghosted me.

So all this makes it a bad candidate for the official app store.

[LoudLemur]

@BrutalBirdie said:

Looks like your AI could not really explain that one ayy?
Missing tests but more importantly, to build the app you need a license for FoundryVTT.
Without a bought license you can't even download the application.
So every update, I have to log in to their website, download the zip and build the app manually.

Ah! Thank you. That explains it.
By the way, while we are on the Foundry topic, apparently the Pathfinder / Starfinder Archives of Nethys repo is no longer being supported by Paizo, I read recently. I am not sure why they decided to end that.