HUB
Sign inSign up

system4us/issue-timeline

By system4us

•Updated 1 day ago

Tracker of trackers | Github - Gitlab - Redmine - Jira

Image
Developer tools
0

250

system4us/issue-timeline repository overview

⁠issue-timeline

Your issues, pull requests, commits, and CI on one timeline — across GitHub, GitLab, Redmine, and Jira.

A single dependency-free Go binary with an embedded React web UI. It syncs issues, merge/pull requests, dependencies, parent/epic hierarchies, commits, and CI runs into local JSON stores, and serves both the web app and an OpenAPI-documented REST/SSE API.


⁠Tags

TagSource
latest, X.Y.ZStable release tags (vX.Y.Z)
beta, X.Y.Z-beta.NPre-release tags (vX.Y.Z-beta.N)
edgeLatest build from main

⁠Quick start

⁠Docker Compose

Create a .env file (see Configuration⁠) and run:

services:
  issue-timeline:
    image: system4us/issue-timeline:latest
    env_file:
      - path: .env
        required: false
    ports:
      - "127.0.0.1:4310:4310"
    volumes:
      - issue-timeline-data:/data
    restart: unless-stopped

volumes:
  issue-timeline-data:
docker compose up -d

Open http://localhost:4310.

⁠docker run
docker run -d \
  --name issue-timeline \
  -p 127.0.0.1:4310:4310 \
  -v issue-timeline-data:/data \
  -e GITHUB_TOKEN=ghp_... \
  -e GITLAB_TOKEN=glpat-... \
  --restart unless-stopped \
  system4us/issue-timeline:latest

The container runs as the unprivileged issue-timeline user, listens on 0.0.0.0:4310, and persists all data under /data (STORE_DIR=/data).


⁠Authentication

Inside the container there is no gh or glab CLI session. You can authenticate in two ways (or combine both):

Set personal access tokens in .env so the server can validate and periodically sync repositories even when no user is signed in:

  • GitHub: GITHUB_TOKEN (fine-grained or classic PAT; private repos require repo / Issues + Pull requests + Contents + Metadata + Actions read).
  • GitLab: GITLAB_TOKEN for gitlab.com, or GITLAB_TOKEN_<HOST> (e.g. GITLAB_TOKEN_GITLAB_EXAMPLE_COM) for self-managed instances (api scope, or read_api for read-only).
  • Redmine / Jira: store secrets inside /data with:
    docker compose exec issue-timeline issue-timeline credentials set redmine-api-key
    docker compose exec issue-timeline issue-timeline credentials set jira-email
    docker compose exec issue-timeline issue-timeline credentials set jira-api-token
    
⁠2. OAuth sign-in (GitHub / GitLab)

Configure an OAuth app so users sign in via Continue with GitHub / Continue with GitLab:

  • Callback URLs:
    • GitHub: <PUBLIC_URL>/api/oauth/github/callback
    • GitLab: <PUBLIC_URL>/api/oauth/gitlab/callback
  • When OAuth is configured, you can sign in right away even before adding your first repository, then add repositories on that host from the UI.
  • Active sessions are persisted in /data/sessions.json (0600, without storing OAuth client secrets) so container restarts keep you signed in until SESSION_IDLE_HOURS or SESSION_MAX_DAYS expires.

⁠Exposing via Reverse Proxy or LAN / Tailscale

For DNS-rebinding protection, the server only accepts Host headers matching its own loopback/container interfaces or ALLOWED_HOSTS.

If you access the container through a reverse proxy, LAN IP, or Tailscale IP/MagicDNS:

  1. Set ALLOWED_HOSTS to the hostname(s) or IP(s) clients use (comma-separated):
    ALLOWED_HOSTS=timeline.example.com,100.64.0.10
    
  2. Set PUBLIC_URL to the external URL (for example https://timeline.example.com), or leave it empty to derive the callback base from the incoming Host header.
  3. Behind an HTTPS reverse proxy, forward X-Forwarded-For and X-Forwarded-Proto: https (or set COOKIE_SECURE=1).

⁠Configuration

VariableDefaultPurpose
PORT4310HTTP port inside the container
HOST0.0.0.0Listen address inside the container
STORE_DIR/dataDirectory for repo stores, config, and sessions
ALLOWED_HOSTSnoneComma-separated hostnames/IPs accepted in Host header
PUBLIC_URLfrom requestBase URL for OAuth callback URLs (e.g. https://timeline.example.com)
COOKIE_SECURE0Set to 1 to force Secure on session cookies
SESSION_IDLE_HOURS12Idle timeout for user sessions
SESSION_MAX_DAYS7Maximum lifetime of user sessions
POLL_MINUTES5Background sync interval in minutes
CI_DAYS90Days of CI runs retained
GITHUB_TOKENnoneServer token for GitHub
GITHUB_HOSTgithub.comGitHub Enterprise Server host
GITHUB_OAUTH_CLIENT_ID, GITHUB_OAUTH_CLIENT_SECRETnoneGitHub App or OAuth App credentials
GITHUB_OAUTH_SCOPESrepoScopes requested for GitHub OAuth Apps
GITLAB_TOKENnoneServer token for gitlab.com (GITLAB_TOKEN_<HOST> for self-managed)
GITLAB_OAUTH_CLIENT_ID, GITLAB_OAUTH_CLIENT_SECRETnoneGitLab OAuth application credentials
GITLAB_OAUTH_URLhttps://gitlab.comGitLab instance URL when different from gitlab.com
GITLAB_OAUTH_SCOPESapiScopes requested for GitLab OAuth (api or read_api)
WEBHOOK_SECRETnoneSecret enabling POST /api/webhook for instant updates
REGISTER_WEBHOOKfalsetrue registers the webhook on each GitHub/GitLab repo using PUBLIC_URL and WEBHOOK_SECRET (needs a PUBLIC_URL the hosts can reach)
VOCABULARY_FILEbuilt-inPath inside container to a custom vocabulary JSON file
REDMINE_API_KEYfrom credentialsFallback Redmine API key
JIRA_EMAIL, JIRA_API_TOKENfrom credentialsFallback Jira Cloud credentials

⁠Persistent Data (/data)

Mount a volume at /data to preserve:

  • repos.json, repo-modes.json, links.json, roles.json — configured repositories, read/write modes, tracker links, and role mappings
  • sessions.json (0600) — active user sessions across restarts
  • credentials.json, secret-origins.json (0600) — Redmine/Jira credentials saved via issue-timeline credentials set
  • *.json, *.commits.json, *.ci.json — cached issues, pull/merge requests, commits, and CI runs per repository

Tag summary

Content type

Image

Digest

sha256:f2ca72c29…

Size

34.6 MB

Last updated

1 day ago

docker pull system4us/issue-timeline:edge