oskar/homelab-codex-ws
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity
homelab-codex-ws/kb/subsystems/legacy-services-list.md
oskar a427aad47e feat(kb): przenosiny type=subsystem do kb/subsystems/ (18 plikow, bez SPLIT) 
public (wzorce/schematy, bez IP/portow/sciezek hostow): observer,
capability-model, event-system, standards, agent-operating-procedures,
service-model, action-approval-model.

private: recon-multiagent, fleet-inventory, fleet-inventory-verify,
kb-mail-pillar, kb-documents-pillar, topology, agent-system.

deprecated (martwe stuby z 2026-04-15) — visibility private wg
rozstrzygniecia 6: access-model, core-stack, legacy-services-list, networking.

git mv + frontmatter, tresc nietknieta.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-04 16:19:30 +02:00

1.5 KiB
Raw Blame History

okf type visibility status updated links superseded_by
0.1 subsystem private deprecated 2026-04-15
kb/subsystems/fleet-inventory.md + hosts/<node>/capabilities.yaml (stub z 2026-04-15, sprzed floty)

Services

Description

This page documents the currently known services in the homelab.

Current configuration

Known Raspberry Pi 5 services:

  • Portainer
  • Nginx Proxy Manager

Known Hetzner VPS services:

  • Nginx Proxy Manager

Known Hetzner VPS service files:

  • Joplin Server

Known supporting platform:

  • Docker

Known facts

  • Portainer is present in the homelab.
  • Nginx Proxy Manager is present in the homelab.
  • Public services are exposed through Nginx Proxy Manager using HTTPS.
  • Private access is available through Tailscale.
  • On the Hetzner VPS, Nginx Proxy Manager is running as container npm.
  • On the Hetzner VPS, Joplin Server files have been created but the service is not running yet.

Unknown / needs clarification

  • Full list of running services and containers on the Raspberry Pi 5.
  • Service names.
  • Service purposes.
  • Public or private exposure for each service.
  • Internal ports for each service.
  • External domains for each public service.
  • Docker image names and versions.
  • Data volume paths.
  • Environment variables and secrets handling.
  • Service dependencies.
  • Restart policies.
  • Health checks.
  • Backup coverage for each service.
  • Restore process for each service.
  • Whether Joplin Server should be documented as part of the current homelab, as a VPS service, or both.