One-ClickGitHub
Home / Documentation / Overview
Getting Started

Overview

A practical map of One-Click: how the shell-native control plane is organised, how modules are loaded, and where to go next.

One-Click documentation · Step-by-step guide

One-Click is a shell-native infrastructure control plane for Linux operators. It groups system administration, security, application hosting, virtualisation, networking and Fleet orchestration into guided workflows while keeping the underlying Linux mechanisms visible.

Operating model

One-Click does not require a permanent web administration service. The normal control surface is the local shell, with temporary web tooling created only for workflows that need it.

Control Domains

System UtilitiesSystem information, OCB benchmarking, logs, cron and backup.
SecurityRule Engine, firewall inspection, audit and IDS workflows.
Web & ApplicationsWordPress, static/PHP, Node.js, databases, SSL and DNS.
Fleet InfrastructureFleet peers, KVM guests, HAProxy edge publishing, snapshots and workload movement.
Network ManagerNetwork health, recovery and DNS operations.

First Steps

  1. Install One-Click using the bootstrap workflow.
  2. Review the generated environment and attach to the managed tmux session.
  3. Initialise Fleet only when the server will act as a controller.
  4. Configure provider credentials only for integrations you actually use.
  5. Use dry-run and preview modes before high-impact changes.

Source of Truth

The public GitHub repository remains the implementation source of truth for commands and module behaviour. These documentation pages organise that information into operator-focused guides and are intended to move with the released shell code.

← Documentation indexExplore the project on GitHub →