foundryvtt VS foundryvtt-docker

There's a very loose list of planned improvements being tracked here, but we have an internal document that's more focused and clearer, I just need to take the time to convert it into issues for our tracker.

That said, we are looking at ways of improving compendium functionality like adding long sought after compendium folders and even creating modules (and their compendium packs) from inside Foundry VTT without needing to set up the manifest files by hand. We also want to continue expanding on our currently implemented adventure functionality and explore new approaches for how he we might incrementally deliver content in worlds rather than handling them as a bulk transfer which includes things like redesigning our low-level approach to data storage.

For convenience, if the authorization menu is not available users will now be redirected to the login screen for the currently active world. (6900)

This will likely be addressed in v10 https://gitlab.com/foundrynet/foundryvtt/-/issues/4621

Disabling the Scene's "Token Vision" setting will now properly remove the LOS mask from ambient light rendered on the Lighting Layer. (6797)

The ChatMessage#logged property has been added and indicates whether or not the message currently appears in the ChatLog. (6796)

Log files now also indicate which build number of the software is running, not just the Version number. (6620)

As for the documentation and alerts in the UI, well, https://gitlab.com/foundrynet/foundryvtt/-/issues/6500 is assigned and should be ready for testing in the first prototype release. I'm pretty excited to get it set up for the PF2e system. Tutorials for new players and GMs sound awesome.

Updated pixi/graphics-smooth to fix rectangle masks and holes. (6493)

Also using the felddy/FoundryVTT, nginx reverse-proxy, and lets-encrypt companion Docker containers.

I already have docker set up for Nextcloud, so threw on this guy, hooking into my existing reverse proxy+letsencrypt https://hub.docker.com/r/felddy/foundryvtt

What can you do 1. Set the default game world in Foundry configuration, that way you won't have to bother with selecting it after restart 2. The docker image has a healthcheck defined, but to my knowledge only Swarm makes use of it, every other orchestrator requires this to be defined separately. Look into azure docs to see how to define it. Have it test the whatever-is-your-url/api/status, compare the script here - this will auto restart the container if it hangs

I'll link to the github discussion I opened, rather than copy/pasting it all here: https://github.com/felddy/foundryvtt-docker/discussions/676

I'm getting ready to run a campaign for some friends using Foundry. To do this I'm running Foundry in a Docker container (https://hub.docker.com/r/felddy/foundryvtt) running on a NUC at my house. I then use NAT to forward the required ports through my firewall so the other players can access it. It sounds more complex than it really is, and I'd be happy to answer any followup questions!

The use-case is as follows; I'm hosting Foundry Virtual Tabletop in a docker container on my NAS for a friend. He does all of his prep work using the copy of Foundry VTT on his personal computer, and then uploads to the NAS using Filebrowser, which I have also set up in a docker container, giving him only access to the Foundry VTT data directory and subdirectories.

I am using this docker image: https://github.com/felddy/foundryvtt-docker I'm getting this error in the console `WebSocket connection to 'wss://foundry.****/socket.io/?session=***&EIO=4&transport=websocket' failed: WebSocket is closed before the connection is established.`

I also run a minecraft server or two from time to time, and three separate instances of Foundry Virtual Tabletop for friends.

I used Mark Feldhousen's foundryvtt-docker docker image for the foundry server, using docker compose: https://github.com/felddy/foundryvtt-docker