foundryvtt-docker VS FoundryVTT-Server-HowTo

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

I've been trying to set up an fvtt server using this guide. I followed the guide until HTTPS_SSL_certbot under Hosting_to_the_world and until this point, I could get access to the site. To use certbot I've followed the certbot instructions for a wildcard on nginx using Cloudflare.

This guide was pretty helpful but it involves the need to purchase a vps. The free options above are nearly identical. All about preference I guess.

https://github.com/meeki007/FoundryVTT-Server-HowTo#Install_Nginx

I've only ever run the server headless, but in Debian 10 so the command structure is a little different. Mostly followed https://github.com/meeki007/FoundryVTT-Server-HowTo (Ubuntu instructions) but added installing curl up front, not using pm2 (enabled the process as a systemd service), and not using nginx just because I wanted the least number of moving parts that could break. Installed first in a small VM on my home ESXi server, then rented the smallest (1vCPU/1GB/25GB) droplet at DigitalOcean when it became apparent the real choke point was upstream bandwidth. Don't forget to configure UFW (or iptables directly if you're a masochist).