Skip to content
Back to search

oneclickvirt

Universal Virtualization Management Platform 可扩展的通用虚拟化管理平台,支持 Proxmox VE / LXD (GPU) / Incus (GPU) / Docker / Podman / Containerd / Qemu / Kubevirt

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday

Check it deeper on your machine

It has changed since its scan on 18 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/oneclickvirt/oneclickvirt with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/oneclickvirt/oneclickvirt'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/oneclickvirt--oneclickvirt/badge.svg)](/listings/oneclickvirt--oneclickvirt)

HTML

<a href="/listings/oneclickvirt--oneclickvirt"><img src="/api/listings/oneclickvirt--oneclickvirt/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 518 lines
  1. # OneClickVirt Virtualization Management Platform
  2. [![Build and Release oneclickvirt](https://github.com/oneclickvirt/oneclickvirt/actions/workflows/build.yml/badge.svg)](https://github.com/oneclickvirt/oneclickvirt/actions/workflows/build.yml)
  3. [![Build and Push Docker Images](https://github.com/oneclickvirt/oneclickvirt/actions/workflows/build_docker.yml/badge.svg)](https://github.com/oneclickvirt/oneclickvirt/actions/workflows/build_docker.yml)
  4. [![Integration Tests](https://github.com/oneclickvirt/oneclickvirt/actions/workflows/integration-tests.yml/badge.svg)](https://github.com/oneclickvirt/oneclickvirt/actions/workflows/integration-tests.yml)
  5. [![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Foneclickvirt%2Foneclickvirt.svg?type=shield&issueType=license)](https://app.fossa.com/projects/git%2Bgithub.com%2Foneclickvirt%2Foneclickvirt?ref=badge_shield&issueType=license) [![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Foneclickvirt%2Foneclickvirt.svg?type=shield&issueType=security)](https://app.fossa.com/projects/git%2Bgithub.com%2Foneclickvirt%2Foneclickvirt?ref=badge_shield&issueType=security)
  6. An extensible universal virtualization management platform that supports LXD, Incus, Docker, Podman, Containerd, Proxmox VE, QEMU/KVM, and KubeVirt.
  7. The web console uses Vue 3, Vite, and Element Plus, with responsive layouts checked for desktop, tablet, Android-sized, and iOS-sized viewports.
  8. ## **Language**
  9. [English Docs](README.md) | [中文文档](README_ZH.md)
  10. ## Detailed Description
  11. [www.spiritlhl.net](https://www.spiritlhl.net/en/guide/oneclickvirt/oneclickvirt_precheck.html)
  12. ## Integration Test Report
  13. The automated integration test report is available at: [oneclickvirt.github.io/oneclickvirt](https://oneclickvirt.github.io/oneclickvirt/)
  14. The report supports bilingual display (Chinese/English), light/dark theme switching, Git ref/SHA/run metadata, and server log expansion for failed cases, covering 200+ API endpoint tests including functional, permission, boundary, and security tests. See [`action_tests/`](action_tests/) for details.
  15. ## Supported Virtualization Platforms
  16. | Type ID | Platform | Instance Types | Repository |
  17. |---------|----------|----------------|------------|
  18. | `lxd` | LXD | container, vm | [oneclickvirt/lxd](https://github.com/oneclickvirt/lxd) |
  19. | `incus` | Incus | container, vm | [oneclickvirt/incus](https://github.com/oneclickvirt/incus) |
  20. | `docker` | Docker | container | [oneclickvirt/docker](https://github.com/oneclickvirt/docker) |
  21. | `podman` | Podman | container | [oneclickvirt/podman](https://github.com/oneclickvirt/podman) |
  22. | `containerd` | Containerd (nerdctl) | container | [oneclickvirt/containerd](https://github.com/oneclickvirt/containerd) |
  23. | `proxmox` | Proxmox VE | container, vm | [oneclickvirt/pve](https://github.com/oneclickvirt/pve) |
  24. | `qemu` | QEMU | vm | [oneclickvirt/qemu](https://github.com/oneclickvirt/qemu) |
  25. | `kubevirt` | KubeVirt | vm | [oneclickvirt/kubevirt](https://github.com/oneclickvirt/kubevirt) |
  26. Additional backend adapters are available for local or desktop virtualization experiments, including `orbstack`, `multipass`, `vagrant`, `virtualbox`, and `vmware`. See [`server/provider/README.md`](server/provider/README.md) for implementation details and support scope.
  27. ## Quick Deployment
  28. Avoid compiling from source whenever possible. We recommend deploying using separate binary files or directly pulling the Docker image for deployment.
  29. ### Method 0: Using the 1Panel Third-Party App Store
  30. [okxlin/appstore](https://github.com/okxlin/appstore) now includes OneClickVirt. If you already use 1Panel, follow that repository's instructions to add or synchronize the local app store, then deploy `oneclickvirt` from the local app list.
  31. ### Method 1: Using Pre-built Images
  32. Use pre-built multi-architecture images that automatically downloads the appropriate version for your system architecture.
  33. **Image Tags:**
  34. | Image Tag | Description | Use Case |
  35. |-----------|-------------|----------|
  36. | `oneclickvirt/oneclickvirt:latest` | All-in-one version (built-in database) | Quick deployment |
  37. | `oneclickvirt/oneclickvirt:20261117` | All-in-one version with specific date | Fixed version requirement |
  38. | `oneclickvirt/oneclickvirt:no-db` | Standalone database version | Without database |
  39. | `oneclickvirt/oneclickvirt:no-db-20261117` | Standalone database version with date | Without database |
  40. All images support both `linux/amd64` and `linux/arm64` architectures.
  41. <details>
  42. <summary>View All-in-One Version (Built-in Database)</summary>
  43. **Basic Usage (without domain configuration):**
  44. ```bash
  45. docker run -d \
  46. --name oneclickvirt \
  47. -p 80:80 \
  48. -p 10000-10099:10000-10099 \
  49. -e OCV_CONTROLLER_PORT_RANGE_START=10000 \
  50. -e OCV_CONTROLLER_PORT_RANGE_END=10099 \
  51. -v oneclickvirt-data:/var/lib/mysql \
  52. -v oneclickvirt-storage:/app/storage \
  53. --restart unless-stopped \
  54. oneclickvirt/oneclickvirt:latest
  55. ```
  56. **Configure Domain Access:**
  57. If you need to configure a domain, set the `FRONTEND_URL` environment variable:
  58. ```bash
  59. docker run -d \
  60. --name oneclickvirt \
  61. -p 80:80 \
  62. -p 10000-10099:10000-10099 \
  63. -e OCV_CONTROLLER_PORT_RANGE_START=10000 \
  64. -e OCV_CONTROLLER_PORT_RANGE_END=10099 \
  65. -e FRONTEND_URL="https://your-domain.com" \
  66. -v oneclickvirt-data:/var/lib/mysql \
  67. -v oneclickvirt-storage:/app/storage \
  68. --restart unless-stopped \
  69. oneclickvirt/oneclickvirt:latest
  70. ```
  71. Or using GitHub Container Registry:
  72. ```bash
  73. docker run -d \
  74. --name oneclickvirt \
  75. -p 80:80 \
  76. -p 10000-10099:10000-10099 \
  77. -e OCV_CONTROLLER_PORT_RANGE_START=10000 \
  78. -e OCV_CONTROLLER_PORT_RANGE_END=10099 \
  79. -e FRONTEND_URL="https://your-domain.com" \
  80. -v oneclickvirt-data:/var/lib/mysql \
  81. -v oneclickvirt-storage:/app/storage \
  82. --restart unless-stopped \
  83. ghcr.io/oneclickvirt/oneclickvirt:latest
  84. ```
  85. </details>
  86. <details>
  87. <summary>View Standalone Database Version</summary>
  88. Use external database for smaller image size and faster startup:
  89. ```bash
  90. docker run -d \
  91. --name oneclickvirt \
  92. -p 80:80 \
  93. -p 10000-10099:10000-10099 \
  94. -e OCV_CONTROLLER_PORT_RANGE_START=10000 \
  95. -e OCV_CONTROLLER_PORT_RANGE_END=10099 \
  96. -e FRONTEND_URL="https://your-domain.com" \
  97. -e DB_HOST="your-mysql-host" \
  98. -e DB_PORT="3306" \
  99. -e DB_NAME="oneclickvirt" \
  100. -e DB_USER="root" \
  101. -e DB_PASSWORD="your-password" \
  102. -v oneclickvirt-storage:/app/storage \
  103. --restart unless-stopped \
  104. oneclickvirt/oneclickvirt:no-db
  105. ```
  106. **Environment Variables:**
  107. - `FRONTEND_URL`: Frontend access URL (required, supports http/https)
  108. - `DB_HOST`: Database host address
  109. - `DB_PORT`: Database port (default 3306)
  110. - `DB_NAME`: Database name
  111. - `DB_USER`: Database username
  112. - `DB_PASSWORD`: Database password
  113. - `OCV_CONTROLLER_PORT_RANGE_START` / `OCV_CONTROLLER_PORT_RANGE_END`: TCP range used by controller-side Agent tunnels. Publish the identical host/container range; the documented default is `10000-10099`. Increase it only when the expected concurrent tunnel count requires more ports, because Docker expands published ranges into per-port bindings.
  114. Controller-side forwarding listens inside the panel container. The Docker `-p` range and both `OCV_CONTROLLER_PORT_RANGE_*` values must stay identical. Ports outside the configured range are rejected instead of being recorded as active but unreachable. Source or bare-metal deployments that omit both variables retain the historical `10000-65535` allocation range.
  115. The `no-db` image stores its runtime configuration at `/app/storage/config.yaml` in the `oneclickvirt-storage` volume. Reuse the same storage volume when updating the image or recreating the container; database settings entered on the initialization page and other system-level settings then survive replacement. Non-empty `DB_*` environment variables take precedence over the file, so recreations may also keep passing the same database environment. Deployments that explicitly mount `/app/config.yaml` continue to use that file first.
  116. </details>
  117. > **Note**: `FRONTEND_URL` is used to configure the frontend access address, affecting features like CORS and OAuth2 callbacks. The system will automatically detect HTTP/HTTPS protocol and adjust configurations accordingly. The protocol prefix can be either http or https.
  118. ### Method 2: Using Docker Compose
  119. <details>
  120. <summary>View Docker Compose Deployment</summary>
  121. Use Docker Compose to deploy the complete development environment with one command, using **multi-container deployment** architecture with separate frontend, backend, and database containers:
  122. ```bash
  123. git clone https://github.com/oneclickvirt/oneclickvirt.git
  124. cd oneclickvirt
  125. cat > .env << 'EOF'
  126. MYSQL_ROOT_PASSWORD=change-this-root-password
  127. MYSQL_PASSWORD=change-this-app-password
  128. EOF
  129. docker-compose up -d --build || docker compose up -d --build
  130. ```
  131. **Default Configuration:**
  132. - Frontend service: `http://localhost:8888`
  133. - Backend API: Accessed via frontend proxy
  134. - MariaDB database: Port 3306, database name `oneclickvirt`
  135. - Database credentials: `MYSQL_ROOT_PASSWORD` and `MYSQL_PASSWORD` from `.env`
  136. - Data persistence:
  137. - Database data: Docker volume `mysql_data`
  138. - Application storage: `./data/app/`
  139. **Initialization Configuration:**
  140. When accessing for the first time, you will enter the initialization interface. Please fill in the database configuration as follows:
  141. - Database Host: `mysql` (container name, not 127.0.0.1)
  142. - Database Port: `3306`
  143. - Database Name: `oneclickvirt`
  144. - Database User: `oneclickvirt`
  145. - Database Password: Use the `MYSQL_PASSWORD` value from `.env`
  146. **Custom Port (Optional):**
  147. To modify the frontend access port, edit the ports configuration in `docker-compose.yaml`:
  148. ```yaml
  149. services:
  150. web:
  151. ports:
  152. - "your-port:80" # e.g., "80:80" or "8080:80"
  153. ```
  154. For controller-side Agent tunnels, set both `OCV_CONTROLLER_PORT_RANGE_START` and `OCV_CONTROLLER_PORT_RANGE_END` in `.env`. Compose publishes the same TCP range on the `api` service automatically. Keep the range bounded to the capacity you actually need.
  155. **Stop Services:**
  156. ```bash
  157. docker-compose down
  158. ```
  159. **View Logs:**
  160. ```bash
  161. docker-compose logs -f
  162. ```
  163. **Clean Data:**
  164. ```bash
  165. docker-compose down
  166. rm -rf ./data
  167. ```
  168. </details>
  169. ### Method 3: Bare-metal Full Installer
  170. <details>
  171. <summary>View Full Installer</summary>
  172. `scripts/install_full.sh` installs the database, reverse proxy, TLS configuration, frontend, backend, and system service in one flow. It supports MySQL-compatible local databases (MySQL or MariaDB) and Caddy, Nginx, or OpenResty.
  173. The installer auto-detects common Linux and Unix-like targets, including Debian/Ubuntu, RHEL/CentOS/Rocky/Alma/Fedora/Amazon Linux, openSUSE/SLES, Arch/Manjaro, Alpine, and BSD package managers. It also detects systemd, OpenRC, rc.d/service, and no-init environments. On distributions where native MySQL packages are unavailable or unstable, the installer automatically falls back to MariaDB as the MySQL-compatible backend; use `--no-db-fallback` to disable this behavior. BSD installs require a matching release asset for the OS/architecture, otherwise use Docker/Linux or build the server from source.
  174. The domain input auto-detects protocol prefixes: enter `https://panel.example.com` to auto-enable TLS, `http://panel.example.com` to auto-disable TLS, or a plain domain to be prompted interactively.
  175. ```bash
  176. curl -fsSL https://raw.githubusercontent.com/oneclickvirt/oneclickvirt/main/scripts/install_full.sh -o install_full.sh
  177. bash install_full.sh
  178. ```
  179. For non-interactive deployment:
  180. ```bash
  181. # HTTPS with auto TLS
  182. bash install_full.sh \
  183. --non-interactive \
  184. --domain https://panel.example.com \
  185. --email admin@example.com \
  186. --db-type mariadb \
  187. --proxy caddy
  188. # HTTP only, no TLS
  189. bash install_full.sh \
  190. --non-interactive \
  191. --domain http://192.168.1.100 \
  192. --proxy caddy
  193. ```
  194. Useful automation flags:
  195. ```bash
  196. bash install_full.sh --db-wait-timeout 300
  197. bash install_full.sh --db-type mysql --no-db-fallback
  198. ```
  199. `--version` is optional. When a fixed release is needed, use the OneClickVirt
  200. timestamp tag format, for example `--version v20260925-052714`.
  201. The installer requires at least 10 GB of free disk space and 2 GB of combined memory and swap by default. It writes the generated database password to the final installation summary; save it before closing the terminal.
  202. After installation, download the standard installer to manage OneClickVirt deployments that use a systemd service:
  203. ```bash
  204. curl -fsSL https://raw.githubusercontent.com/oneclickvirt/oneclickvirt/main/scripts/install.sh -o install.sh
  205. chmod +x install.sh
  206. ./install.sh status
  207. ./install.sh logs --lines 200
  208. ./install.sh logs --follow
  209. ./install.sh upgrade
  210. ./install.sh uninstall
  211. ```
  212. `uninstall` removes the service, program, and web files while retaining `config.yaml` and `storage`; `uninstall --purge` removes the entire application directory. Neither mode removes the database, reverse proxy, or TLS certificates because other applications may share them. Non-interactive uninstall also requires `--yes`.
  213. </details>
  214. ### Controller Version Management
  215. Super administrators can open **Manage updates** in the controller page footer to view the current version, Release candidates, remote rollback versions, local backups, and copyable manual commands.
  216. - The panel can automatically update, roll back, or restart only a Linux systemd installation running as root whose controller binary and applicable Web directory are inside the controlled installation root and are not symlinks. It creates up to five local backups before switching files and attempts to restore controller/Web assets on failure. Database migrations are not rolled back automatically.
  217. - A Release must provide a `SHA256SUMS` asset. The panel downloads that manifest first, verifies the selected Linux controller archive and, when the deployment manages its controlled static directory, `web-dist.zip`, and only then extracts or changes local files. Older Releases without the manifest are shown as unavailable for automatic application; the existing script remains available for manual recovery.
  218. - Docker, Docker Compose, and source deployments are never modified by the panel. It displays commands only. This repository's Compose deployment uses `docker compose up -d --build --force-recreate api web` to rebuild API and Web while retaining the `mysql_data` named volume. Custom Docker ports, domains, environment variables, and `no-db` deployments must reuse their original container arguments after exporting them.
  219. - A reverse proxy is reloaded after a controlled systemd restart only when it is explicitly listed in `ONECLICKVIRT_PROXY_SERVICES`. Release metadata and assets try GitHub, `ONECLICKVIRT_UPDATE_API_ENDPOINTS`, and the configured CDN/API proxy endpoints in order; panel download URLs must use HTTPS.
  220. Common overrides (prefer a controlled service environment file, then restart the service):
  221. | Variable | Purpose |
  222. | --- | --- |
  223. | `ONECLICKVIRT_UPDATE_ENABLED=false` | Disables panel update, rollback, and restart actions. |
  224. | `ONECLICKVIRT_UPDATE_MODE` | Forces `systemd`, `docker`, `compose`, `source`, `embedded`, `unknown`, or `disabled`. Set `compose` explicitly when a Compose container cannot expose a reliable marker. |
  225. | `ONECLICKVIRT_UPDATE_PROXY` | Comma-separated HTTPS Release-asset/CDN proxy prefixes. |
  226. | `ONECLICKVIRT_UPDATE_API_ENDPOINTS` | Comma-separated HTTPS GitHub API or API-proxy roots. |
  227. | `ONECLICKVIRT_UPDATE_REPO` | Release repository; defaults to `oneclickvirt/oneclickvirt`. |
  228. | `ONECLICKVIRT_UPDATE_FLAVOR` | `standalone` or `allinone`; normally inferred from the installer's `SERVER_ASSET` marker. |
  229. | `ONECLICKVIRT_UPDATE_WEB` | Explicitly enables or disables replacement of the controlled static Web directory. `install_full.sh` sets this to `true` because it serves `web-dist.zip` through its reverse proxy. |
  230. | `ONECLICKVIRT_INSTALL_ROOT`, `ONECLICKVIRT_SERVER_BIN`, `ONECLICKVIRT_WEB_DIR` | Controlled install root, controller binary, and managed static Web directory. Automatic mode requires each applicable update target to remain below the install root. |
  231. | `ONECLICKVIRT_SERVICE_NAME`, `ONECLICKVIRT_SERVICE_FILE` | Controlled systemd service and unit file. |
  232. | `ONECLICKVIRT_PROXY_SERVICES` | Comma-separated systemd service names such as Nginx, OpenResty, or Caddy to reload after an update/restart. |
  233. | `ONECLICKVIRT_UPDATE_SCRIPT` | Existing installer path shown in the footer commands tab; when absent, the panel shows a download-and-run command. |
  234. | `ONECLICKVIRT_UPDATE_HEALTH_PORT` | Local `/api/v1/health` port after restart; defaults to the controller config or `8888`. |
  235. | `ONECLICKVIRT_UPDATE_ALLOW_UNVERIFIED=true` | Recovery-only opt-out for old Releases without `SHA256SUMS`; do not set it in production. |
  236. ### DeepSeek Harness Plugin
  237. ```bash
  238. dsh plugin --profile web add github:oneclickvirt/oneclickvirt
  239. ```
  240. <details>
  241. <summary>Install and use the OneClickVirt page</summary>
  242. Requires DSH `>=0.2.2-rc.1 <0.3.0` and Node.js 22.6 or newer. In Desktop, use **Plugins → Add → Install third-party plugin** with the GitHub repository, or select `dsh-plugin-oneclickvirt.tgz` from [DSH releases](https://github.com/oneclickvirt/oneclickvirt/releases/latest). The Desktop profile is managed by the app; the command above is for the Web profile.
  243. Open **OneClickVirt** in the sidebar and sign in to an existing deployment. Administrators and users can manage instances within their existing permissions, select node images and resource specifications, edit display aliases, and inspect tasks and monitoring. Switching DSH pages preserves this page. Remembered password sign-in creates a device API token; signing out clears it and revokes that device token. Existing API tokens keep their own expiry and are not revoked on sign-out. Passwords are never saved.
  244. The same native tools work in CLI/CI with `ONE_CLICK_VIRT_API_URL` and `ONE_CLICK_VIRT_API_TOKEN`; no Web UI or MCP binary is required. macOS, Windows and Linux use the same plugin. Installation does not change the running controller, database or hypervisor. See the [full guide](https://www.spiritlhl.net/en/guide/oneclickvirt/oneclickvirt_advanced_install.html#deepseek-harness-plugin) for installation, updates and credential storage.
  245. </details>
  246. ### Method 4: Build from Source
  247. <details>
  248. <summary>View Build Instructions</summary>
  249. If you need to modify the source code or build custom images:
  250. **All-in-One Version (Built-in Database):**
  251. ```bash
  252. git clone https://github.com/oneclickvirt/oneclickvirt.git
  253. cd oneclickvirt
  254. docker build -t oneclickvirt .
  255. docker run -d \
  256. --name oneclickvirt \
  257. -p 80:80 \
  258. -p 10000-10099:10000-10099 \
  259. -e OCV_CONTROLLER_PORT_RANGE_START=10000 \
  260. -e OCV_CONTROLLER_PORT_RANGE_END=10099 \
  261. -v oneclickvirt-data:/var/lib/mysql \
  262. -v oneclickvirt-storage:/app/storage \
  263. --restart unless-stopped \
  264. oneclickvirt
  265. ```
  266. Docker builds embed `scripts/install_agent.sh` automatically. If you also want the controller image to serve local agent release archives instead of redirecting to GitHub Releases, place these files in `server/assets/agent/` before `docker build`:
  267. ```text
  268. install_agent.sh
  269. oneclickvirt-agent-linux-amd64.tar.gz
  270. oneclickvirt-agent-linux-arm64.tar.gz
  271. ```
  272. **Standalone Database Version:**
  273. ```bash
  274. git clone https://github.com/oneclickvirt/oneclickvirt.git
  275. cd oneclickvirt
  276. docker build -f Dockerfile.no-db -t oneclickvirt:no-db .
  277. docker run -d \
  278. --name oneclickvirt \
  279. -p 80:80 \
  280. -p 10000-10099:10000-10099 \
  281. -e OCV_CONTROLLER_PORT_RANGE_START=10000 \
  282. -e OCV_CONTROLLER_PORT_RANGE_END=10099 \
  283. -e FRONTEND_URL="https://your-domain.com" \
  284. -e DB_HOST="your-mysql-host" \
  285. -e DB_PORT="3306" \
  286. -e DB_NAME="oneclickvirt" \
  287. -e DB_USER="root" \
  288. -e DB_PASSWORD="your-password" \
  289. -v oneclickvirt-storage:/app/storage \
  290. --restart unless-stopped \
  291. oneclickvirt:no-db
  292. ```
  293. When updating or recreating a `no-db` container, reuse the same `oneclickvirt-storage` volume. The runtime configuration remains at `/app/storage/config.yaml`, so the database does not need to be initialized again.
  294. Direct source builds of the Go controller behave the same way: local agent assets in `server/assets/agent/` are optional, and missing files fall back to the official GitHub installer/releases instead of breaking the build.
  295. </details>
  296. ## Development and Testing
  297. ### Proxmox VE integration checks
  298. The `proxmoxve` integration job uses the installer from [`oneclickvirt/pve`](https://github.com/oneclickvirt/pve). It provisions a disposable worker, runs the installer in detached phases, waits through both the kernel reboot and any scheduled `ifupdown2` bootstrap reboot, then validates the PVE runtime, bridge, NAT state, and controller-facing provider path. A lost worker connection is reported as an infrastructure skip only when the detached job cannot be observed; it is not treated as a passing module assertion. The PVE repository also runs syntax, network regression, and ShellCheck tests for its installer scripts.
  299. <details>
  300. <summary>View Development Setup</summary>
  301. ### Environment Requirements
  302. * Go 1.25.0
  303. * Node.js 22+
  304. * MySQL 5.7+
  305. * npm or yarn
  306. ### Environment Deployment
  307. 1. Build frontend
  308. ```bash
  309. cd web
  310. npm i
  311. npm run serve
  312. ```
  313. 2. Build backend
  314. ```bash
  315. cd server
  316. go mod tidy
  317. go run main.go
  318. ```
  319. 3. In development mode, there's no need to proxy the backend, as Vite already includes backend proxy requests.
  320. 4. Create an empty database named `oneclickvirt` in MySQL, and record the corresponding account and password.
  321. 5. Access the frontend address, which will automatically redirect to the initialization interface. Fill in the database information and related details, then click initialize.
  322. 6. After completing initialization, it will automatically redirect to the homepage, and you can start development and testing.
  323. ### Local Development
  324. * Frontend: [http://localhost:8080](http://localhost:8080)
  325. * Backend API: [http://localhost:8888](http://localhost:8888)
  326. * API Documentation: [http://localhost:8888/swagger/index.html](http://localhost:8888/swagger/index.html)
  327. </details>
  328. ## Initial Account
  329. The administrator account is created from the setup form during first initialization. The quick-fill action generates a random strong password each time; save the generated value before submitting the form.
  330. ## Configuration File
  331. The main configuration file is located at `server/config.yaml`
  332. ## Sponsors
  333. Thanks to the following groups and individuals for sponsoring OneClickVirt:
  334. [![Docker Sponsored OSS](https://img.shields.io/badge/Docker-Sponsored%20OSS-2496ED?logo=docker&logoColor=white)](https://hub.docker.com/r/oneclickvirt/oneclickvirt)
  335. <p>
  336. <a href="https://dartnode.com?aff=bonus">
  337. <img src="./web/src/assets/images/dartnode.png" alt="DartNode" height="44">
  338. </a>
  339. &nbsp;&nbsp;
  340. <a href="https://console.zmto.com/?affid=1524">
  341. <img src="https://console.zmto.com/templates/2019/dist/images/logo_dark.svg" alt="zmto" height="44">
  342. </a>
  343. &nbsp;&nbsp;
  344. <a href="https://community.ibm.com/zsystems/form/l1cc-oss-vm-request/">
  345. <img src="./web/src/assets/images/ibm-linuxone.png" alt="IBM LinuxONE OSS Community Cloud" height="44">
  346. </a>
  347. &nbsp;&nbsp;
  348. <a href="https://fossvps.org/">
  349. <img src="https://lowendspirit.com/uploads/userpics/793/nHSR7IOVIBO84.png" alt="fossvps" height="44">
  350. </a>
  351. &nbsp;&nbsp;
  352. <a href="https://linux.do/">
  353. <img src="https://cdn3.ldstatic.com/original/4X/d/1/4/d146c68151340881c884d95e0da4acdf369258c6.png" alt="Linux DO" height="44">
  354. </a>
  355. </p>
  356. ## LICENSE
  357. [![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Foneclickvirt%2Foneclickvirt.svg?type=large&issueType=license)](https://app.fossa.com/projects/git%2Bgithub.com%2Foneclickvirt%2Foneclickvirt?ref=badge_large&issueType=license)
  358. ## Demo Screenshots
  359. The screenshots below are generated from the current responsive frontend, including the public homepage, sponsor section, mobile layout, admin pages, and user pages.
  360. **Public homepage**
  361. ![](./.back/1.png)
  362. **Sponsors**
  363. ![](./.back/2.png)
  364. **Mobile homepage**
  365. ![](./.back/3.png)
  366. **Admin dashboard**
  367. ![](./.back/4.png)
  368. **Provider management**
  369. ![](./.back/5.png)
  370. **User dashboard**
  371. ![](./.back/6.png)
  372. **User instances**
  373. ![](./.back/7.png)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.