CyberTools Admin – Install & Release Guide
v1.5.0 Rollout (Compiled Edition · Option A)
Modules: CyberBackup · Admin Restore · CyberTools Admin Menu
Built for real outages: simulate, back up, and restore without guessing.
What this guide covers
🧩 Quick Requirements
- CyberPanel VPS (Ubuntu 20.04+ / 22.04+)
- Root SSH access
- 10–15 GB free disk space recommended
- SFTP client (FileZilla / WinSCP) to upload the package
1. Overview
CyberTools Admin is a CLI companion for CyberPanel servers. It adds:
- CyberBackup (admin-backup): project + system backup tools (simulate / safe / direct modes)
- Admin Restore (admin-restore): guided restore with clear prompts and logging
- CyberTools Admin Menu (admin-menu): color menu hub, autostart, timeout, dependency helpers
Customers receive compiled binaries only. Source scripts remain on your development system. Licensing is handled via standard customer license prompts during install.
2. Requirements & Assumptions
- Server: Ubuntu 20.04+ / 22.04+ with CyberPanel installed
- Access: root SSH (server admins only)
- Tools:
tar,gzip,bash, Python 3 - Python libraries:
paramiko,django,mysqlclient(installed via menu) - SFTP upload access to
/root
3. Package Contents (What the Customer Receives)
You deliver a tarball for each server, example:
CyberToolsAdmin_v1.5.0_SERVER01.tar.gz
Inside:
/root/cybertoolsadmin/ admin-menu (compiled binary) admin-backup (compiled binary) admin-restore (compiled binary) config.conf.sample dependencies.txt system-deps.txt installer.sh LICENSE_README.txt VERSION.txt
Customers should not receive *.dev or *.x.c files.
4. – Customer Install (Compiled Only)
1) SSH as root → 2) upload tar.gz → 3) extract → 4) run installer.sh → 5) edit config.conf → 6) install deps → 7) simulate backup & restore
4.1 Log in as root via SSH
ssh root@YOUR_SERVER_IP pwd # should show /root
4.2 Upload the release archive
Open FileZilla / WinSCP (or similar).
- Host:
YOUR_SERVER_IP - User:
root - Port:
22
On the server side, go to /root.
Upload CyberToolsAdmin_v1.5.0_SERVER01.tar.gz into /root.
4.3 Unpack the release
cd /root tar -xzvf CyberToolsAdmin_v1.5.0_*.tar.gz
This will create /root/cybertoolsadmin with the compiled binaries and helper files.
4.4 Run the installer (installer.sh)
This is the important part. The installer script wires up the license, config, and autostart.
cd /root/cybertoolsadmin chmod +x installer.sh ./installer.sh
Typical tasks performed by installer.sh:
- Create the license folder (if missing):
mkdir -p /root/.cybertoolsadmin
- Prompt for the license phrase you emailed to the customer and save it as:
/root/.cybertoolsadmin/license.key
- Compute a SHA256 hash of that file and store:
/root/cybertoolsadmin/.valid_hash
- Copy
config.conf.sampletoconfig.confif needed. - Ensure a main menu wrapper exists:
/root/admin-menu → /root/cybertoolsadmin/admin-menu
- Offer autostart at root login:
# CyberToolsAdmin Autostart if [[ $- == *i* ]] && [ -x /root/admin-menu ]; then /root/admin-menu fi
What the customer should see
• Confirm the license
• Show config.conf location
• Prompt them to run
/root/admin-menu
4.5 Edit config.conf
Ask the customer to open the config file:
nano /root/cybertoolsadmin/config.conf
Example contents:
# === CyberToolsAdmin Config === BACKUPDIR="/home/backup" PROJECTDIR="/home/sealproven.com/public_html/sealproven-saas-pilot" LOGFILE="/var/log/cybertools-backup.log" KEEP_PROJECT_BACKUPS=5 KEEP_SYSTEM_BACKUPS=3 ENABLE_AUTOPRUNE="yes" VERSION="1.5.0" AUTHOR="Your Name" RELEASE_DATE="2025-11-06" PROJECT_STEM="sealproven-saas"
Key points for customers:
BACKUPDIR– archive storage locationPROJECTDIR– main site/app directory to protectKEEP_PROJECT_BACKUPS,KEEP_SYSTEM_BACKUPS– retention levelsENABLE_AUTOPRUNE="yes"– auto-delete old archives
Tip: Avoid spaces or hidden Windows characters. Retype paths directly if needed.
4.6 First run & dependency install
/root/admin-menu
At the top they should see:
- CyberTools Admin – v1.5.0
- License Status: VALID
- Autostart: ENABLED or DISABLED
- Dependency status for paramiko, django, mysqlclient
If any Python deps are missing, press I.
4.7 Test a project backup (simulate)
1) CyberBackup – Backup & Restore Tools 5) Backup Project (PROJECTDIR) S # simulate only
The tool prints included files without writing an archive.
For a real backup:
F # full backup
4.8 Test restore (simulation)
6) Restore a previous project backup S # simulate
This confirms backups are valid without touching the live project.
