Linux infrastructure automation

One-Click Toolkit. Your Infrastructure, Your Control.

One-Click is a shell-native Linux control plane for fleets, KVM virtual machines, networking, DNS and isolated application hosting — turning repetitive administration into explicit, repeatable workflows.

Open source · MIT licensed · SSH-first · no permanent web control panel required

one-click | setup replay replay
  ___                 ____ _ _      _
 / _ \ _ __   ___    / ___| (_) ___| | __
| | | | '_ \ / _ \  | |   | | |/ __| |/ /
| |_| | | | |  __/  | |___| | | (__|   <
 \___/|_| |_|\___|   \____|_|_|\___|_|\_\

 ___           _        _ _          _
|_ _|_ __  ___| |_ __ _| | | ___  __| |
 | || '_ \/ __| __/ _` | | |/ _ \/ _` |
 | || | | \__ \ || (_| | | |  __/ (_| |
|___|_| |_|___/\__\__,_|_|_|\___|\__,_|
[SUCCESS] One-Click Is Now Installed!
Shell-nativeNormal Linux underneath
Fleet-awareAnsible + SSH orchestration
Cloud-aware DNSBIND, Cloudflare and API providers
PortableFleet import/export across boundaries
VPS in practice

From Fleet Hypervisor to Published Service.

See how One-Click prepares a host, creates a guest and publishes its services through that host’s own edge proxy.

Follow a NAT Linux VPS from controller setup to a published service. Expand each stage for the commands and decisions involved.

01Establish Fleet

Run from the intended controller. Add the target hypervisor by its reachable address and verify SSH/Ansible access before provisioning.

one-click fleet init
one-click fleet add <hypervisor-ip> hypervisor1 [ssh-port]
one-click fleet list
one-click fleet verify
02Plan and enable VPS hosting

Confirm hardware virtualisation, recovery-console access, storage capacity and the host network plan. Review ENABLE_VPS and the allocation settings in /usr/local/bin/one-click. The VPS entry point offers to enable the feature if it is disabled. Preparation can change host bridges and network services, including when starting with a NAT guest.

sudoedit /usr/local/bin/one-click
03Request a guest

Choose a unique name, a Fleet hypervisor, an image, CPU, RAM, disk and network mode. This Linux example omits --password and uses the Fleet SSH key. Supply your own values and use a supported image profile.

one-click --vps create --target hypervisor1 --name web1 --image debian13 --cpu 2 --ram 2048 --disk 20G --mode nat
04Prepare the environment on first use

The create workflow resolves the image and checks the selected host. If its virtualisation environment is missing, One-Click invokes setup within that workflow. Confirm the initialisation prompt only after reviewing the host plan. Setup prepares controller tracking, address pools, WireGuard configuration and the target KVM/libvirt networks. Subsequent creations reuse the prepared environment.

05Build and start the VPS

Provisioning checks target resources, prepares guest storage and configuration, creates the libvirt guest and waits for network access. The path varies by image: Linux cloud-image provisioning, installation media and Windows builds have different stages. Larger downloads and OS installations take longer.

06Verify inventory and access

Inspect the guest and its owning hypervisor, confirm Fleet registration and test SSH. Check the hypervisor network and guest service before exposing a workload. If libvirt contains the VM but the inventory does not, investigate registration before creating it again.

one-click --vps list
one-click --vps info web1
one-click fleet list
one-click fleet verify
one-click --ssh web1
07Publish the required service

For NAT guests, configure HAProxy on the owning hypervisor after the guest service is running. DNS points to that hypervisor’s public address. This HTTPS example forwards to port 443 in the guest, where its web server presents the certificate.

one-click proxy --target web1 --website app.example.org --proto https
one-click --vps snapshot create --target web1 --name before-change
Management

One-Click controller

Fleet inventory, SSH/Ansible orchestration and VPS operations

Fleet hypervisor A

Public address ALocal HAProxyPublished service traffic to this host’s guest
NAT VPS · web1Guest application and HTTPS certificate

Guest outbound traffic uses this hypervisor’s NAT.

Fleet hypervisor B

Public address BLocal HAProxyPublished service traffic to this host’s guest
NAT VPS · web2Guest application and HTTPS certificate

Guest outbound traffic uses this hypervisor’s NAT.

The controller can also host guests when configured as a hypervisor. WireGuard connectivity does not move a public IP or provide service failover; availability depends on the configured routing and recovery design.

Core workflows

One Toolkit for Everyday Linux Operations.

Keep the operating system visible while automating the repetitive parts of fleet, virtualisation, DNS, security and application operations.

Fleet orchestration

Linux Fleet Management

Register, verify, audit and operate remote Linux nodes through controller-driven Ansible and SSH trust.

Explore →
Portability

Fleet Import & Export

Move workloads between managed fleet members and external Linux hosts through the Fleet portability workflow.

Explore →
DNS

Cloudflare & DNS Automation

Operate DNS through BIND or API-backed providers including Cloudflare, from the same terminal-led workflow.

Explore →
Virtualisation

KVM VPS Automation

Provision and operate NAT or public KVM guests across suitable controller and fleet hosts.

Explore →
Rule Engine

Human-Readable Firewall Control

Translate intent into validated firewall changes with previews, critical-port protection and native-rule access.

Explore →
Application hosting

Isolated Web & App Hosting

Deploy and manage WordPress, Nextcloud, static/PHP sites and Node.js apps with separate site environments and shared HTTPS management.

Explore →
Designed for operators

Automate Repetitive Work. Keep Full Control.

One-Click reduces repetitive command work while preserving normal Linux tools, files and services underneath.

No Always-on Admin Portal

Routine administration stays SSH-first. Temporary browser surfaces are created only when a workflow needs one.

Cloudflare without a Separate Control Plane

Cloudflare joins BIND and other API providers as a DNS workflow, so public DNS operations can stay in the same operational model.

External Movement Belongs to Fleet

Import/export makes workload transfer a fleet operation, keeping inventory, trust and orchestration relationships central instead of maintaining a separate migration path.

Native Infrastructure Components

Ansible, KVM, WireGuard, HAProxy, Nginx, Apache, PHP-FPM and standard Linux services remain visible and inspectable.

How it works

From Installation to Everyday Management.

One-Click keeps the setup path explicit: fetch the public bootstrap, validate the host, prepare only what is missing, load the module cache and enter the managed shell. The same Linux primitives remain visible throughout.

See the full installation flow
01Bootstrap

Fetch one-click.sh and invoke setup.

02Validate

Detect the Linux family, privileges and host state.

03Prepare

Install missing dependencies and initialise state.

04Load

Refresh or reuse the bounded module cache.

05Operate

Enter the managed System, Security, Web, Fleet and Network domains.

Public bootstrapcurl -fsSL https://raw.githubusercontent.com/SiteHUB-NG/One-Click/main/one-click.sh -o /tmp/one-click.sh && bash /tmp/one-click.sh setup && rm -f /tmp/one-click.sh
Installation documentation →
Practical guides

Keep Your Infrastructure Running.

Go deeper into the operations that follow deployment.