shithub Public

Watch 1 Fork 0 Star 0
markdown · 2274 bytes Raw Blame History

Status

Live status of shithub.sh and the published mirrors. This page is hand-maintained by the operator on call; the machine-readable health endpoints are linked under each section.

A full statuspage.io-style dashboard is planned post-MVP. Until then, this page + the operator's incident notes are the authoritative status source.

Right now

All systems normal.

Last updated: TBD (operator updates on each cutover or incident).

Health endpoints

These return immediately and reflect the running web process:

A scripted check from your machine:

curl -fsS https://shithub.sh/readyz

Non-200 means the web service is degraded or down. The operator's monitoring also alerts on this; you don't need to poll it.

Subdomains

Subdomain Purpose Health
shithub.sh App /readyz
docs.shithub.sh Docs site (this site) Static; HTTP 200 on /

Backups

The most recent successful backup is recorded by the operator's monitoring. Quarterly restore drills are scheduled; the last one's log is archived to the backup bucket (shithub-backups/drills/<YYYY-Q>/).

Mailbox availability

The disclosure mailbox security@shithub.sh auto-acks within minutes. If you reported a vulnerability and didn't get an auto-ack within 30 min, the inbound flow is broken — please email the operator's GitHub-listed contact as a fallback.

Recent incidents

(none yet)

Subscribing

There's no email/RSS feed for status updates yet. Watch the operator's announcements account (linked from the homepage) or refresh this page during a known incident window.

View source
1 # Status
2
3 Live status of `shithub.sh` and the published mirrors.
4 This page is hand-maintained by the operator on call; the
5 machine-readable health endpoints are linked under each section.
6
7 > A full statuspage.io-style dashboard is planned post-MVP. Until
8 > then, this page + the operator's incident notes are the
9 > authoritative status source.
10
11 ## Right now
12
13 **All systems normal.**
14
15 Last updated: TBD (operator updates on each cutover or incident).
16
17 ## Health endpoints
18
19 These return immediately and reflect the running web process:
20
21 - [`https://shithub.sh/-/health`](https://shithub.sh/-/health) —
22 `200 OK` with version + commit + buildAt when the web service
23 is up.
24 - [`https://shithub.sh/healthz`](https://shithub.sh/healthz) —
25 liveness only; `200 OK` if the process is responding.
26 - [`https://shithub.sh/readyz`](https://shithub.sh/readyz) —
27 readiness; `200 OK` only when DB + storage are reachable.
28
29 A scripted check from your machine:
30
31 ```sh
32 curl -fsS https://shithub.sh/readyz
33 ```
34
35 Non-200 means the web service is degraded or down. The operator's
36 monitoring also alerts on this; you don't need to poll it.
37
38 ## Subdomains
39
40 | Subdomain | Purpose | Health |
41 |----------------------------|------------------------|---------------------------------------------|
42 | `shithub.sh` | App | `/readyz` |
43 | `docs.shithub.sh` | Docs site (this site) | Static; HTTP 200 on `/` |
44
45 ## Backups
46
47 The most recent successful backup is recorded by the operator's
48 monitoring. Quarterly restore drills are scheduled; the last one's
49 log is archived to the backup bucket
50 (`shithub-backups/drills/<YYYY-Q>/`).
51
52 ## Mailbox availability
53
54 The disclosure mailbox `security@shithub.sh` auto-acks within
55 minutes. If you reported a vulnerability and didn't get an
56 auto-ack within 30 min, the inbound flow is broken — please email
57 the operator's GitHub-listed contact as a fallback.
58
59 ## Recent incidents
60
61 (none yet)
62
63 ## Subscribing
64
65 There's no email/RSS feed for status updates yet. Watch the
66 operator's announcements account (linked from the
67 [homepage](https://shithub.sh/)) or refresh this page during
68 a known incident window.