If you have to copy to a lot of other servers (let's say prod publish farm), you could create a workflow package and then subject it to a WF which replicates to various servers.
Please have a look at this community article:-
1) Use package manager
Pros: Very simple to create and do not require command like knowledge
Cons: Not suitable for Big packages. Slow some time
2) Use VLT (We are explaining how to use this in this article)
Pros: Faster than package manager. Do not consume package space like package manager.
Cons: Slow I/O
3) Use Tool based on VLT like Recap http://adamcin.net/net.adamcin.recap/
Pros: VLT rcp UI easy to see status and administer. Do not require command like knowledge.
Cons: Slow I/O because it uses VLT under the hood.
4) Use Tool based on other transfer protocol like Grabit https://github.com/TWCable/grabbit
Pros: Faster than VLT
Cons: Not Adobe supported. Need more dependency to set up.
I also agree with Ankur and Scott that "package is best way". If uploading is a problem, them you can certainly use Curl to automate it.
More reference articles:-
Thanks and Regards
The issue is to give all path names in package filter one by one while creating package in author to upload in another author environment. Let’s say you have 200 new pages to be transferred and all paths are not under one node in that case adding 200 filter paths manually while creating package is a lot of effort. So thinking of something like: http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manag...
Here I am also agreeing with creating package is the best way, but if we can automate that process can be a better solution?