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

archetech / archon / 33446311227
95%

Build:
DEFAULT BRANCH: main
Ran 31 Aug 2026 10:31PM 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 10:27PM UTC coverage: 92.48%. Remained the same
33446311227

push

github

web-flow
perf(docker): Split cli and explorer into build and runtime stages (#996)

* perf(docker): Split cli and explorer into build and runtime stages

The last two images in #987, neither of which fitted the template used
for the rest.

cli is exec'd into rather than run, so what may be pruned is a question
about what the image is for. It carries the compiled workspaces, the
dependencies they resolve through, and scripts/ -- and nothing that only
the build needed. 1.09GB -> 621MB. Verified by using it: `keymaster
--version` reports 0.6.3, `--help` renders, and `create-wallet` loads
cipher and node:sqlite and reaches the gatekeeper connection.

explorer serves its bundle through its own server.js, which imports only
express and dotenv -- both resolving from the service's own
node_modules. The root tree is therefore not copied into the runtime at
all, which is why this is the largest reduction of the set: 1.27GB ->
288MB.

Checked against the previous image rather than assumed: both serve
`<title>Archon Explorer</title>` at /explorer/index.html, both return the
same status on /, /explorer, /explorer/ and /explorer/index.html, and the
same hashed asset resolves in both. The 302 on /explorer/ is present in
the old image too and is unrelated to this change.

Refs #987

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

* fix(docker): Carry VITE_EXPLORER_BASE into the explorer runtime

Review caught the runtime stage losing it. server.js reads
VITE_EXPLORER_BASE to decide the path it serves under, and the bundle is
built against the same value, so an image built with a non-default base
served its assets from one path while the bundle referenced another.

Narrower than it appears: docker/compose/explorer.yml supplies the value
both as a build arg and in the environment, so compose deployments were
unaffected. The image alone was inconsistent.

Verified by building with --build-arg VITE_EXP... (continued)

3880 of 4464 branches covered (86.92%)

Branch coverage included in aggregate %.

8528 of 8953 relevant lines covered (95.25%)

717.56 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33446311227.1 31 Aug 2026 10:31PM UTC 184
93.57
GitHub Action Run
Source Files on build 33446311227
  • 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 #33446311227
  • 0fb3f1f9 on github
  • Prev Build on main (#33441791586)
  • Next Build on main (#33455065226)
  • 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