Skip to content

Rewrite BlazeGraph connection guide with practical instructions#1699

Draft
kmcginnes wants to merge 3 commits into
aws:mainfrom
kmcginnes:docs/rewrite-blazegraph-guide
Draft

Rewrite BlazeGraph connection guide with practical instructions#1699
kmcginnes wants to merge 3 commits into
aws:mainfrom
kmcginnes:docs/rewrite-blazegraph-guide

Conversation

@kmcginnes
Copy link
Copy Markdown
Collaborator

@kmcginnes kmcginnes commented Apr 22, 2026

Description

The BlazeGraph connection guide was only 2 vague bullet points with no actionable information. Rewrote it to match the quality of the Gremlin Server guide:

  • Docker command to run BlazeGraph
  • Exact connection form values for Graph Explorer
  • Note about custom namespaces
  • Docker networking section with step-by-step instructions for container-to-container communication
  • Troubleshooting section for common issues

Since the proxy server now preserves URL paths, the guide connects directly to BlazeGraph's SPARQL endpoint without requiring a reverse proxy (nginx) in between.

Validation

Verified the BlazeGraph Docker image and SPARQL endpoint path are correct. Tested end-to-end with Graph Explorer connecting to BlazeGraph via the full endpoint URL.

Related Issues

Check List

  • I confirm that my contribution is made under the terms of the Apache 2.0 license.
  • I have verified pnpm checks passes with no errors.
  • I have verified pnpm test passes with no failures.
  • I have covered new added functionality with unit tests if necessary.
  • I have updated documentation if necessary.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.67%. Comparing base (c5affc5) to head (6b7b71a).
⚠️ Report is 143 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1699       +/-   ##
===========================================
+ Coverage   47.81%   72.67%   +24.86%     
===========================================
  Files         382      408       +26     
  Lines        8525    12286     +3761     
  Branches     3159     3525      +366     
===========================================
+ Hits         4076     8929     +4853     
+ Misses       3070     2339      -731     
+ Partials     1379     1018      -361     
Flag Coverage Δ
unittests 72.67% <ø> (+24.86%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@kmcginnes kmcginnes force-pushed the docs/rewrite-blazegraph-guide branch 2 times, most recently from 6dc702d to 6b7b71a Compare April 22, 2026 22:47
@kmcginnes kmcginnes force-pushed the docs/rewrite-blazegraph-guide branch from 6b7b71a to 5227ada Compare May 4, 2026 16:47
kmcginnes added 3 commits May 8, 2026 17:36
… guide

Address review findings:
- Explain proxy server path stripping limitation with nginx workaround
- Add --restart unless-stopped to Docker command
- Note BlazeGraph 2.1.5 is the final release
- Add tables explaining connection settings and Docker options
- Add troubleshooting section for common issues
The proxy server now preserves URL paths, so users can connect
directly to BlazeGraph's SPARQL endpoint without nginx in between.
@kmcginnes kmcginnes force-pushed the docs/rewrite-blazegraph-guide branch from 5227ada to 6b6b2c6 Compare May 11, 2026 15:54
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.

1 participant