v1.0.0 Release Candidate 4

Fixed

• Fixes server files being inaccessible if the root data path is a symlink to another location on the machine.
• Fixes some console output being written to the logs accidentally truncating other lines due to special ANSI sequences being output.
• Fixes server.properties files getting mangled by the automatic configuration editor when booting a server.
• Fixes a missed stream close when stopping resource polling that would lead to memory leaks.
• Fixes port bindings being incorrectly re-assigned when using 127.0.0.1 with Docker. These are now properly re-mapped to the pterodactyl0 interface so that networking operates as expected for the server.
• Fixes handling of values within arrays in yaml and json configuration files.
• Fixes a 304 error being returned rather than a 400 error when a file upload is invalid.
• Fixes deadlocks and response delays when processing server console and stat events. This was causing server consoles to become completely unresponsive after random periods of time and was only resolvable via a Wings restart.

Changed

• Allows a stale value to be present when starting a server if the server is allowed an unlimited amount of disk space.
• Removed all remaining traces of the zap logging library from the codebase.
• Servers no longer auto-restart as if they crashed when a stop command is manually sent via the server console to the instance.
• Changes the CORS checks to allow * as a remote origin.

Added

• Added an auto-generated logrotate file which is written to the normal logrotate directory when wings is first started.
• Added additional debug logging within the internals of the resource polling for servers to better trace unexpected behavior.
• Adds additional logic check to avoid even trying to stop a suspended server if it is already stopped.

SHA256 Checksum

cbf4f3d9aa08f9d9ed4d3aa4db3168ef714d7f2054f73f2e5601212d321eca4b  wings_linux_amd64