Moving individual deployments

If you only need to place specific game server deployments on another drive, you do not need to move the entire Agent installation or the full `deployments` folder.

Each deployment lives as its own folder under `deployments`:

deployments/<server_id>/

You can relocate that folder to another drive and leave a directory link (Windows junction / Linux symbolic link) in its original place. The Agent continues to use the original path under `deployments`, while the data is stored on the target drive.

If you instead want to relocate the entire `deployments` directory, use the `deployments_dir` override described in Moving an Agent installation.

Before going forward, verify that this change is absolutely required as incorrect linking may result in a broken deployment path.

Requirements

• The game server belonging to the deployment must be stopped
• The Agent must be stopped before the folder is moved and the link is created
• The target location must be on a local drive available to the same machine
• The folder name at the target location should remain the deployment `server_id`

Windows uses a directory junction (`mklink /J`).
Linux uses a symbolic link (`ln -s`).

Hard links can not be used for directories. On Windows they also can not span different drives.

Moving a single deployment

Follow these steps for each deployment you want to relocate:

1. Stop the game server in Architect Manager

2. Stop the Agent

3. Open a Windows CMD (Run as administrator) / Linux Shell and identify the deployment folder under `deployments`

4. Move the entire deployment folder to the new target location

   # Windows example
   move "C:\ArchitectAgent\deployments\<server_id>" "D:\game-servers\<server_id>"
   
   # Linux example
   mv /opt/architect/deployments/<server_id> /mnt/data/game-servers/<server_id>
   

   After this step, the original path under `deployments` must no longer exist as a regular folder.

5. Create the link at the original deployment path:

   # Windows (directory junction)
   mklink /J "C:\ArchitectAgent\deployments\<server_id>" "D:\game-servers\<server_id>"
   
   # Linux (symbolic link)
   ln -s /mnt/data/game-servers/<server_id> /opt/architect/deployments/<server_id>
   

   Replace the example paths with your actual Agent installation path, `server_id` and target location.

   Note the argument order differs by operating system:

   • Windows: `mklink /J`
   • Linux: `ln -s`

6. Restart the Agent

7. Start the game server and verify that files, updates and runtime behavior work as expected

Notes

• Repeat the process per deployment if different servers should live on different drives
• Do not create the link before the original folder has been moved away
• Do not delete the target folder later while the link still exists; remove or recreate the link first
• On Windows, remove a junction with `rmdir` against the link path. This removes the link only, not the data at the target location
• On Linux, remove a symbolic link with `rm` against the link path. This removes the link only, not the data at the target location
• The same approach applies to deployments that reside under a user space `deployments` folder