This is not directly related to gaggio's suggestion, or even perl related; but it is realted to the "website maintenance upload problem" so I thought I would share.

I used to work for a company that had many web developers. The production environment was set up with one "master" server on the inside of the firewall. All the web developers would access it using SMB/SAMBA, mounting it as a drive to their PC. They could move files around with tools no more complicated than Windows Explorer. There was a scheduled job (also could be triggered on-demand) that would use SCP to push the files from the "master" out to the "live webservers" that served the content to the world. This also had the added benefit that if any of the live webservers were ever hacked they could be rebuilt easily by just refreshing them from the master.

This is not a good solution for every environment (particularly not good for small environments), but for some situations it works very well.