AMP 2.7.2.8 ‘Deimos’
This is a special update with a few features that are primarily to support Dune Awakening specifically. However it includes some fixes to how containers are tracked that seriously improves behaviour when performing tasks such as changing ports or reconfiguring instances.
This makes AMP the only platform that provides true turnkey setup for Dune Awakening. No Hyper-V virtual machine, no Windows, no Alpine, no Kubernetes - just a simple, convenient, self-contained system on normal Linux systems (or Windows via Docker). It’s been a lot of work, but it has been worth it!
New Features
Port Range Definitions - the port listings for applications now support ranges for games that require contiguous blocks of ports. For example you can have 7777 to 7787 in a single block for a game that requires 10 sequential ports without requiring separate definitions for each individual port.
Resource Usage Information - When creating an instance, template authors can now include an additional note to warn you if a server has particularly high resource requirements such as requiring unusually large amounts of RAM.
Docker / Podman Event Stream - AMP now subscribes to the event streams for the container platform in use, which solves a lot of problems with AMP thinking an instance is running when it’s not and vice-versa and the stalling that would happen when an instance was reconfigured or had it’s ports changed.
Fixes
Addresses ports not correctly showing up in the monitoring section within an instance (along with the primary endpoint) after either being changed in the instances Ports section or when an update to an instances base template configuration requires port reallocation.