You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[okxlin/appstore](https://github.com/okxlin/appstore) now includes OneClickVirt. If you already use 1Panel, add or synchronize that local app store, then deploy `oneclickvirt` from the local app list.
Copy file name to clipboardExpand all lines: docs/en/guide/dashboard.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,10 @@ Stars and forks are welcome. Everything listed here is open source. If you redis
30
30
31
31
https://github.com/oneclickvirt/oneclickvirt
32
32
33
+
## 1Panel Third-Party App Store
34
+
35
+
[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.
### Installation via the 1Panel Third-Party App Store
35
+
36
+
[okxlin/appstore](https://github.com/okxlin/appstore) now includes OneClickVirt. This repository is an unofficial 1Panel app store adaptation repository. 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.
37
+
34
38
### Installation via Pre-compiled Binary Files
35
39
36
40
Two methods are distinguished here:
@@ -564,6 +568,6 @@ Admin123!@#
564
568
565
569
During the initialization process, all image seed data is loaded into the database by default, but by default only ```debian``` and ```alpine``` related version images are enabled. This is to avoid user selection difficulties caused by too many enabled images.
566
570
567
-
If you need additional types of images, you need to search by type, architecture, and version in the system image management interface under administrator privileges and enable them.
571
+
If you need additional types of images, you need to search by type, architecture, and version in the system image management interface under administrator privileges and enable them. Windows, Android, macOS, and other non-Linux/BSD images are also imported as preset seeds, but they are disabled by default and have higher CPU, memory, and disk requirements to prevent accidental creation on low-end nodes. Before enabling these images, confirm that the target provider satisfies the required nested virtualization, disk space, KVM, or Docker special runtime conditions.
568
572
569
573
After initialization, please immediately change the default administrator username and password, and disable or delete the default enabled test user ```testuser```. This can be donein the administrator's user management page.
Copy file name to clipboardExpand all lines: docs/en/guide/oneclickvirt/oneclickvirt_precheck.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ No Port Mapping
57
57
58
58
- Traffic Statistics: Integrates IP-level and network interface-level precise network traffic statistics. Forces traffic data synchronization during sensitive operations to ensure data accuracy
59
59
60
-
-Monthly traffic usage statistics reset at the beginning of each month. Supports traffic statistics and limits at user, instance, and Provider levels
60
+
-Traffic reset days can be configured per provider. Leaving the field empty follows the natural month and resets on the 1st day of each month. Supports traffic statistics and limits at user, instance, and Provider levels
61
61
62
62
- Invitation Code System: Supports non-public registration invitation mechanism, with different resource quota limits based on user levels
Copy file name to clipboardExpand all lines: docs/en/guide/oneclickvirt/oneclickvirt_usage.md
+21-5Lines changed: 21 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -156,7 +156,7 @@ Not recommended to modify the mapping method unless you know what this setting d
156
156
157
157

158
158
159
-
Simply put, this sets the maximum bandwidth for instances created on the node and the total available traffic calculated on a natural-month basis. Traffic monitoring and traffic statistics are not enabled by default.
159
+
Simply put, this sets the maximum bandwidth for instances created on the node and the total available traffic quota. Traffic monitoring and traffic statistics are not enabled by default. The traffic cycle follows the natural month by default and resets on the 1st day of each month. You can also choose a monthly reset day in the Expiry Settings section later; if 29, 30, or 31 is selected, shorter months automatically use the last day of that month.
160
160
161
161
#### agent (Recommended)
162
162
@@ -204,6 +204,8 @@ Only after enabling traffic control will the traffic monitoring management butto
204
204
205
205

206
206
207
+
The traffic reset day affects current-cycle statistics, user/instance/provider traffic limit checks, and recovery queueing for instances automatically stopped because of traffic overuse. When a provider reaches its reset day, the system first clears that provider's traffic-limit state, then recalculates user and instance limits. Instances that are no longer over the limit and have no other freeze reason will automatically receive a start task.
208
+
207
209
### Level Restrictions (Required)
208
210
209
211

@@ -214,16 +216,30 @@ During the actual instance creation process, the node-level level restrictions w
214
216
215
217
This setting is to specialize the configuration limits of instances that users of corresponding levels can create on the current node, avoiding situations where global limits are not suitable for the current node. Global limits can be set in system configuration and are generally used for user account-level resource usage restrictions.
216
218
217
-
### Advanced Settings (Optional)
219
+
### Expiry Settings (Optional)
218
220
219
221

220
222
221
-

222
-
223
223
Expiration time:
224
224
225
225
Prevents users from continuing to operate expired nodes. Expired nodes will be automatically frozen, at which time corresponding instances will not allow any operations but will not be automatically deleted. If a node is frozen, please clean and delete it in time.
226
226
227
+
Traffic reset day:
228
+
229
+
Leave it empty to follow the natural month, which starts a new traffic cycle on the 1st day of each month. You can also set any day from 1 to 31. The system calculates the current cycle, next reset time, and traffic-overlimit recovery separately for each provider.
230
+
231
+
Instance expiration handling:
232
+
233
+
When an instance expires, it can be frozen, stopped, automatically extended, or left for cleanup according to the provider setting. If an instance was automatically stopped because it expired, a successful check-in renewal creates a start task automatically, so the administrator does not need to start it manually.
234
+
235
+
Check-in renewal:
236
+
237
+
The previous check-in renewal tab has been merged into Expiry Settings. Configure check-in availability, renewal days, consecutive check-in rewards, and related limits here. After a successful check-in extends the expiration time, the system also clears the freeze caused by expiration. If the instance was stopped only because of expiration, it enters the start queue automatically.
238
+
239
+
### Advanced Settings (Optional)
240
+
241
+

242
+
227
243
Task concurrency control:
228
244
229
245
Default is single-threaded serial execution. At the same time, only one add/delete/modify task (corresponding to instance creation, deletion, and reset operations) will exist.
@@ -532,4 +548,4 @@ Detailed configuration for system log recording, based on the zap log library.
532
548
- `show-line`: Whether to display the filename and line number of log calls
533
549
- `stacktrace-key`: Key name for stack trace information
534
550
535
-
Note: When debugging issues, `level` should be set to `debug` to obtain detailed log information.
551
+
Note: When debugging issues, `level` should be set to `debug` to obtain detailed log information.
0 commit comments