Original Summary

I kept losing track of what was actually running on my home server. It started small: a Gitea instance, Jellyfin, a 9router, an FTP box. Then each one wanted its own way of being run - one in tmux, a couple as systemd units, the rest in Docker. Nothing was broken exactly, but there was no single place that answered "is everything up right now?" and no place that told me in the morning that something had died at 3am. So I built home-hosted: a control panel plus process supervisor that treats each service as just command + args + env, and puts the whole stack on one page. What it gave me: - start/stop/restart per service, health checks, and restart/port-conflict policy handled for me - one dashboard: CPU/RAM, live logs, status - DDNS + reverse proxy, so a domain points home and gets HTTPS automatically - backups that include the managed servers' own data, restorable on a blank host - Telegram alerts when something crashes, fails health, fills the disk, or changes IP - an OpenAPI spec and CLI, so I can hand installation and management to an agent - a replaceable frontend (BYOU) for when I want my own UI - Linux, macOS and Windows It is MIT, at v0.8, and honestly the most useful feedback right now would be on the supervision model and the config/API shape. Repo: https://github.com/NamesMT/home-hosted Try: npx home-hosted   submitted by   /u/markithepews [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/15 03:44:32