Browser editor or SFTP? Choose a safer file workflow

A game-server file manager handles several different jobs: reading configuration, moving archives, downloading logs and migrating whole directories. Those jobs do not all belong in a text editor.

The integrated website panel gives you a convenient starting point, but file size, format and application behaviour still determine the safest workflow.

Keep editing focused on text

Properties, YAML and JSON files are good browser-editor candidates when they fit within the supported size. The website's text-editor default is currently 20 MiB. That is an editor boundary, not a promise that every file below it is pleasant to work with on every device.

A large log is often easier to download and search locally. A JAR, ZIP, image or world-data file is not text and should not be forced through an editor by changing its filename.

Understand the upload path

Uploads have separate limits. The node, upstream proxy, disk quota and connection can each constrain the operation. A request-too-large message and a disk-full message point to different problems; repeatedly retrying without reading the error wastes time.

After a timeout, refresh the directory and check the destination before sending another copy. For a large migration, SFTP may be more practical where that access is available on the service.

Plan the save, not just the edit

Stop an application before editing files that it rewrites on shutdown. Preserve a copy of the original, change one setting and validate its syntax. After a save, use the required restart or reload procedure and read the console before declaring the job complete.

A conflict warning deserves attention. Another administrator or the application itself may have changed the file since you opened it. Reload the current version and reconcile your change instead of replacing someone else's work.

Keep team access deliberate

Give collaborators their own subuser permissions rather than your main account credentials. Someone who only needs to inspect logs may not need permission to delete files or reinstall the server. Review those permissions after a project ends.

Ask for help with a reproducible failure

Include the service ID, approximate file size, operation attempted and exact error. Do not include tokens, passwords or private world downloads in a public channel.

Read large-file handling, SFTP access and subuser permissions for the relevant steps.