Node Documentation: wings1

This document describes the hardware, operating system, Pterodactyl Wings configuration, and hosted services for the wings1 Wings node.

This document should be updated when the node hardware, operating system, status, location, resource allocation, network configuration, or hosted services significantly change.

Node Identity

Node Name:

wings1

Role:

Wings node

Current purpose:

• Runs a Pterodactyl Wings instance.
• Hosts a Minecraft server.

Status:

Active

Location:

us.pa.portage.loc1

The location name follows the internal Pterodactyl infrastructure naming convention.

Physical Host

Hardware

CPU:

Intel Core i7-8700T

CPU Architecture:

x86_64

RAM:

32 GB

Memory Configuration:

2x 16 GB DIMMs

Manufacturer:

Dell

Model:

OptiPlex 3060 Micro

Firmware and Management Controllers

BIOS Version:

1.32.0

Management Controller:

Intel Management Engine (ME) - Disabled in firmware

Management Controller Firmware:

Not available while ME is disabled

Storage Controller:

Intel chipset integrated NVMe/SATA controller

Controller Cache:

No dedicated controller cache

Storage Controller Firmware:

Managed through system firmware/NVMe device firmware

CPU Topology

The server contains:

1 CPU socket

Each CPU:

6 physical cores
12 logical threads

Total:

6 physical cores
12 logical threads

CPU pinning may be configured on individual server allocations when latency-sensitive workloads require predictable CPU placement.

CPU pinning is configured on a per-server basis through Pterodactyl.

The CPU provides six physical cores with simultaneous multithreading (SMT), so each physical core exposes two logical CPUs.

Memory

Total host memory:

32 GB

Memory is shared between:

• Pterodactyl services.
• Wings-managed containers.
• Operating system usage.
• File caching.
• Other system services.

Operating System

Operating System:

Debian 13

Swap Configuration:

Approximately 24 GB swap partition

The swap partition is configured as part of the Debian host installation and is managed by Debian.

Primary Storage

Storage Volume:

/dev/nvme0n1p2

Filesystem usage:

Root filesystem

Configuration:

Single NVMe drive, no RAID

Raw Capacity:

Approximately 512 GB

Usable Capacity:

Approximately 452 GB

Drive Manufacturer:

SK hynix

Drive Model:

PC611 NVMe SK hynix 512GB

Purpose:

• Container storage.
• Game server data.
• Pterodactyl application data.
• System storage.

Secondary Storage

Storage Volume:

/dev/sda1

Filesystem usage:

Dedicated backup storage

Mount Point:

/mnt/backups/

Configuration:

Single SATA drive

Raw Capacity:

Approximately 500 GB

Usable Capacity:

Approximately 458 GB

Drive Manufacturer:

HGST

Drive Model:

HTS725050A7E630

Purpose:

• Pterodactyl backup storage.
• External mounts.

Pterodactyl Configuration

Wings Version:

1.13.1

Resource Allocation

Resource management for this node is handled through Pterodactyl server allocations.

CPU Limit:

Unlimited

CPU Pinning:

Managed per server allocation.

Memory:

Shared host resource

Disk:

Shared host storage. Individual limits are managed through Pterodactyl server allocations.

Hosted Services

Current services:

• Pterodactyl Wings.
• mcforge.gorgarath.net Minecraft server.

Network Configuration

Public services hosted on this node are exposed through externally managed hostnames.

Current network features:

• DNS records.
• SRV records (where applicable).
• DDNS hostname updates (where applicable).

Reverse proxy:

No reverse proxy

Service-Specific Network Requirements

No additional service-specific network requirements are currently configured.

Additional service ports should be documented in the corresponding server environment documentation if deployed.

Backup Storage

Backup storage is located separately from container storage.

The backup storage directory resides on a dedicated secondary SATA drive mounted at /mnt/backups/.

Pterodactyl backup storage path:

/mnt/backups/wings/

Purpose:

• Stores Pterodactyl-generated server backups.
• Keeps backup data separate from container storage.
• Allows backup storage to be managed independently from server allocations.

Backup configuration such as retention limits, schedules, and enabled backups is managed at the individual server level and is documented in the corresponding server environment documentation.

Application Backup Mounts

Application-specific backup storage is mounted separately from Pterodactyl backup storage.

Application backup mount:

Host:

/mnt/backups/minecraft-world-backups/<server-name>

Container:

/home/container/simplebackups/

Purpose:

• Keeps application-specific backups outside the container filesystem.
• Prevents Pterodactyl backups from recursively including generated backup archives.
• Allows multiple applications to share a structured backup storage location.

External Mounts

The node allows container mounts from the following host path:

/mnt/backups/

Currently used for:

• Application-specific backup storage.
• Separation of application backups from Pterodactyl backup storage.
• Other external storage requirements as needed.

Migration Considerations

Servers may be migrated between Wings nodes.

Before migrating servers from this node, verify:

• Required storage exists on the destination node.
• External mounts are available.
• Backup paths are accessible.
• CPU and memory allocations are supported.
• Network requirements are available.

Maintenance Notes

When making changes to this node:

• Update this documentation after significant changes.
• Record operating system changes.
• Record hardware changes.
• Record firmware changes.
• Record Pterodactyl infrastructure changes.
• Record Wings version changes.
• Verify backups before migrations or upgrades.
• Review server documentation for consistency after infrastructure changes.

Related Documentation

The following documents provide additional information about this node and the services hosted on it.

Change History

2026-08-03

Updated node documentation structure and clarified hardware, operating system, storage, and resource allocation details.

Documented CPU topology, swap configuration, storage layout, Pterodactyl/Wings versions, external mounts, and current hosted services. Improved consistency with the centralized infrastructure documentation structure.

2026-07-26

Initial documentation created for the node.