reverse-proxy-confs VS foundryvtt-docker

More reading: https://github.com/linuxserver/reverse-proxy-confs/tree/master

Linuxserver.io maintains a reverse proxy (SWAG) and they have a github repo of all the configs they support, nextcloud being one of them (ofc to do it on your own you have to merge a few of the includes they have ssl.conf, proxy.conf, etc).

According to this link, guacamole doesn't need an additional base url configuration as it already uses /guacamole by default: https://github.com/linuxserver/reverse-proxy-confs/blob/master/guacamole.subfolder.conf.sample

Glad to see you got it going. For future learning I'd recommend the sample nginx configs built by Linuxserver.io for SWAG, https://github.com/linuxserver/reverse-proxy-confs

Take a basic config, for example https://github.com/linuxserver/reverse-proxy-confs/blob/master/ghost.subdomain.conf.sample

I think swag also templates for those. You can check at https://github.com/linuxserver/reverse-proxy-confs if there is a subdomain conf for it.

Wow, this makes me appreciate linuxserver's mastodon docker so much more. Plug in your parameters and it just works. Linuxserver's swag docker is similarly one click install for nginx/reverse-proxy/certbot. It even comes with a mastodon sample conf.

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