docs(packaging): stop telling packagers to document dependency version constraints (#3576)
writing-readmes.md contradicted itself: the AI-quick-reference admonition and the pre-publish checklist both say a README carries no version numbers anywhere, while the section outline and the Dependencies section instructed packagers to document a version constraint per dependency.
The instructions won, and the constraints went stale as predicted: monerod-startos listed Tor at >= 0.4.9.5 against a declared >=0.4.9.11:4, and all four of open-webui-startos’ backend minimums had drifted from startos/backends.ts. Both READMEs dropped the column rather than syncing it; this removes the instruction that produced it.
setupDependencies() stays the single source of truth for a version range.
Co-authored-by: Matt Hill 9935159+MattDHill@users.noreply.github.com
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
Start Technologies
What is this?
This repository is the monorepo for all Start9 products. Its flagship is StartOS — an open-source Linux distribution for running a personal server, handling discovery, installation, network configuration, data backup, dependency management, and health monitoring of self-hosted services.
All products share a single Rust backend library (
start-core) and a single Angular workspace; each product is a thin wrapper underprojects/that adds only its own entry point and any product-specific frontend or packaging, while shared code lives at the top level undershared-libs/.projects/start-os/startbox/start-containerbins, web UI + setup wizard, container runtime, OS packagingprojects/start-cli/projects/start-registry/registrybox); serves the marketplace UIprojects/start-tunnel/tunnelbox) + its web UIprojects/start-wrt/startwrtbin + embedded web UI), flashable image for the SpaceMiT K1projects/start-sdk/@start9labs/start-sdkfor building StartOS service packagesprojects/brochure-marketplace/projects/start-docs/shared-libs/crates/start-core/shared-libs/ts-modules/shared-libs/crates/patch-db/Tech stack: Rust backend (Tokio/Axum), Angular frontend (Taiga UI), Node.js container runtime with LXC, and a custom diff-based database (Patch-DB) for reactive state synchronization. Services run in isolated LXC containers, packaged as S9PKs — a signed, merkle-archived format supporting partial downloads and cryptographic verification.
See ARCHITECTURE.md for how the pieces fit together.
What can you do with StartOS?
StartOS lets you self-host services that would otherwise depend on third-party cloud providers — giving you full ownership of your data and infrastructure. Browse available services on the Start9 Marketplace, including:
Services are added by the community. If a service you want isn’t available, you can package it yourself.
Getting StartOS
Buy a Start9 server
The easiest path. Buy a server from Start9 and plug it in.
Build your own
Follow the install guide to install StartOS on your own hardware.
Build from source
See CONTRIBUTING.md for the shared toolchain and development workflow, and projects/start-os/CONTRIBUTING.md to build a StartOS image.
The rest of the monorepo
StartOS is the flagship, but it shares this repo with the rest of the Start9 stack:
.s9pk).@start9labs/start-sdkTypeScript SDK and packaging toolchain for wrapping any app into an installable StartOS service.Documentation
CLAUDE.mdis a one-line@AGENTS.mdimport)Contributing
There are multiple ways to contribute: work directly on a product in this repo, package a service for the marketplace, or help with documentation and guides. See CONTRIBUTING.md or visit start9.com/contribute.
To report security issues, email security@start9.com.