Copy BASIC source code from production server to development server

Are the servers linux or windows servers?

Using EclipseIDE we copy from our development machine to our production machine using and XML install script. Since we use UniObjects for Java, there is a dataset read and dataset write command that speeds up that copying by 30 to 50% as compared to COPY command. Our production machine is in California and our development machine is in Colorado so this technique works any where you have UniObjects access.

If you have the UVNET package enabled on both servers then you can set up pointers and copy at the UV level.  If not, then you can use ‘Linux’ if you are using Linux/Unix.  If you are on Windows, you should be able to shares and copy from a command prompt.

Depends what kind of workflow you want.

Guys already shared inside Uni ecosystem solution. You have ability to use external things, as it is no different than generic javascript or python dev workflow.

For source code if you have ssh access to production machine, you can transfer files and entire BP folders using rsync (you have scp as well, but rsync is more powerfull as it supports delta copy, compression - it transfers only changes, once first copy done). 

On linux (or heavy modified Windows) if you have ssh you can mount any remote folder using sshfs: https://github.com/libfuse/sshfs

In general if I had to have new user modern deployment, I would use git repo. And never edit from prod to dev direction.  You have options to sync from dev to production either manually or using devops pipeline.

If you are maintaining PCI compliance, like we are, our development server is out-of-scope so a direct connection violates PCI.  So we have to TAR up the development source code and ftp it to the production sever.  There we can extract it from the TAR bundle and copy it into the appropriate program file. (We run on AIX).

Of course, we have built programs to handle this with a few clicks.

That is true a direct connection violates the PCI compliance. However, the way it can be done is with a machine in between the production machine and the development machine which we call the QA machine. All updates to the production machine are handled by a different person with approved pull requests with a clear log showing who wrote the code and who approved the deployment to the production server via the QA machine. Using UniObjects for Java with EclipseIDE and version control this process is much easier that using tar/ftp where you would have to create the appropriate manual logs for that whole process which sounds very messy.