Remote Files & Deployment
How to safely browse, edit, import, download, and deploy mission files through DZconfig remote file tools.
Overview
Remote file tools let you browse, download, edit, import, and deploy files through an FTP or SFTP connection tied to an instance.
Use remote editing for targeted changes and generated exports for larger config releases. Keep a backup of working server files before replacing mission configs.
Quick Facts
| Protocols | FTP and SFTP |
|---|---|
| Editable types | XML, JSON, CFG, TXT, LOG, ADM, and INI within configured size limits |
| Best for | Pulling live configs, reviewing logs, editing small files, and deploying generated output |
Recommended Workflow
Import first
Pull the current remote file into DZconfig before making major edits.
Generate locally
Use DZconfig generators for structured files so values come from validated models.
Review diff mentally
Check filenames, folders, and map-specific paths before upload.
Restart intentionally
Most mission config changes are loaded only on restart. Schedule deployment accordingly.
Safety Notes
Avoid editing binary files or very large logs through the text editor. Use download/import flows for those instead.
When editing serverDZ.cfg remotely, keep passwords and admin tokens private. Do not paste secrets into shared support tickets or public examples.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| File changed but server did not | Server needs restart, or the wrong mission folder was edited. |
| Upload succeeds but config breaks | Malformed XML/JSON or wrong filename casing. |
| Cannot browse deep folder | Remote browsing depth limit or restricted server account permissions. |
| Generated file missing data | The instance model data has not been imported or created yet. |