mirror of https://github.com/MengMengCode/CLICD.git synced 2026-08-05 05:36:07 +08:00

Files

T

MengMengCode a45e063fc2 Add comprehensive documentation for CLICD features and operations

- Introduced Container Management documentation covering lifecycle operations, resource management, and console access.
- Added Dashboard documentation detailing metrics and related APIs.
- Created Host Report documentation summarizing host environment and resource status.
- Included Image Management documentation for template handling and management actions.
- Documented Networking and Routing features including NAT4 and IPv6 management.
- Added Security Alerts documentation outlining alert scenarios and API usage.
- Created Snapshot Management documentation for snapshot operations and scheduling.
- Documented Sub-user management for granting access to specific containers.
- Added Configuration guide detailing runtime settings and security recommendations.
- Created Installation guide for setting up CLICD with requirements and steps.
- Added Introduction and Quick Start guides for new users.
- Documented Upgrade process with version checking and pre-upgrade checklist.
- Created Deployment guide for service exposure and firewall recommendations.
- Added FAQ section addressing common questions and concerns.
- Documented Troubleshooting steps for common issues encountered.

2026-06-10 00:42:06 +08:00

1.1 KiB

Raw Blame History

FAQ

Which version does the installer install by default?

It installs the latest version from GitHub Releases. The script default is CLICD_VERSION=latest, which downloads the Linux AMD64 artifact from releases/latest.

Can I pin a specific version?

Yes:

curl -fsSL https://raw.githubusercontent.com/MengMengCode/CLICD/main/install.sh | sudo CLICD_VERSION=v1.1.6 sh

Can sub-users see every container?

No. Sub-users only see containers authorized by the administrator.

No. API keys are created on the API Integration page for programmatic access. The login password is used for the web panel.

What happens after a container reaches its traffic limit?

The container is automatically shut down to avoid further overage. The administrator can adjust the limit or reset traffic usage.

Why is IPv6 unreachable after assignment?

IPv6 reachability depends on the host and upstream network. Confirm that the host has a routable IPv6 prefix and that routing, firewall, neighbor discovery, or proxy configuration is correct.

1.1 KiB Raw Blame History

FAQ