foundryvtt-docker VS Healthchecks

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

Hey mate, I'm using https://healthchecks.io/ for heartbeat monitoring my crons. It's been working flawlessly for quite some time now. The UI is super clean and easy to navigate. It's also free up to 20 monitored jobs. Note - I'm not in any way related to that project.

In fact, your platform (https://healthchecks.io/) is a prime example of where running customer wasm would be really excellent.

Instead of sending webhooks out to customer configured URLs, you could run a Wasm environment to execute customer code. Off hand, a good use case here is to do further inspection of the event before it gets sent off to some other system - maybe there are cases where you send false-positives and needlessly trigger external system alerts. The customer Wasm could do more introspection on the healthcheck event and make a more informed decision about how to proceed.

i use healthchecks.io and have been very happy

Is there anything different from https://healthchecks.io/ --- a service I've been using for free for a couple years now?

Because of this block on the router, and the fact that IPv6 connections are by default preferred over IPv4, many things on the system now cannot access the internet. the only things that can access the internet are for accessing servers that ONLY support IPv4 like my mail.smpt2go or my uptime monitoring scripts for healthchecks.io.

i use https://healthchecks.io/ and highly recommend it.

We use a heartbeat system. Basically the monitoring continuously sends an alert to a healtcheck system. If that heartbeat fails, PagerDuty sends an alert to the oncall.

i like healthchecks.io