Once we're on Git I'll just install a LAMP server on my computer and use pushes and pulls to get the files on the remote server. We're in the process of moving things to Git but until then we have to use FTP. I was kind of expecting that type of answer. It is a security nightmare except on a private network with no other users. The fact that they allow anyone to use plain FTP is a real concern.īut regardless, please don't use plain FTP anymore. If the webhost only supports plain FTP, it is time to fire them. Scripting is much more efficient, IMHO, and frees you from some GUI that will change in ways you have no control over.
Lots of editors support using rsync, sftp and git, but I'd suggest you just create a little script that does what you want, since a professional website would automatically generate any graphical assets in an optimized way and compress and dynamic code to make page access and loading more efficient.īTW, pretty much any file manager in Linux supports the sftp:// URL, if you want to treat it just like plain FTP, but will honor ~/.ssh/config settings and keys. Using password-based authentication is considered a security failure and has been for the last 15+ yrs.
The other options are based on ssh and use ssh-keys for authentication. The last option, git, has been taking over most web dev processes the last few years. I don't know which is best for you, but some ideas: If you are dead set on using FTP, stop reading.įor transferring files, there are multiple other solutions these days that don't send passwords unencrypted. It should have been removed in 1995 when telnet and rlogin were effectively killed off.
0 kommentar(er)
