caddy-docker VS foundryvtt-docker

The official Caddy documentation of their Docker image: https://hub.docker.com/_/caddy

I use https://static-web-server.net/

Cross-platform, written in Rust, straightforward configuration, secure defaults, also has a hardened container image and a hardened NixOS module.

I wouldn't recommend Caddy. Their official docker image runs as root unnecessarily (and the reasoning suggests a lack of understanding) [1], and they don't provide a properly sandboxed systemd unit file [2].

[1]: https://github.com/caddyserver/caddy-docker/issues/104

There is also a short section about it on the Docker hub page under the "Adding custom Caddy modules" section: https://hub.docker.com/_/caddy

Caddy uses a number of volumes. Two point directly at files within our project, first our Caddyfile, then our public folder which Caddy will serve live files. The other two are virtual filesystems Docker will create as defined by the master volumes parameters. We can assume the caddy_config volume is where active configuration is stored as it is not discussed on the Caddy Docker Official Image page, so we're copying their parameter exactly, but the caddy_data volume needs some extra discussion. It is used to store a number of things including SSL certificates. By default Docker creates and destroys volumes upon startup and exit. As we want to persist our certificate across sessions we can take advantage of an external Docker volume. These virtual filesystems are created before starting the Docker session for the first time. This can ve done from the command line or more easily from within the Docker Desktop app. Simply choose "Volumes", click the "Create" button and specify caddy_data.

I've been able to create a network with no issues (that I know of yet) but when I try to create the volumes I run into trouble. This specific example is from Caddy2...

For a reverse proxy I would suggest Caddy. The configuration is super easy and it handles SSL for you out of the box using LetsEncrypt! There’s also an official docker image like PHP and MySQL here https://hub.docker.com/_/caddy

Their image is dead simple to use, the config is fine, and auto-https is baked in. You can use it as a sidecar, proxy for multiple images, or just as a base to add your app into, depending on the complexity of your existing config.

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