Search Results

ZyveraWeb is an advanced web hosting plugin for Minecraft servers that embeds a complete HTTP/HTTPS web server directly into the server's JVM process. It allows server administrators to host websites, REST APIs, reverse proxies, and JavaScript applications alo...

Web Server HTTP/HTTPS — Full HTTP/1.1 support with optional TLS 1.3/1.2 encryption. Configurable binding — Bind to any host and port (default: 0.0.0.0:8080). Thread pool — Adaptive thread pool sized to available processors. Virtual Hosting Multi-domain rout...

ZyveraWeb uses a platform abstraction architecture with a single core and platform-specific adapters. The same feature set is available on all supported platforms. Platform Matrix Platform Minimum Version Status Spigot 1.16 Tested Paper 1.16 Tested ...

ZyveraWeb uses a layered architecture with a platform-independent core and platform-specific adapters, following the Adapter pattern. High-Level Diagram ┌──────────────────────────────────────────────────────────┐ │ ZyveraWebCore ...

Minimum Requirements Requirement Value Java JDK 21 or later Minecraft Server Spigot/Paper 1.16+, Folia, Velocity 3.3+, or BungeeCord 1.16+ RAM 50 MB additional overhead beyond the Minecraft server Disk Space ~10 MB for the plugin JAR + space for w...

Step 1: Download the Plugin Download the latest ZyveraWeb.jar from the official release channel. The file is a fat JAR (ShadowJar) containing all bundled dependencies. Step 2: Place the JAR Copy ZyveraWeb.jar into your server's plugins/ directory: server-root/...

What Happens on First Run When ZyveraWeb starts for the first time with an empty plugins/ZyveraWeb/ directory, it automatically populates the following files: Default Configuration config.yml is created with sensible defaults: host: "0.0.0.0" port: 8080 api: ...

The main configuration file is located at plugins/ZyveraWeb/config.yml. It uses the YAML format and is divided into several sections. Full Schema host: "<ip-address>" port: <port-number> api: cors-origins: - "<origin>" rate-limit: placeholder: re...

The web server is configured at the root level of config.yml. Settings host The IP address the web server binds to. Value Behavior "0.0.0.0" Bind on all available network interfaces (default) "127.0.0.1" Listen on localhost only (not accessible from o...

The sites: section defines virtual hosts, allowing you to serve different content based on the Host header of incoming requests. This works like Nginx server_name blocks. Site Types Each site must specify exactly one of the following types: Type Value Descr...

ZyveraWeb uses a token bucket algorithm to rate-limit requests per IP address. Each bucket is refilled to its maximum capacity after the time window elapses. Rate Limit Sections There are two independent rate limit configurations: Section Scope Default ...

ZyveraWeb supports HTTPS with TLS 1.3 and TLS 1.2. SSL is configured per-site rather than globally — each virtual host can have its own certificate. Config Settings SSL is configured under each site entry in sites: sites: - domain: "example.com" dir: "si...

The web server lifecycle can be managed both automatically (plugin startup/shutdown) and manually (in-game commands). Automatic Lifecycle Event Server Action Plugin enable Web server starts automatically after config validation Plugin disable Web serv...

The FileHandler serves static files from a configured root directory. This is the most common use case for hosting websites. Configuration A static site is defined in config.yml with the dir: key: sites: - domain: "example.com" dir: "site/main-site" The...

The reverse proxy handler forwards incoming HTTP requests to an upstream server. This is useful for integrating external web applications hosted on the same machine or network. Configuration sites: - domain: "api.example.com" proxy: "http://localhost:300...

The virtual host handler is the router that sits in front of all site-specific handlers. It matches incoming requests to the appropriate handler based on the Host header. Matching Logic Request → Extract Host header | Domain + Port (ho...

ZyveraWeb supports both plain HTTP and encrypted HTTPS. HTTPS is enabled per-site rather than with a global toggle. HTTP Server No encryption overhead Configured with a fixed thread pool Binds to the configured host:port when no site has SSL HTTPS Server En...

ZyveraWeb can run server-side JavaScript directly inside the JVM using GraalVM Polyglot (GraalJS). No external Node.js binary is required. How It Works The plugin creates a JavaScript runtime for each Node.js project. JavaScript files are evaluated within this...