Node Documentation: wings02
This document describes the hardware, operating system, Pterodactyl Wings configuration, and hosted services for the wings02 Wings node.
This document should be updated when the node hardware, operating system, status, location, resource allocation, network configuration, or hosted services significantly change.
Document Scope
This document covers:
- Physical hardware and storage.
- Operating system configuration.
- Pterodactyl node configuration and resource availability.
- Node networking, backup storage, external mounts, and hosted services.
It does not document individual game server configuration, startup arguments, or application-specific settings. Those are documented in the corresponding server documentation.
Node Identity
Pterodactyl Node Name:
wings02
Linux Hostname:
wings02
Internal FQDN:
wings02.pchs.gorgarath.net
Public Wings FQDN:
wings02.gorgarath.net
Legacy Public FQDN:
opti3060.gorgarath.net
Role:
Wings node
Current purpose:
- Runs a Pterodactyl Wings instance.
Status:
Active
Location:
us.pa.cresson.loc1
The location name follows the internal Pterodactyl infrastructure naming convention.
Physical Host
Hardware
CPU:
Intel Core i5-8500T
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
6 logical threads
Total:
6 physical cores
6 logical threads
Individual server allocations may use CPU pinning 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 without simultaneous multithreading (SMT), so each logical CPU corresponds directly to a physical core.
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 16 GB swap partition
The swap partition is configured as part of the Debian host installation and is managed by Debian.
Storage
Primary Storage Volume:
/dev/nvme0n1p2
Filesystem usage:
Root filesystem
Storage Configuration:
Single NVMe drive, no RAID
Raw Capacity:
Approximately 512 GB
Usable Capacity:
Approximately 452 GB
Drive Hardware:
SK hynix
Drive Model:
PC611 NVMe SK hynix 512GB
Purpose:
- Container storage.
- Game server data.
- Pterodactyl application data.
- System storage.
Pterodactyl Configuration
Wings Version:
1.13.3
Resource Allocation
The following resources are configured for the node:
CPU Limit:
No node-level limit
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:
| Service | Type | Purpose |
|---|---|---|
| Wings | Container Management | Pterodactyl Wings daemon |
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).
Public Wings API endpoint:
wings02.gorgarath.net
Wings TLS certificate:
/etc/letsencrypt/live/wings02.gorgarath.net/fullchain.pem
/etc/letsencrypt/live/wings02.gorgarath.net/privkey.pem
Certificate SANs:
wings02.gorgarath.net
opti3060.gorgarath.net
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 separated from container storage through a dedicated backup directory.
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.
External Mounts
The node allows container mounts from:
/mnt/backups/
No application-specific external mounts are currently configured.
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 Panel version changes if applicable.
- 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.
| Document | Purpose |
|---|---|
README.md |
Documentation index and repository conventions |
infrastructure.md |
Overall infrastructure layout, locations, networking, storage, and shared configuration |
wings00.md |
Hardware and configuration details for the wings00 Wings node and Pterodactyl panel host |
wings01.md |
Hardware and configuration details for the wings01 Wings node |
../servers/ |
Individual server deployment documentation |
Change History
2026-11-12
- Upgraded physical RAM from 16 GB (2x 8 GB DIMMs) to 32 GB (2x 16 GB DIMMs); updated total host memory.
2026-09-19
-
Standardized document structure and Markdown style to match repository conventions.
-
Updated documentation to reflect the rename from
opti3060towings02. Documented the current Linux hostname, internal and public FQDNs, TLS certificate paths, and legacyopti3060.gorgarath.netcertificate SAN. Updated related node references and updated the documented Wings version to 1.13.3.
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.