Textode is evolving through alpha builds. Check current compatibility and keep independent backups of important files.
Use SFTP rather than unencrypted FTP when possible
SFTP runs over SSH and protects the connection in transit. Before entering credentials, confirm the server address and compare its SSH host-key fingerprint with a trusted value from your hosting provider. A fingerprint change is a reason to investigate, not something to accept automatically.
- Prepare hostname, port and username.
- Use a limited-privilege account when possible.
- Confirm the SSH host fingerprint through a separate trusted channel.
Connect to the right directory
A root account may start at the filesystem root (/), while a restricted hosting user may start in its home or a chroot directory. Do not guess a filesystem path if the server provides a starting directory. Expand folders in the remote explorer to find the application or public site root.
Safely edit and save a remote file
Open a small noncritical file first. Read it, change one harmless line, save, and reopen it to confirm that the upload has succeeded. Keep a server-side backup, particularly when editing application configuration or deployed PHP files.
Remote files can change while your editor is open. If the server copy changed externally, review those changes rather than overwriting it without warning. Also account for interrupted connections, permissions and differences in file encodings.
- Create a backup or use version control first.
- Test read, write and reopen on a disposable file.
- Confirm remote permissions and be ready to roll back.
SFTP in Textode
Recent Textode alpha builds provide a Connect action and a remote folder tree inside the familiar Explorer panel. Selecting a file opens it for editing and Ctrl+S is intended to save it back to the same remote path.
This functionality is still undergoing interoperability and security testing. Treat live production changes cautiously and verify the result on the server.