Point of clarification - Git location

I am currently using VSCode using the Remote SSH tools and modifying code on the server. The repository on the Linux server is actually configured as a git instance.

It's my understanding, using the MVVS extension, the git repository is on the user's PC or shared drive (OneDrive) but the files on the Linux server are not actually a git repository. The net result of this is that the version of a program on the server is always the latest saved version, regardless of branch.

It appears that this SFTP extension works well for keeping items in the local repository uploaded to the server. Any other suggestions?

This could actually simplify life to some extent. The cautionary tale is that if someone modifies an item on the server side, it must be manually pulled back to the user's repository. Or, is there an "automagic" means of doing that? Also, any items ID's may need to be converted to URL's if they include characters such as '*', '\\', etc.

Thanks, in advance!

I am currently using VSCode using the Remote SSH tools and modifying code on the server. The repository on the Linux server is actually configured as a git instance.

It's my understanding, using the MVVS extension, the git repository is on the user's PC or shared drive (OneDrive) but the files on the Linux server are not actually a git repository. The net result of this is that the version of a program on the server is always the latest saved version, regardless of branch.

It appears that this SFTP extension works well for keeping items in the local repository uploaded to the server. Any other suggestions?

This could actually simplify life to some extent. The cautionary tale is that if someone modifies an item on the server side, it must be manually pulled back to the user's repository. Or, is there an "automagic" means of doing that? Also, any items ID's may need to be converted to URL's if they include characters such as '*', '\\', etc.

Thanks, in advance!

I am currently using VSCode using the Remote SSH tools and modifying code on the server. The repository on the Linux server is actually configured as a git instance.

It's my understanding, using the MVVS extension, the git repository is on the user's PC or shared drive (OneDrive) but the files on the Linux server are not actually a git repository. The net result of this is that the version of a program on the server is always the latest saved version, regardless of branch.

It appears that this SFTP extension works well for keeping items in the local repository uploaded to the server. Any other suggestions?

This could actually simplify life to some extent. The cautionary tale is that if someone modifies an item on the server side, it must be manually pulled back to the user's repository. Or, is there an "automagic" means of doing that? Also, any items ID's may need to be converted to URL's if they include characters such as '*', '\\', etc.

Thanks, in advance!

Forgot to say that besides compiling code to be copied to the U2 server, you pull and push from the GitHub repository, to syncronize with the other developers. MVVS has a GitHub extension that simpifies this.

  Regards,
  Enrique

I use the SFTP extension with Linux and Windows (with OpenSSH installed) and it works great.

There are two settings that reduce friction, UploadOnSave uploads to the server every time you save locally.  DownloadOnOpen can do the same in reverse, but it's a little more dangerous - I instead manually right click on the program and choose "Download File" when starting to work with a new program, and if there are any unexpected changes then review in the source control view.

I guess theoretically two programmers could be working on the same program and overwrite each other, but in the environments I work in that's really unlikely.

This approach means I have three copies of the code - one local repo on my desktop, the in-process code being run on the server in dev, and the main "blessed" repo with a production branch I check in to when deploying.  Because of git and the SFTP extension it's easy to keep all three in the expected state and avoid confusion, while having a good safety net to make changes without fear.

Thanks for the response. We have been trying to manage the Git functions on the Linux server and, in the long run, it appears that managing via Windows and SFTP will actually be a bit easier. It's certainly easier to get the current version of Git on the PC rather than the Linux server. Still a lot of "old habits" to unlearn...