npmapps 1.0.13 → 1.0.15

package/app/nginxManagement/backend/nginx-1.28.0/docs/README.md

@@ -1,230 +0,0 @@
-<picture>
-  <source media="(prefers-color-scheme: dark)" srcset="https://github.com/user-attachments/assets/9335b488-ffcc-4157-8364-2370a0b70ad0">
-  <source media="(prefers-color-scheme: light)" srcset="https://github.com/user-attachments/assets/3a7eeb08-1133-47f5-859c-fad4f5a6a013">
-  <img alt="NGINX Banner">
-</picture>
-
-NGINX (pronounced "engine x" or "en-jin-eks") is the world's most popular Web Server, high performance Load Balancer, Reverse Proxy, API Gateway and Content Cache.
-
-NGINX is free and open source software, distributed under the terms of a simplified [2-clause BSD-like license](LICENSE).
-
-Enterprise distributions, commercial support and training are available from [F5, Inc](https://www.f5.com/products/nginx).
-
-> [!IMPORTANT]
-> The goal of this README is to provide a basic, structured introduction to NGINX for novice users. Please refer to the [full NGINX documentation](https://nginx.org/en/docs/) for detailed information on [installing](https://nginx.org/en/docs/install.html), [building](https://nginx.org/en/docs/configure.html), [configuring](https://nginx.org/en/docs/dirindex.html), [debugging](https://nginx.org/en/docs/debugging_log.html), and more. These documentation pages also contain a more detailed [Beginners Guide](https://nginx.org/en/docs/beginners_guide.html), How-Tos, [Development guide](https://nginx.org/en/docs/dev/development_guide.html), and a complete module and [directive reference](https://nginx.org/en/docs/dirindex.html).
-
-# Table of contents
-- [How it works](#how-it-works)
-  - [Modules](#modules)
-  - [Configurations](#configurations)
-  - [Runtime](#runtime)
-- [Downloading and installing](#downloading-and-installing)
-  - [Stable and Mainline binaries](#stable-and-mainline-binaries)
-  - [Linux binary installation process](#linux-binary-installation-process)
-  - [FreeBSD installation process](#freebsd-installation-process)
-  - [Windows executables](#windows-executables)
-  - [Dynamic modules](#dynamic-modules)
-- [Getting started with NGINX](#getting-started-with-nginx)
-  - [Installing SSL certificates and enabling TLS encryption](#installing-ssl-certificates-and-enabling-tls-encryption)
-  - [Load Balancing](#load-balancing)
-  - [Rate limiting](#rate-limiting)
-  - [Content caching](#content-caching)
-- [Building from source](#building-from-source)
-  - [Installing dependencies](#installing-dependencies)
-  - [Cloning the NGINX GitHub repository](#cloning-the-nginx-github-repository)
-  - [Configuring the build](#configuring-the-build)
-  - [Compiling](#compiling)
-  - [Location of binary and installation](#location-of-binary-and-installation)
-  - [Running and testing the installed binary](#running-and-testing-the-installed-binary)
-- [Asking questions and reporting issues](#asking-questions-and-reporting-issues)
-- [Contributing code](#contributing-code)
-- [Additional help and resources](#additional-help-and-resources)
-- [Changelog](#changelog)
-- [License](#license)
-
-# How it works
-NGINX is installed software with binary packages available for all major operating systems and Linux distributions. See [Tested OS and Platforms](https://nginx.org/en/#tested_os_and_platforms) for a full list of compatible systems.
-
-> [!IMPORTANT]
-> While nearly all popular Linux-based operating systems are distributed with a community version of nginx, we highly advise installation and usage of official [packages](https://nginx.org/en/linux_packages.html) or sources from this repository. Doing so ensures that you're using the most recent release or source code, including the latest feature-set, fixes and security patches.
-
-## Modules
-NGINX is comprised of individual modules, each extending core functionality by providing additional, configurable features. See "Modules reference" at the bottom of [nginx documentation](https://nginx.org/en/docs/) for a complete list of official modules.
-
-NGINX modules can be built and distributed as static or dynamic modules. Static modules are defined at build-time, compiled, and distributed in the resulting binaries. See [Dynamic Modules](#dynamic-modules) for more information on how they work, as well as, how to obtain, install, and configure them.
-
-> [!TIP]
-> You can issue the following command to see which static modules your NGINX binaries were built with:
-```bash
-nginx -V
-```
-> See [Configuring the build](#configuring-the-build) for information on how to include specific Static modules into your nginx build.
-
-
-## Configurations
-NGINX is highly flexible and configurable. Provisioning the software is achieved via text-based config file(s) accepting parameters called "[Directives](https://nginx.org/en/docs/dirindex.html)". See [Configuration File's Structure](https://nginx.org/en/docs/beginners_guide.html#conf_structure) for a comprehensive description of how NGINX configuration files work.
-
-> [!NOTE]
-> The set of directives available to your distribution of NGINX is dependent on which [modules](#modules) have been made available to it.
-
-## Runtime
-Rather than running in a single, monolithic process, NGINX is architected to scale beyond Operating System process limitations by operating as a collection of processes. They include:
-- A "master" process that maintains worker processes, as well as, reads and evaluates configuration files.
-- One or more "worker" processes that process data (eg. HTTP requests).
-
-The number of [worker processes](https://nginx.org/en/docs/ngx_core_module.html#worker_processes) is defined in the configuration file and may be fixed for a given configuration or automatically adjusted to the number of available CPU cores. In most cases, the latter option optimally balances load across available system resources, as NGINX is designed to efficiently distribute work across all worker processes.
-
-> [!TIP]
-> Processes synchronize data through shared memory. For this reason, many NGINX directives require the allocation of shared memory zones. As an example, when configuring [rate limiting](https://nginx.org/en/docs/http/ngx_http_limit_req_module.html#limit_req), connecting clients may need to be tracked in a [common memory zone](https://nginx.org/en/docs/http/ngx_http_limit_req_module.html#limit_req_zone) so all worker processes can know how many times a particular client has accessed the server in a span of time.
-
-# Downloading and installing
-Follow these steps to download and install precompiled NGINX binaries. You may also choose to [build NGINX locally from source code](#building-from-source).
-
-## Stable and Mainline binaries
-NGINX binaries are built and distributed in two versions: stable and mainline. Stable binaries are built from stable branches and only contain critical fixes backported from the mainline version. Mainline binaries are built from the [master branch](https://github.com/nginx/nginx/tree/master) and contain the latest features and bugfixes. You'll need to [decide which is appropriate for your purposes](https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-open-source/#choosing-between-a-stable-or-a-mainline-version).
-
-## Linux binary installation process
-The NGINX binary installation process takes advantage of package managers native to specific Linux distributions. For this reason, first-time installations involve adding the official NGINX package repository to your system's package manager. Follow [these steps](https://nginx.org/en/linux_packages.html) to download, verify, and install NGINX binaries using the package manager appropriate for your Linux distribution.
-
-### Upgrades
-Future upgrades to the latest version can be managed using the same package manager without the need to manually download and verify binaries.
-
-## FreeBSD installation process
-For more information on installing NGINX on FreeBSD system, visit https://nginx.org/en/docs/install.html
-
-## Windows executables
-Windows executables for mainline and stable releases can be found on the main [NGINX download page](https://nginx.org/en/download.html). Note that the current implementation of NGINX for Windows is at the Proof-of-Concept stage and should only be used for development and testing purposes. For additional information, please see [nginx for Windows](https://nginx.org/en/docs/windows.html).
-
-## Dynamic modules
-NGINX version 1.9.11 added support for [Dynamic Modules](https://nginx.org/en/docs/ngx_core_module.html#load_module). Unlike Static modules, dynamically built modules can be downloaded, installed, and configured after the core NGINX binaries have been built. [Official dynamic module binaries](https://nginx.org/en/linux_packages.html#dynmodules) are available from the same package repository as the core NGINX binaries described in previous steps.
-
-> [!TIP]
-> [NGINX JavaScript (njs)](https://github.com/nginx/njs), is a popular NGINX dynamic module that enables the extension of core NGINX functionality using familiar JavaScript syntax.
-
-> [!IMPORTANT]
-> If desired, dynamic modules can also be built statically into NGINX at compile time.
-
-# Getting started with NGINX
-For a gentle introduction to NGINX basics, please see our [Beginner’s Guide](https://nginx.org/en/docs/beginners_guide.html).
-
-## Installing SSL certificates and enabling TLS encryption
-See [Configuring HTTPS servers](https://nginx.org/en/docs/http/configuring_https_servers.html) for a quick guide on how to enable secure traffic to your NGINX installation.
-
-## Load Balancing
-For a quick start guide on configuring NGINX as a Load Balancer, please see [Using nginx as HTTP load balancer](https://nginx.org/en/docs/http/load_balancing.html).
-
-## Rate limiting
-See our [Rate Limiting with NGINX](https://blog.nginx.org/blog/rate-limiting-nginx) blog post for an overview of core concepts for provisioning NGINX as an API Gateway.
-
-## Content caching
-See [A Guide to Caching with NGINX and NGINX Plus](https://blog.nginx.org/blog/nginx-caching-guide) blog post for an overview of how to use NGINX as a content cache (e.g. edge server of a content delivery network).
-
-# Building from source
-The following steps can be used to build NGINX from source code available in this repository.
-
-## Installing dependencies
-Most Linux distributions will require several dependencies to be installed in order to build NGINX. The following instructions are specific to the `apt` package manager, widely available on most Ubuntu/Debian distributions and their derivatives.
-
-> [!TIP]
-> It is always a good idea to update your package repository lists prior to installing new packages.
-> ```bash
-> sudo apt update
-> ```
-
-### Installing compiler and make utility
-Use the following command to install the GNU C compiler and Make utility.
-
-```bash
-sudo apt install gcc make
-```
-
-### Installing dependency libraries
-
-```bash
-sudo apt install libpcre3-dev zlib1g-dev
-```
-
-> [!WARNING]
-> This is the minimal set of dependency libraries needed to build NGINX with rewriting and gzip capabilities. Other dependencies may be required if you choose to build NGINX with additional modules. Monitor the output of the `configure` command discussed in the following sections for information on which modules may be missing. For example, if you plan to use SSL certificates to encrypt traffic with TLS, you'll need to install the OpenSSL library. To do so, issue the following command.
-
->```bash
->sudo apt install libssl-dev
-
-## Cloning the NGINX GitHub repository
-Using your preferred method, clone the NGINX repository into your development directory. See [Cloning a GitHub Repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) for additional help.
-
-```bash
-git clone https://github.com/nginx/nginx.git
-```
-
-## Configuring the build
-Prior to building NGINX, you must run the `configure` script with [appropriate flags](https://nginx.org/en/docs/configure.html). This will generate a Makefile in your NGINX source root directory that can then be used to compile NGINX with [options specified during configuration](https://nginx.org/en/docs/configure.html).
-
-From the NGINX source code repository's root directory:
-
-```bash
-auto/configure
-```
-
-> [!IMPORTANT]
-> Configuring the build without any flags will compile NGINX with the default set of options. Please refer to https://nginx.org/en/docs/configure.html for a full list of available build configuration options.
-
-## Compiling
-The `configure` script will generate a `Makefile` in the NGINX source root directory upon successful execution. To compile NGINX into a binary, issue the following command from that same directory:
-
-```bash
-make
-```
-
-## Location of binary and installation
-After successful compilation, a binary will be generated at `<NGINX_SRC_ROOT_DIR>/objs/nginx`. To install this binary, issue the following command from the source root directory:
-
-```bash
-sudo make install
-```
-
-> [!IMPORTANT]
-> The binary will be installed into the `/usr/local/nginx/` directory.
-
-## Running and testing the installed binary
-To run the installed binary, issue the following command:
-
-```bash
-sudo /usr/local/nginx/sbin/nginx
-```
-
-You may test NGINX operation using `curl`.
-
-```bash
-curl localhost
-```
-
-The output of which should start with:
-
-```html
-<!DOCTYPE html>
-<html>
-<head>
-<title>Welcome to nginx!</title>
-```
-
-# Asking questions and reporting issues
-We encourage you to engage with us.
-- [NGINX GitHub Discussions](https://github.com/nginx/nginx/discussions), is the go-to place to start asking questions and sharing your thoughts.
-- Our [GitHub Issues](https://github.com/nginx/nginx/issues) page offers space to submit and discuss specific issues, report bugs, and suggest enhancements.
-
-# Contributing code
-Please see the [Contributing](CONTRIBUTING.md) guide for information on how to contribute code.
-
-# Additional help and resources
-- See the [NGINX Community Blog](https://blog.nginx.org/) for more tips, tricks and HOW-TOs related to NGINX and related projects.
-- Access [nginx.org](https://nginx.org/), your go-to source for all documentation, information and software related to the NGINX suite of projects.
-
-# Changelog
-See our [changelog](https://nginx.org/en/CHANGES) to keep track of updates.
-
-# License
-[2-clause BSD-like license](LICENSE)
-
----
-Additional documentation available at: https://nginx.org/en/docs

package/app/nginxManagement/backend/nginx-1.28.0/docs/SECURITY.md

@@ -1,103 +0,0 @@
-# Security Policy
-
-This document provides an overview of security concerns related to nginx
-deployments, focusing on confidentiality, integrity, availability, and the
-implications of configurations and misconfigurations.
-
-## Reporting a Vulnerability
-
-Please report any vulnerabilities via one of the following methods
-(in order of preference):
-
-1. [Report a vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)
-within this repository. We are using the GitHub workflow that allows us to
-manage vulnerabilities in a private manner and interact with reporters
-securely.
-
-2. [Report directly to F5](https://www.f5.com/services/support/report-a-vulnerability).
-
-3. Report via email to security-alert@nginx.org.
-This method will be deprecated in the future.
-
-### Vulnerability Disclosure and Fix Process
-
-The nginx team expects that all suspected vulnerabilities be reported
-privately via the
-[Reporting a Vulnerability](SECURITY.md#reporting-a-vulnerability) guidelines.
-If a publicly released vulnerability is reported, we
-may request to handle it according to the private disclosure process.
-If the reporter agrees, we will follow the private disclosure process.
-
-Security fixes will be applied to all supported stable releases, as well
-as the mainline version, as applicable. We recommend using the most recent
-mainline or stable release of nginx. Fixes are created and tested by the core
-team using a GitHub private fork for security. If necessary, the reporter
-may be invited to contribute to the fork and assist with the solution.
-
-The nginx team is committed to responsible information disclosure with
-sufficient detail, such as the CVSS score and vector. Privately disclosed
-vulnerabilities are embargoed by default until the fix is released.
-Communications and fixes remain private until made public. As nginx is
-supported by F5, we generally follow the
-[F5 security vulnerability response policy](https://my.f5.com/manage/s/article/K4602).
-
-### Vulnerability Disclosure and Fix Service Level Objectives
-
-- We will acknowledge all vulnerability reports within 1 to 3 days.
-- Fixes will be developed and released within 90 days from the date of
-disclosure. If an extension is needed, we will work with the disclosing person.
-- Publicly disclosed (i.e., Zero-Day vulnerabilities) will be addressed ASAP.
-
-## Confidentiality, Integrity, and Availability
-
-### Confidentiality and Integrity
-
-Vulnerabilities compromising data confidentiality or integrity are considered
-the highest priority. Any issue leading to unauthorized data access, leaks, or
-manipulation will trigger the security release process.
-
-### Availability
-
-Availability issues must meet the following criteria to trigger the security
-release process:
-- Is present in a standard module included with nginx.
-- Arises from traffic that the module is designed to handle.
-- Resource exhaustion issues are not mitigated by existing timeout, rate
-limiting, or buffer size configurations, or applying changes is impractical.
-- Results in highly asymmetric, extreme resource consumption.
-
-Availability issues excluded from the security release process:
-- Local file content or upstream response content resulting only in worker
-process termination.
-- Issues with experimental features which result only in availability impact.
-
-## Trusted Configurations and Misconfigurations
-
-In nginx, configuration files, modules, certificate/key pairs, nginx JavaScript,
-and local file content are considered trusted sources. Issues arising from
-loading or execution of these trusted components are not considered
-vulnerabilities. Operators are responsible for securing and maintaining the
-integrity of these sources. Misconfigurations can create vulnerabilities, and
-operators should implement configurations according to best practices, review
-them regularly, and apply security updates.
-
-## Data Plane vs. Control Plane
-
-The data plane handles traffic through nginx, directly interacting with user
-data. nginx inherently trusts the content and instructions from upstream
-servers. The control plane governs configuration, management, and orchestration.
-Misconfigurations or vulnerabilities in the control plane can cause improper
-behavior in the data plane.
-
-## Modules Under Scope
-
-The policy applies to all nginx modules included in this repository. Security
-considerations and attack vectors for each module will be identified, with
-recommended configurations to mitigate risks.
-
-## Debug Logging and Core Files
-
-Debug logs and core files produced by nginx may contain un-sanitized data,
-including sensitive information like client requests, server configurations,
-and private key material. These artifacts must be handled carefully to avoid
-exposing confidential data.

package/app/nginxManagement/backend/nginx-1.28.0/docs/zlib.LICENSE

@@ -1,20 +0,0 @@
- (C) 1995-2024 Jean-loup Gailly and Mark Adler
-
-  This software is provided 'as-is', without any express or implied
-  warranty.  In no event will the authors be held liable for any damages
-  arising from the use of this software.
-
-  Permission is granted to anyone to use this software for any purpose,
-  including commercial applications, and to alter it and redistribute it
-  freely, subject to the following restrictions:
-
-  1. The origin of this software must not be misrepresented; you must not
-     claim that you wrote the original software. If you use this software
-     in a product, an acknowledgment in the product documentation would be
-     appreciated but is not required.
-  2. Altered source versions must be plainly marked as such, and must not be
-     misrepresented as being the original software.
-  3. This notice may not be removed or altered from any source distribution.
-
-  Jean-loup Gailly        Mark Adler
-  jloup@gzip.org          madler@alumni.caltech.edu

package/app/nginxManagement/backend/nginx-1.28.0/html/50x.html

@@ -1,19 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-<title>Error</title>
-<style>
-html { color-scheme: light dark; }
-body { width: 35em; margin: 0 auto;
-font-family: Tahoma, Verdana, Arial, sans-serif; }
-</style>
-</head>
-<body>
-<h1>An error occurred.</h1>
-<p>Sorry, the page you are looking for is currently unavailable.<br/>
-Please try again later.</p>
-<p>If you are the system administrator of this resource then you should check
-the error log for details.</p>
-<p><em>Faithfully yours, nginx.</em></p>
-</body>
-</html>

package/app/nginxManagement/backend/nginx-1.28.0/html/index.html

@@ -1,23 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-<title>Welcome to nginx!</title>
-<style>
-html { color-scheme: light dark; }
-body { width: 35em; margin: 0 auto;
-font-family: Tahoma, Verdana, Arial, sans-serif; }
-</style>
-</head>
-<body>
-<h1>Welcome to nginx!</h1>
-<p>If you see this page, the nginx web server is successfully installed and
-working. Further configuration is required.</p>
-
-<p>For online documentation and support please refer to
-<a href="http://nginx.org/">nginx.org</a>.<br/>
-Commercial support is available at
-<a href="http://nginx.com/">nginx.com</a>.</p>
-
-<p><em>Thank you for using nginx.</em></p>
-</body>
-</html>

package/app/nginxManagement/backend/nginx-1.28.0/logs/error.log

@@ -1,33 +0,0 @@
-2025/07/02 10:38:20 [emerg] 15296#27856: invalid port in upstream "localhost:80801" in C:\Users\w1768\Documents\wk\web\nginxManagement\backend\nginx-1.28.0/conf/api.conf:7
-2025/07/02 10:38:25 [emerg] 34464#33708: invalid port in upstream "localhost:80801" in C:\Users\w1768\Documents\wk\web\nginxManagement\backend\nginx-1.28.0/conf/api.conf:7
-2025/07/02 10:39:42 [notice] 14620#808: signal process started
-2025/07/02 10:39:42 [error] 14620#808: invalid PID number "" in "C:\Users\w1768\Documents\wk\web\nginxManagement\backend\nginx-1.28.0/logs/nginx.pid"
-2025/07/02 10:43:43 [notice] 28692#33032: signal process started
-2025/07/02 10:43:43 [error] 28692#33032: invalid PID number "" in "C:\Users\w1768\Documents\wk\web\nginxManagement\backend\nginx-1.28.0/logs/nginx.pid"
-2025/07/02 10:43:45 [notice] 31940#3284: signal process started
-2025/07/02 10:43:45 [error] 31940#3284: invalid PID number "" in "C:\Users\w1768\Documents\wk\web\nginxManagement\backend\nginx-1.28.0/logs/nginx.pid"
-2025/07/02 10:43:48 [notice] 26348#28536: signal process started
-2025/07/02 10:43:48 [error] 26348#28536: invalid PID number "" in "C:\Users\w1768\Documents\wk\web\nginxManagement\backend\nginx-1.28.0/logs/nginx.pid"
-2025/07/02 10:45:24 [notice] 14632#32912: signal process started
-2025/07/02 10:45:24 [error] 14632#32912: invalid PID number "" in "C:\Users\w1768\Documents\wk\web\nginxManagement\backend\nginx-1.28.0/logs/nginx.pid"
-2025/07/02 10:47:53 [notice] 31088#29580: signal process started
-2025/07/02 10:48:04 [notice] 13636#28108: signal process started
-2025/07/02 10:48:06 [notice] 3644#32680: signal process started
-2025/07/03 09:13:00 [notice] 28356#28164: signal process started
-2025/07/03 10:05:23 [notice] 31992#12720: signal process started
-2025/07/03 10:11:17 [notice] 29132#19404: signal process started
-2025/07/03 10:49:02 [notice] 10400#28508: signal process started
-2025/07/03 10:52:30 [notice] 33048#30396: signal process started
-2025/07/03 10:52:37 [notice] 16144#27736: signal process started
-2025/07/03 10:52:53 [notice] 26948#27324: signal process started
-2025/07/03 10:53:20 [notice] 30212#30396: signal process started
-2025/07/03 10:53:31 [notice] 34408#12892: signal process started
-2025/07/03 10:53:36 [notice] 27200#29132: signal process started
-2025/07/03 10:55:30 [notice] 25312#31604: signal process started
-2025/07/03 10:55:55 [notice] 10332#29032: signal process started
-2025/07/03 10:55:55 [error] 10332#29032: OpenEvent("Global\ngx_stop_14148") failed (2: The system cannot find the file specified)
-2025/07/03 10:57:33 [notice] 25464#17272: signal process started
-2025/07/03 10:57:44 [notice] 1416#31524: signal process started
-2025/07/03 10:58:07 [notice] 17908#27604: signal process started
-2025/07/03 11:02:22 [notice] 19508#5724: signal process started
-2025/07/03 11:02:49 [notice] 19516#28348: signal process started

package/app/nginxManagement/frontend/dist/assets/index-AG5xSNXD.css

@@ -1 +0,0 @@
-.card-header[data-v-4ed7fb36]{display:flex;justify-content:space-between;align-items:center}.header-actions[data-v-4ed7fb36]{display:flex;gap:10px}.config-content[data-v-4ed7fb36]{margin-bottom:30px}.config-preview[data-v-4ed7fb36]{margin-top:30px}.config-preview h3[data-v-4ed7fb36]{margin-bottom:15px;color:#303133}.el-table[data-v-4ed7fb36]{margin-bottom:10px}.el-form-item[data-v-4ed7fb36]{margin-bottom:20px}.proxy-addresses[data-v-4ed7fb36]{display:flex;flex-direction:column;gap:5px}.proxy-address-item[data-v-4ed7fb36]{display:flex;gap:5px;align-items:center}.proxy-address-item .el-input[data-v-4ed7fb36]{flex:1}

package/app/nginxManagement/frontend/dist/assets/index-B2VcD4B4.js

@@ -1 +0,0 @@
-import{_ as C,r as d,c as N,o as D,a as e,w as a,b as l,d as t,t as i}from"./index-D80vACWt.js";const R={class:"dashboard-container"},S={class:"card-header"},h={class:"card-header"},z={class:"stat-value"},E={class:"card-header"},I={class:"stat-value"},P={class:"card-header"},T={class:"stat-value"},U={slot:"header",class:"card-header"},j={class:"chart-container"},A={__name:"index",setup(F){const m=d(128),v=d(35.6),f=d(99.8),p=d("today"),g=d([{domain:"api.example.com",requests:12543,percentage:"45.2%"},{domain:"www.example.com",requests:8762,percentage:"31.4%"},{domain:"static.example.com",requests:6321,percentage:"22.8%"},{domain:"admin.example.com",requests:1532,percentage:"5.5%"}]);return(G,s)=>{const b=l("monitor"),c=l("el-icon"),o=l("el-card"),n=l("el-col"),x=l("connection"),w=l("refresh-left"),q=l("success"),u=l("el-row"),r=l("el-option"),y=l("el-select"),V=l("el-progress"),_=l("el-table-column"),k=l("el-table");return D(),N("div",R,[e(u,{gutter:20},{default:a(()=>[e(n,{span:6},{default:a(()=>[e(o,{class:"stat-card"},{default:a(()=>[t("div",S,[e(c,{class:"card-icon"},{default:a(()=>[e(b)]),_:1}),s[1]||(s[1]=t("span",null,"服务器状态",-1))]),s[2]||(s[2]=t("div",{class:"stat-value"},"运行中",-1)),s[3]||(s[3]=t("div",{class:"stat-desc"},"Nginx 1.23.3",-1))]),_:1,__:[2,3]})]),_:1}),e(n,{span:6},{default:a(()=>[e(o,{class:"stat-card"},{default:a(()=>[t("div",h,[e(c,{class:"card-icon"},{default:a(()=>[e(x)]),_:1}),s[4]||(s[4]=t("span",null,"活跃连接",-1))]),t("div",z,i(m.value),1),s[5]||(s[5]=t("div",{class:"stat-desc"},"较昨日 +12%",-1))]),_:1,__:[5]})]),_:1}),e(n,{span:6},{default:a(()=>[e(o,{class:"stat-card"},{default:a(()=>[t("div",E,[e(c,{class:"card-icon"},{default:a(()=>[e(w)]),_:1}),s[6]||(s[6]=t("span",null,"请求/秒",-1))]),t("div",I,i(v.value),1),s[7]||(s[7]=t("div",{class:"stat-desc"},"较昨日 +5%",-1))]),_:1,__:[7]})]),_:1}),e(n,{span:6},{default:a(()=>[e(o,{class:"stat-card"},{default:a(()=>[t("div",P,[e(c,{class:"card-icon"},{default:a(()=>[e(q)]),_:1}),s[8]||(s[8]=t("span",null,"成功率",-1))]),t("div",T,i(f.value)+"%",1),s[9]||(s[9]=t("div",{class:"stat-desc"},"较昨日 -1%",-1))]),_:1,__:[9]})]),_:1})]),_:1}),e(u,{gutter:20,style:{"margin-top":"20px"}},{default:a(()=>[e(n,{span:16},{default:a(()=>[e(o,null,{default:a(()=>[t("div",U,[s[10]||(s[10]=t("span",null,"请求趋势",-1)),e(y,{modelValue:p.value,"onUpdate:modelValue":s[0]||(s[0]=B=>p.value=B),size:"small",style:{"margin-left":"10px"}},{default:a(()=>[e(r,{label:"今日",value:"today"}),e(r,{label:"本周",value:"week"}),e(r,{label:"本月",value:"month"})]),_:1},8,["modelValue"])]),t("div",j,[e(V,{percentage:65,status:"success"}),s[11]||(s[11]=t("div",{class:"chart-placeholder"},"请求趋势图表将显示在这里",-1))])]),_:1})]),_:1}),e(n,{span:8},{default:a(()=>[e(o,null,{default:a(()=>[s[12]||(s[12]=t("div",{slot:"header",class:"card-header"},[t("span",null,"Top 访问域名")],-1)),e(k,{data:g.value},{default:a(()=>[e(_,{prop:"domain",label:"域名"}),e(_,{prop:"requests",label:"请求数"}),e(_,{prop:"percentage",label:"占比"})]),_:1},8,["data"])]),_:1,__:[12]})]),_:1})]),_:1})])}}},J=C(A,[["__scopeId","data-v-c33ec8b9"]]);export{J as default};

package/app/nginxManagement/frontend/dist/assets/index-BLD4e3hR.css

@@ -1 +0,0 @@
-.dashboard-container[data-v-c33ec8b9]{padding:10px}.stat-card[data-v-c33ec8b9]{height:100%;transition:all .3s ease}.stat-card[data-v-c33ec8b9]:hover{transform:translateY(-5px);box-shadow:0 10px 20px #0000001a}.card-header[data-v-c33ec8b9]{display:flex;align-items:center;margin-bottom:15px;color:#606266}.card-icon[data-v-c33ec8b9]{margin-right:8px;color:#409eff}.stat-value[data-v-c33ec8b9]{font-size:24px;font-weight:700;margin-bottom:5px}.stat-desc[data-v-c33ec8b9]{color:#909399;font-size:14px}.chart-container[data-v-c33ec8b9]{height:300px;display:flex;flex-direction:column;justify-content:center;align-items:center}.chart-placeholder[data-v-c33ec8b9]{margin-top:20px;color:#909399}

package/app/nginxManagement/frontend/dist/assets/index-BRTcbQAV.css

@@ -1 +0,0 @@
-.card-header[data-v-1ea91675]{display:flex;justify-content:space-between;align-items:center}.header-actions[data-v-1ea91675]{display:flex;gap:10px}.config-content[data-v-1ea91675]{margin-bottom:30px}.config-preview[data-v-1ea91675]{margin-top:30px}.config-preview h3[data-v-1ea91675]{margin-bottom:15px;color:#303133}.el-table[data-v-1ea91675]{margin-bottom:10px}.el-form-item[data-v-1ea91675]{margin-bottom:20px}.proxy-addresses[data-v-1ea91675]{display:flex;flex-direction:column;gap:5px}.proxy-address-item[data-v-1ea91675]{display:flex;gap:5px;align-items:center}.proxy-address-item .el-input[data-v-1ea91675]{flex:1}