📢 Docker image change: nginx removed from the Jussi container

Summary

We have removed the bundled nginx from the Jussi (legacy Python) Docker image. The change is merged in PR #242 — refactor: remove internal nginx (migrated to openresty proxy).

Why

Nginx was an extra hop in front of the Jussi process. Dropping it removes one layer of proxy forwarding, simplifies the container, and aligns deployment with a single edge proxy (for example OpenResty or nginx) that already handles routing, compression, keepalives, and observability for your environment.

What you need to do

The image now exposes the Jussi app directly (see the PR for ports and environment cleanup, including removal of NGINX_SERVER_PORT). Anything you previously relied on nginx for at the edge must live in your front nginx or OpenResty (or ingress / load balancer), for example:

• GET / handling (e.g. default page, redirects, or explicit behavior for probes)
• HTTP redirects you used to define in the old bundled config
• /health (or your platform’s health URL) for load balancers and orchestration

In short: Jussi is focused on JSON-RPC; do not assume the same convenience routes or redirects as the old all-in-one image. Configure GET /, redirects, and /health (or equivalents) explicitly on the proxy in front of Jussi.

Questions

Any issue could write here.

Looking ahead: Go rewrite and OpenTelemetry

The Golang rewrite of Jussi has finished development and internal testing. That version emits telemetry using the OpenTelemetry protocol, so production rollout will require new collectors/backends (or equivalent tooling) to receive and store those signals.

We have not stood up that new monitoring environment yet; it is waiting in the priority queue alongside other work. We currently expect to complete go-live this calendar quarter, subject to scheduling. We will share deployment notes (endpoints, env vars, and any breaking changes) when the observability stack is ready and the cutover is scheduled.