Server Environment: <server-name>

This document describes the hosting environment for <server-name>, including the Pterodactyl configuration, resource allocations, container image, storage mounts, and network configuration.

This document reflects the current deployment environment for <server-name> and serves as the reference for its Pterodactyl configuration.

Server startup arguments, runtime configuration, and application-specific settings should be documented separately where appropriate.

Node hardware details and Pterodactyl infrastructure information are documented separately in ../../infrastructure.md and the corresponding node documentation.

Document Scope

This document describes:

• The Pterodactyl deployment configuration.
• Resource allocations.
• Container image selection.
• Pterodactyl egg configuration.
• Storage mounts.
• Network configuration.
• Pterodactyl backup settings and storage configuration.

It does not document:

• Runtime startup arguments.
• Host hardware details.
• Pterodactyl Panel or Wings versions.
• Node hardware configuration.
• Application runtime configuration.
• Gameplay configuration or content configuration.
• Mod/plugin/modpack configuration.

Those topics should be documented separately where appropriate.

Server Overview

Operational procedures, startup configuration, backup procedures, and application-specific guidance should be documented separately in related documentation.

Pterodactyl Deployment

This server is deployed using a self-hosted Pterodactyl installation running on the <node-name> Wings node.

Current deployment:

Platform:
Pterodactyl

Wings Node:
`<Node name>`

This server can be migrated between Wings nodes when required. If migration occurs, this document should be updated with the new node assignment.

Node-specific hardware information is documented separately in the corresponding node documentation.

Egg Configuration

The server uses the following Pterodactyl egg:

Document any egg-specific changes or customizations here.

Startup commands and runtime configuration should be documented separately.

Container Image

Configured container image:

<Container image>

This image provides the container environment and runtime used by the server.

Runtime versions and startup configuration should be documented separately.

When changing runtime versions, the container image and startup configuration should be reviewed together.

Resource Allocation

Configured Pterodactyl resource limits:

CPU Allocation

CPU Limit

The CPU limit is configured as:

<Value>

Document whether CPU quota limits, CPU pinning, or another method controls CPU availability.

CPU Pinning

The server is pinned to the following logical CPU threads:

<CPU affinity>

Document the CPU topology relationship if CPU pinning is used.

Example:

CPU topology is specific to the current host hardware. If the server is migrated to another node, CPU pinning should be reviewed.

Memory Allocation

The configured memory allocation is:

<Memory allocation>

Document how allocated memory is expected to be used.

Consider documenting:

• Application runtime allocation.
• Runtime overhead.
• Native libraries.
• Mod/plugin overhead.
• Operating system and filesystem cache requirements.

The Pterodactyl memory allocation should remain higher than any configured application runtime limit.

Swap Allocation

Swap configuration:

<Swap allocation>

Document any reasoning behind the swap configuration.

OOM Killer

Pterodactyl OOM Killer setting:

<Enabled/Disabled>

Document any considerations related to memory exhaustion handling.

Storage Configuration

Container Storage

The server operates within the standard Pterodactyl container filesystem:

/home/container/

Files referenced by startup commands are relative to this working directory unless otherwise specified.

Mounted Storage

The server uses the following external mounts:

Purpose:

Simple Voice Chat:
Protocol:
UDP

<Number>

<Schedule or manual>

<Path>

<Configuration>