Skip to content

docs: add Deploy to Zopday buttons and repair the dead chart links - #319

Merged
arunesh-j merged 2 commits into
mainfrom
docs/readme-deploy-badges
Aug 19, 2026
Merged

arunesh-j merged 2 commits into
mainfrom
docs/readme-deploy-badges

Conversation

@arunesh-j

Copy link
Copy Markdown
Contributor

The links were all dead

Every chart link in the top-level README pointed at https://helm.zop.dev/<chart>. All 24 of them return 404 — that path was never served. The live page is the chart browser:

https://helm.zop.dev/mysql                        -> 404
https://helm.zop.dev/src/readme.html?id=mysql     -> 200

Every link now uses the working form, and each one was checked against the running site rather than assumed.

Deploy to Zopday buttons

Added to all seven application charts' READMEs, directly under the H1:

<p align="center">
  <a href="https://zop.dev/zopday/app/deploy?install=holmesgpt"><img src="https://zop.dev/deploytozopday-inkhard.svg" alt="Deploy to Zopday"></a>
</p>

holmesgpt, jupyterhub, litellm, localai, outline, superset, wordpress — each with its own install=<chart>. The top-level applications table also gains a Deploy column carrying the same button, so it is reachable without opening a chart first.

Datasource charts deliberately do not get one: they are not something a user deploys as an app.

n8n gets the same button on #311 rather than here, so it cannot land without it.

Eight charts were missing from the tables

All published, none listed: scylladb (datasources) and openobserve-standalone, uptime-monitoring, zookeeper, zookeeper-operator, solr-operator, karpenter-gcp (others).

uptime-monitoring had no README

It was the one published chart with none, so the link I was adding would have landed on the site's not-found illustration. Written from its templates: what it probes, the two queries it exists for (probe_success, and certificate expiry via (probe_ssl_earliest_cert_expiry - time()) / 86400), its values, and one thing worth knowing before installing — its Blackbox objects (blackbox-exporter, blackbox-config, prometheus-config) are not release-prefixed, so two releases in one namespace collide. Documented rather than changed, since renaming them is a breaking change for anyone already running it.

Also

Two dead links in the holmesgpt README: holmesgpt.dev moved its docs under a /latest/ prefix, so /ai-providers/ and /data-sources/ both 404. Repaired and verified.

Verification

Every URL in every README resolves — 45 in the top-level README, 27 across the chart READMEs, checked live:

  • all 33 readme.html?id= chart links → 200
  • all 7 zop.dev/zopday/app/deploy?install= links → 200
  • the badge SVG → 200

One deliberate exception: https://oauth2.googleapis.com/token in a chart README is a POST-only endpoint and correctly 404s on GET.

Every chart link in the top-level README pointed at https://helm.zop.dev/<chart>,
and all 24 of them return 404. The live page is the chart browser at
https://helm.zop.dev/src/readme.html?id=<chart>, so every link now uses that
form. Each one was checked against the running site rather than assumed.

Adds the Deploy to Zopday button to the seven application charts' READMEs, each
pointing at https://zop.dev/zopday/app/deploy?install=<chart>, and a Deploy
column to the applications table so the same button is reachable from the
top-level README. Datasource charts deliberately do not get one - they are not
things a user deploys as an app.

Eight published charts were missing from the tables entirely: scylladb under
datasources, and openobserve-standalone, uptime-monitoring, zookeeper,
zookeeper-operator, solr-operator and karpenter-gcp under others.

uptime-monitoring was the one published chart with no README at all, so linking
it would have landed on the site's not-found state. Written from its templates:
what it probes, the two queries it exists for (probe_success and certificate
expiry), its values, and the fact that its Blackbox objects are not
release-prefixed so it can only be installed once per namespace.

Also repairs two dead links in the holmesgpt README - holmesgpt.dev moved its
docs under a /latest/ prefix.

Every URL in every README now resolves: 45 in the top-level README, 27 across
the chart READMEs. The two exceptions are intentional - oauth2.googleapis.com
is a POST-only endpoint that 404s on GET.
The centred block sat under the heading and pushed the description down. A
right-floated anchor placed before the H1 puts it on the title line instead,
flush right.

Verified against the live stylesheet rather than assumed: docs/src/css/readme.css
sets #readme-content img to display:block, which does not defeat a float. Rendered
geometry measured at float:right, 169x36, overlapping the h1 box. The anchor stays
outside the heading so readme.js, which labels its sidebar from heading.textContent,
still reads a clean title.
@arunesh-j
arunesh-j merged commit 119a7e9 into main Aug 19, 2026
1 check passed
@arunesh-j
arunesh-j deleted the docs/readme-deploy-badges branch August 19, 2026 13:03
arunesh-j added a commit that referenced this pull request Aug 28, 2026
docs/index.yaml conflicted again because both sides regenerated it wholesale -
main gained the qdrant chart (#310) and the README fixes (#319). Resolved the
same way: discard both versions and re-run

  helm repo index . --url https://helm.zop.dev

over the merged docs/ directory. Verified the only semantic change against main
is the added n8n v0.0.1 entry - 184 tarball digests match, nothing removed,
nothing altered, and qdrant v0.0.1 from main is intact.

Also adds n8n to the applications table in the top-level README. #319 landed
that table with a Deploy column while this branch was open, so without this the
chart would merge unlisted. Both of its links were checked live.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants