Polish up README and other docs to get ready for 1.0.0#147
Conversation
There was a problem hiding this comment.
Pull request overview
Documentation polish in preparation for a 1.0.0 release, focusing on clarifying Docker image usage/building, consolidating developer workflows into the Development Guide, and de-duplicating contributor docs.
Changes:
- Update README Docker examples to use locally built images and link SBOM generation instructions to the Development Guide.
- Add Maven Local publishing + local SBOM generation instructions to
dev-docs/DEVELOPMENT.md. - Remove duplicated Maven Local publishing section from
CONTRIBUTING.md.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| README.md | Switches Docker examples to solr-mcp:latest, adds a “build locally first” note, and links SBOM local generation to dev docs. |
| dev-docs/DEVELOPMENT.md | Adds Maven Local publishing instructions and a dedicated section for generating the CycloneDX SBOM locally. |
| CONTRIBUTING.md | Removes the Maven Local publishing section to avoid duplication (now covered in the Development Guide). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ## Get started (users) | ||
|
|
||
| > **Note:** Published container images are not yet available on a public registry. The `docker run` examples below use a **locally built** image — build it first with `./gradlew jibDockerBuild` (produces `solr-mcp:latest`), or use the JAR path instead. See [Building Docker images](#building-docker-images). |
| - Docker: | ||
| ```bash | ||
| docker run -i --rm ghcr.io/apache/solr-mcp:latest | ||
| docker run -i --rm solr-mcp:latest |
| - Docker: | ||
| ```bash | ||
| docker run -p 8080:8080 --rm -e PROFILES=http ghcr.io/apache/solr-mcp:latest | ||
| docker run -p 8080:8080 --rm -e PROFILES=http solr-mcp:latest |
|
|
||
| ```bash | ||
| docker run -p 8080:8080 --rm -e PROFILES=http ghcr.io/apache/solr-mcp:latest | ||
| docker run -p 8080:8080 --rm -e PROFILES=http solr-mcp:latest |
| Using Docker (CLI): | ||
| ```bash | ||
| claude mcp add --transport stdio solr-mcp -- docker run -i --rm ghcr.io/apache/solr-mcp:latest | ||
| claude mcp add --transport stdio solr-mcp -- docker run -i --rm solr-mcp:latest |
|
|
||
| # Docker | ||
| docker run -p 8080:8080 --rm -e PROFILES=http ghcr.io/apache/solr-mcp:latest | ||
| docker run -p 8080:8080 --rm -e PROFILES=http solr-mcp:latest |
| This is useful when: | ||
| - Testing the library locally before publishing to a remote repository | ||
| - Sharing artifacts between local projects during development |
Three factual fixes surfaced while reviewing the README polish (apache#147/apache#151), which the website source pages share: - clients/jetbrains.md: Junie's project MCP config lives at `.junie/mcp/mcp.json` (nested `mcp/` dir), not `.junie/mcp.json`. - clients/vs-code.md: the `/mcp` endpoint is Streamable HTTP, so the VS Code server entry needs `"type": "http"`, not the legacy `"sse"`. - security.md: HTTP mode is **secured by default** (`http.security.enabled` defaults to true). Corrected the "disabled by default" framing and removed the non-existent `SECURITY_ENABLED` toggle; the issuer (`OAUTH2_ISSUER_URI`) is what you set to use auth, and `HTTP_SECURITY_ENABLED=false` disables it for local dev. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: adityamparikh <aditya.m.parikh@gmail.com>
|
Thanks for kicking off the 1.0.0 docs polish, @epugh — I built a follow-up on top of this PR and a couple of companion changes. Summary so the threads are linked: #151 — builds on this PR (your commits are bundled in). It finishes the review of #147 and:
You can either merge #151 as the consolidated 1.0.0 docs PR, or merge this PR first and I'll rebase #151 down to just the delta. Companion changes (same fixes, other surfaces):
Merge order: #143 → #151 (the README links into #143's pages), and solr-site#175 fetches #143's content at build time. |
…95) (#151) * until we publish docker images.... lets show the clone * Move dev oritented docs on publishing to dev guide * SBOM generation locally is a development task * be truthful about our lack of published images * keep the good parts! * Add native compile docs * consoildate all security related docs under docs/security * from pr 95 * docs: slim README to a "how to use" guide; relocate build/SBOM detail Refocuses README.md on end-user "how to use" content and moves developer/operational detail into the docs that own it, so the README stays scannable and the deep material has a single home. README.md - Lean structure: value prop -> Quick start (start Solr, build, connect a client, try it) -> Example prompts -> tools/resources/prompts tables -> essential config -> documentation hub -> community. - Ports the unique end-user content from #95: sample-data blurb (films/books) and the categorized Example prompts. - Defers the full per-client matrix to the in-repo site pages under docs/site/content/pages/mcp/ (from #143), security to docs/security/, observability to the site page, and build/Docker/native/SBOM to dev-docs. - Fixes carried over from the #147 review: HTTP_SECURITY_ENABLED (secured by default), not the non-existent SECURITY_ENABLED. CONTRIBUTING.md - Convert bare-path references to markdown links for consistency. - De-duplicate "Publishing to Maven Local" -> link the dev-docs section (CONTRIBUTING's own principle is "no duplication; detail lives in dev-docs"). dev-docs/DEPLOYMENT.md - New "Image variants — why three images" section receiving the rationale moved out of the README: the image x mode matrix, run commands, why Jib builds the JVM image and Paketo the native variants (and why Paketo's JVM image breaks STDIO), and the native Claude Desktop config (latest-native-stdio). dev-docs/DEVELOPMENT.md - Move the consumer-facing SBOM content (where it ships, fetch via the actuator endpoint, scan with Trivy/Grype) here next to "Generating the SBOM locally", replacing the now-removed README section it linked to. Companion website-page fixes (.junie/mcp/mcp.json, VS Code type: http, HTTP_SECURITY_ENABLED) flow into #143. Depends on #143 for the docs/site/* links to resolve on main. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: adityamparikh <aditya.m.parikh@gmail.com> * docs: document MCP completions and Solr version compatibility - README: add a "Completions" subsection (the `{collection}` resource argument and the search-collection/index-data/view-schema/design-schema prompt arguments all autocomplete to live collection names), and a one-line Solr compatibility note linking the dev-docs section. - dev-docs/DEVELOPMENT.md: add "Solr Version Compatibility" under Testing — the `-Dsolr.test.image` override, the tested-version matrix (8.11, 9.4, 9.9, 9.10, 10), and the Solr 10 caveats (mbeans removed → null cache/handler stats; SolrJ 10.x not yet on Maven Central). Ported from AGENTS.md so it lives in the developer docs, not just the agent guide. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: adityamparikh <aditya.m.parikh@gmail.com> --------- Signed-off-by: adityamparikh <aditya.m.parikh@gmail.com> Co-authored-by: Eric Pugh <epugh@opensourceconnections.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Close in favour of #151 |
No description provided.