It does seems that whenever I suggest that Atom can cooperate with other tools through the command line my post is “flagged by the community”.
This post is edited since my first reply (“peep”) above was flagged as “off-topic”. So I will address the “topic” and then suggest why I would not follow this advice.
The remote-ftp package is here (but there are others if OP searches further).
OP does not specify the exact package name. However, continuing with remote-ftp.
Enable browsing remote FTP/FTPS/SFTP just like the built-in Tree View. Requires a project.
The OP refers to FTP and not SFTP. FTP protocol is not secure and it is recommended that SFTP protocol be adopted. If the host server does not support SFTP consider changing.
The configuration file is .ftpconfig placed in the Atom project folder.
The parameters for FTP should be evident. See package documentation.
… … …
If OP searches further there is this Atom package remote-ssh.
Putty specific options in .ftpconfig
The session option was added in case you have saved sessions inside your Putty and you want to re-use those.
This allows OP to use PuTTY tool to make a test connection, and then transfer the session configuration into Atom remote-ssh ftpconfig file.
If Atom process-palette package is installed OP can “drive” PuTTY directly through command line.
If OP prefers to emulate the client-server functions offered by Dreamweaver the Atom top menu bar can be customised to execute a number of process-palette commands. For example I have “Toggle Custom Commands” in my top bar. I can also launch Ansible playbooks to manage localhost < – > remote host.
FTP is insecure.
SFTP setup requires a project configuration file.
Mix and match operations using other tools such as PuTTY.