> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/game-hosting/processes/index/rolling-deployment.md). # Rolling Deployment Updating your game servers with a rolling update means that you update game servers as soon as they exit naturally or when they are empty and unallocated. This of course only works for game types that have matches that end. Some games do not have the concept of finite matches but instead run forever. That type of game might not be suited for this kind of update method. No maintenance window is required. What is required is that your back end can handle multiple game server versions alongside each other. Additionally your clients should be able to connect to either version. As you can tell, you should only perform rolling updates if the new version is compatible with the old one. After a while most game servers will be updated. Any remainders can be [Forcibly Updated](/game-hosting/processes/index/forced-deployment.md). {% hint style="info" %} This deployment method has not yet been implemented. {% endhint %} ## Benefits * No maintenance window is required * No extra server resources are required. The total amount of game servers will remain equal during a rolling update * Completely transparent to your clients ## Downsides * No way to test your newly deployed game server versions. As such, testing must be done beforehand! ## Performing a Rolling Deployment via the UI {% hint style="info" %} This deployment method is not yet available. This documentation will be updated as soon as it is available. {% endhint %} ## Performing a Rolling Deployment via the API {% hint style="info" %} This deployment method is not yet available. This documentation will be updated as soon as it is available. {% endhint %} ## Performing a Rolling Deployment manually You can perform all of the above manually if you wish, bypassing our automated systems. For more details on how to do this, please see the [Rolling Deployment - Manually](/game-hosting/processes/index/rolling-deployment-manually.md) chapter. Note that you will not receive any live-reporting emails then. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.i3d.net/game-hosting/processes/index/rolling-deployment.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.