Files
homarr/apps/docs
Thomas 987c9ade18 fix: make internal nginx proxy tolerate disabled IPv6 (#4596) (#6539)
* fix: keep nginx IPv6 listen only when IPv6 is available (#4596)

Commit 2c48b1896 (1.45.2) made the internal nginx proxy listen on the IPv6
wildcard ('listen [::]:7575;'), which aborts nginx startup on hosts/VMs with
IPv6 disabled:

    nginx: [emerg] socket() [::]:7575 failed (97: Address family not supported by protocol)

A plain revert would reintroduce #2697 and break IPv6-only/dual-stack
environments where this listener is required. Instead, only emit the IPv6
listen directive when the host actually has IPv6 configured.

Reuse the envsubst step run.sh already performs: compute NGINX_LISTEN_IPV6
from /proc/net/if_inet6 and substitute it into the template. proc files always
report size 0, so presence is detected by grepping the file (not 'test -s').

* fix: honor HOMARR_DISABLE_IPV6 override in nginx config generation

Review feedback on #6539: give users an explicit opt-out from the IPv6
listener even when the host reports IPv6. The issue reporter (#4596)
requested such an env var, and the pattern matches the existing
ENABLE_DNS_CACHING IPv6 toggle. Auto-detection behavior is unchanged when
the var is unset. Validated in containers: override wins, dual-stack
preserved by default, IPv4-only fallback on IPv6-less hosts.
2026-08-08 11:16:49 +02:00
..

Homarr Documentation (@homarr/docs)

The official homarr.dev documentation site, built with Docusaurus 3 and living inside the Homarr monorepo.

Why it's in the monorepo

Having documentation alongside the application code enables:

  • Two-way linking — the docs app imports from @homarr/definitions for type-safe integration/widget metadata, and the main app references doc paths via generated sitemap types
  • Atomic PRs — code changes and their documentation updates ship in the same pull request
  • Shared tooling — same Node version, pnpm catalog, oxlint/oxfmt, CI pipeline
  • Build-time validation — Docusaurus strict mode catches broken links and references at build time

Development

From the monorepo root:

# Start the docs dev server (port 3003)
pnpm dev:docs

# Or from within this directory
pnpm dev

Build

# Build docs only
pnpm turbo build --filter=@homarr/docs

# Build everything (docs + main app + tasks + websocket)
pnpm build

Lint & Format

Uses oxlint and oxfmt (same as the rest of the monorepo):

pnpm lint        # oxlint
pnpm format      # oxfmt (check)
pnpm format -- --write  # oxfmt (fix)

Typecheck

pnpm typecheck

Content Structure

docs/
├── getting-started/    # Installation guides, glossary, prerequisites
├── management/         # Boards, apps, users, integrations, settings, tasks, API
├── integrations/       # 55 integration guides (one folder each)
├── widgets/            # 42 widget guides (one folder each)
├── advanced/           # SSO, env vars, proxy, styling, CLI, development
└── community/          # FAQ, donate, license, translations, get-in-touch

Each integration/widget doc follows a consistent pattern:

  • index.ts — typed metadata (IntegrationDefinition / WidgetDefinition)
  • index.mdx — content using shared React components (IntegrationHeader, WidgetHeader, etc.)

Importing from homarr packages

The docs app has @homarr/definitions as a workspace dependency. You can import integration kinds, widget kinds, and other definitions directly:

import { IntegrationKind } from '@homarr/definitions';

This enables type-safe references to homarr domain concepts within documentation code.

Search (Algolia DocSearch)

Search uses the Docusaurus Algolia index (crawler cd77a285-2756-4557-bf21-ee703748df15). A separate markdown index is built for LLM markdown indexing.

Crawler reference config: docsearch.config.js.

Verify search health:

pnpm verify:search

Tech Stack

Layer Technology
Site generator Docusaurus 3 (@docusaurus/preset-classic)
Styling Tailwind CSS 3 + Docusaurus Infima
Icons @tabler/icons-react
Diagrams Mermaid (@docusaurus/theme-mermaid)
Search Algolia DocSearch
Analytics PostHog
Charts @nivo/line

Contributing

When making changes to the homarr codebase that affect user-facing behavior, always update the corresponding documentation in this app. See .cursor/rules/documentation-sync.mdc for the complete mapping of code changes to doc locations.