• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

archetech / archon / 33436524747
87%

Build:
DEFAULT BRANCH: main
Ran 31 Aug 2026 08:36PM UTC
Jobs 1
Files 92
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

31 Aug 2026 08:31PM UTC coverage: 92.48% (-0.007%) from 92.487%
33436524747

push

github

web-flow
perf(docker): Split the mediators and node servers into build and runtime stages (#993)

* perf(docker): Split the mediators and node servers into build and runtime stages

Seven more images take the two-stage split from #990 and #992. Three
shapes among them, which is why they were not a single mechanical pass:

- satoshi and lightning-mediator set WORKDIR to the service before
  building, so the prune runs with that as the working directory and has
  to return to /app for the root tree.
- pinning and filecoin build with `cd <svc>` from /app, so the prune is
  the other way round.
- gatekeeper-ts, keymaster-ts and didcomm copy into a `server`
  subdirectory, so the service tree pruned is `<svc>/server`.

gatekeeper-ts installs wget, which is not build tooling: the compose
healthcheck is `test "$(wget -qO- http://127.0.0.1:4224/api/v1/ready)" =
"true"`. Leaving it in the builder only would have left gatekeeper
permanently unhealthy, and every service declaring `depends_on:
condition: service_healthy` would never start. It is installed in the
runtime stage instead. Every other healthcheck across the compose files
uses `node`, which the runtime base already has.

  satoshi              649MB
  gatekeeper-ts        636MB
  lightning-mediator   633MB
  filecoin             628MB
  keymaster-ts         628MB
  pinning              628MB
  didcomm              626MB

No prior images were on hand for these, so there are no measured starting
points; the equivalents before conversion ran 1.13-1.16GB.

Each was built and run. The mediators reach their startup retry loop,
didcomm logs "DIDComm relay listening on 0.0.0.0:4236", gatekeeper-ts
stays up with wget present, and none report a missing module.

Refs #987

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GYGMfX3foBcVqP7AQNXjWj

* fix(docker): Install wget once, in the stage that needs it

Review caught wget being installed in both stages of the gatekee... (continued)

3880 of 4464 branches covered (86.92%)

Branch coverage included in aggregate %.

8528 of 8953 relevant lines covered (95.25%)

717.59 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33436524747.1 31 Aug 2026 08:36PM UTC 184
93.57
GitHub Action Run
Source Files on build 33436524747
  • Tree
  • List 92
  • Changed 78
  • Source Changed 0
  • Coverage Changed 78
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #33436524747
  • 06b22d6f on github
  • Prev Build on main (#33427826543)
  • Next Build on main (#33439622458)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc