circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

Explain platform startup failures and allow HTTP on private networks

  • github
  • github/openchronology/timeline-app
  • commit
  • main
  • github/athanclark

A production server with an http:// APP_ORIGIN other than localhost refused to start its API, and Next.js reported that as an empty 500 on every API route, so the website only showed "Unexpected end of JSON input". - Startup failures now answer 503 JSON. Configuration errors (APP_ORIGIN, PLUGIN_LIBRARY) name the problem; anything else stays non-disclosing, and the cause is logged. - ALLOW_INSECURE_ORIGIN=1 permits a plain HTTP origin on a trusted private network; it is in the .deb configuration template, compose.yml and docs. - The web API client reports the HTTP status when a response is not JSON. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/6c8296701fc8f83e9dd60286ff138d5b7ea87292

Open Explain platform startup failures and allow HTTP on private networks in the timeline

Explain platform startup failures and allow HTTP on…