Thanks for the suggestion! 💚 After reviewing it, we won’t be moving forward right now, but we genuinely appreciate the input.
We aren’t able to support custom storage allocation for game servers created through the Web Interface because the deployment system relies on pre‑configured Docker templates. Each game server image is built with fixed volume mappings and predefined storage quotas. Changing these dynamically would require rebuilding the container images and adjusting the underlying host‑level storage orchestration, which the current architecture doesn’t support without risking instability or inconsistent resource allocation.
We may revisit this in the future, but for now the WI can only deploy servers using the standardized storage configuration defined in our installation scripts.
Log in to comment and vote
Comments1
Mar 9
PinnedThanks for the suggestion! 💚
After reviewing it, we won’t be moving forward right now, but we genuinely appreciate the input.
We aren’t able to support custom storage allocation for game servers created through the Web Interface because the deployment system relies on pre‑configured Docker templates. Each game server image is built with fixed volume mappings and predefined storage quotas. Changing these dynamically would require rebuilding the container images and adjusting the underlying host‑level storage orchestration, which the current architecture doesn’t support without risking instability or inconsistent resource allocation.
We may revisit this in the future, but for now the WI can only deploy servers using the standardized storage configuration defined in our installation scripts.