Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

docs: air-gapped / offline deployment guide and telemetry opt-out

Open
#45 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
49/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java, ollama

Research direction

Start by reading the deployment and configuration documentation to identify how to configure a local Ollama model, outbound calls, OTLP telemetry, and dashboard behavior; the issue does not name specific files or tests. Document required and optional connections and telemetry opt-out or self-hosting, and add a switch only if none exists. Done means the guide explains an offline deployment and clearly describes which calls can be disabled.

Written by the indexing model from the issue text.

Description

documentation enhancement java
Problem Statement

A core selling point is running reviews on your own infrastructure against a local model (Ollama) so no code leaves the network — but there is no guide for an air-gapped/offline deployment, and it is unclear which outbound calls (telemetry, GitHub, provider) happen and how to disable the optional ones.

Proposed Solution

Document an air-gapped/offline deployment: required vs optional outbound connections, how to point at a local Ollama model, how to disable or self-host OTLP telemetry, and how the dashboard behaves without external calls. Add a telemetry opt-out switch if one does not already exist.

Alternatives Considered
  • Leave it to users to infer from config — undercuts the privacy niche the project targets.
Priority

Nice to have

Code of Conduct
  • I have searched for existing issues and this is not a duplicate.
Dominant language
Java
Stars
35
Forks
7
Avg merge
9h 32m
Merged PRs (30d)
144

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devops-thiago/ThrillhouseBot

All issues in devops-thiago/ThrillhouseBot

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.