Skip to content

Disco is an Open Source deployment platform built for developers

active 2024-03-312026-06-02 (UTC)

Complete coverage26,504 / 26,504 hourly files (100%) · 2 absent upstream2023-08-152026-08-23 (UTC)
Events
490
Pushes
212
Pull requests
7
Issues
63
Stars
72
Forks
3

Activity over time

Daily event counts in the loaded window

Line chart, 794 days from 2024-03-31 to 2026-06-02. Pushes: 212 total, peak 8 in a day. Pull requests: 7 total, peak 2 in a day. Issues: 63 total, peak 3 in a day. Comments: 52 total, peak 10 in a day. Stars: 72 total, peak 18 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
antoineleclair232203016
gregsadetsky889428
emanuelefaja5014
mota-lhd3012
reorx2001
colus0011010
rhelsing1000
robsimmons1001

Recent activity

Latest issues, pull requests and releases

  • Issue#97gregsadetsky2026-05-08 17:09
    Often getting failed to update reverse proxy to serve new deployment.
  • Issue comment#92emanuelefaja2026-04-24 03:11
    Add extraRunParams for hooks, commands, and crons
  • Issue comment#92emanuelefaja2026-04-03 04:13
    Add extraRunParams for hooks, commands, and crons
  • Issue comment#97emanuelefaja2026-04-03 03:19
    Often getting failed to update reverse proxy to serve new deployment.
  • Issue comment#97gregsadetsky2026-04-03 02:57
    Often getting failed to update reverse proxy to serve new deployment.
  • Issue#89gregsadetsky2026-02-08 01:04
    expose (on project level?) status of tls/ssl letsencrypt certificate
  • Pull request#87gregsadetsky2026-01-29 01:57
  • Issue#15gregsadetsky2026-01-22 14:39
    deployment gets stuck in "queued"
  • Issue comment#52gregsadetsky2026-01-22 14:38
    consider/look into a grafana/loki compatible logging sender..? to have more options than syslog
  • Issue#84gregsadetsky2026-01-19 20:46
    HA brainstorming
  • Issue comment#81gregsadetsky2026-01-16 22:04
    dev-deploy.sh -- "some files/attrs were not transferred"
  • Issue comment#80gregsadetsky2025-12-25 02:50
    Add DOCKERFILE_PATH as env to support multiple Dockerfiles in a monorepo
  • Pull request#80colus0012025-12-25 02:23
  • Issue comment#79gregsadetsky2025-12-09 17:58
    interactive shell websockets
  • Pull request#79gregsadetsky2025-12-09 02:44
  • Issue#78reorx2025-12-04 09:17
    Is it possible to configure an app to trigger pull image and redeploy from github action?
  • Issue comment#78reorx2025-12-04 09:17
    Is it possible to configure an app to trigger pull image and redeploy from github action?
  • Issue comment#78gregsadetsky2025-12-03 14:32
    Is it possible to configure an app to trigger pull image and redeploy from github action?
  • Issue comment#78gregsadetsky2025-12-03 05:35
    Is it possible to configure an app to trigger pull image and redeploy from github action?
  • Issue comment#76gregsadetsky2025-11-24 02:10
    exposedInternally not creating stable network aliases
  • Issue#76rhelsing2025-11-24 01:33
    exposedInternally not creating stable network aliases
  • Issue comment#75gregsadetsky2025-11-23 02:58
    Add CPU and RAM resource limits support to disco.json
  • Issue comment#75emanuelefaja2025-11-16 03:03
    Add CPU and RAM resource limits support to disco.json
  • Pull request#75emanuelefaja2025-11-16 01:38
  • Issue#45antoineleclair2025-11-08 01:01
    Failed to cancel deployment after deployment hung because of full disk

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 72 stars here means stars gained during the window, not the repo's star count.