test

[hcoop/zz_old/ikiwiki] / FileTransfer.mdwn

The recommended way (and possibly only reasonable way at the moment) to upload content from your computer to our servers (or the other way around if you want to make backups) is to use ''scp''. It is a secure and easy way to copy single files or whole directory trees.\r
\r
If all you want is to keep a directory at hcoop in sync with your local changes, you should consider using ''rsync''. It can significantly reduce bandwidth usage by only transmitting the differences between the two trees. Since version 2.6 ''rsync'' uses ''scp'' for file transfer by default. For older versions you have to use the ''-e'' (''--rsh'') option. For example:\r
\r
{{{\r
rsync -avz -e ssh ~/html/hcoop/* username@hcoop.net:public_html\r
}}}\r
You can also use plain ''scp'', but it overwrites destination files and is usually only applicable when you are uploading new files to hcoop:\r
\r
{{{\r
scp -r ~/html/hcoop/* username@hcoop.net:public_html\r
}}}\r
You can run command-line sftp (Secure FTP) tool:\r
\r
{{{\r
sftp hcoop.net\r
Connecting to hcoop.net...\r
Password:\r
sftp> help\r
}}}\r
With GUI FTP clients, SFTP connection is possible if the clients support "Secure FTP" or similar as the connection method. In Unix/Gnome, you could use for example ''gftp''; for Microsoft Windows, example clients are the free [http://WinSCP.sourceforge.net WinSCP], or proprietary FTP Voyager.\r
\r
We also started supporting the usual FTP protocol, but you need to request the ability to use it (see [https://members.hcoop.net Member Portal]), and we only allow "SSL Auth" method (see FtpConfiguration). Here's an example:\r
\r
{{{\r
ftp hcoop.net\r
Connected to hcoop.net.\r
220 fyodor.hcoop.net FTP server ready.\r
Name (hcoop.net:user):\r
234 AUTH SSL OK.\r
[SSL Cipher AES256-SHA]\r
331 Password required for user.\r
Password:\r
User logged in.\r
Remote system type is UNIX.\r
Using binary mode to transfer files.\r
ftp> help\r
}}}\r