fly.toml

# fly.toml app configuration file generated for jchat on 2026-02-28T21:01:38Z
#
# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
#

app = 'jchat'
primary_region = 'sjc'

[build]
  dockerfile = "Dockerfile"

# Persistent storage — one volume in primary_region (SQLite + sessions are per-machine; use 1 machine only)
#   fly volume create chat_data --region sjc --size 1 -a jchat
[mounts]
  source = "chat_data"
  destination = "/data"

[http_service]
  internal_port = 8080
  force_https = true
  auto_stop_machines = false
  auto_start_machines = true
  min_machines_running = 1
  processes = ["app"]

  [http_service.http_options]
  idle_timeout = 600

# Boot probe -- Fly's proxy marks the instance unhealthy until this
# returns 200. Without it, the proxy shows "no known healthy
# instances found for route tcp/443" right after deploys (PR01).
# 200 OK from a static "ok" body in Node; deliberately cheap.
[[http_service.checks]]
  grace_period = "10s"
  interval = "15s"
  method = "GET"
  timeout = "5s"
  path = "/health"

[[vm]]
  cpu_kind = 'shared'
  cpus = 1
  # 1GB is the minimum that runs Chromium + the per-user daemon pool
  # without constant OOMs. 512MB caused the daemon to die mid-call
  # whenever a second user hit the dashboard, which made cold-start
  # fetches 4x slower (each section had to wait for Chromium to relaunch).
  memory_mb = 1024