Install Vi from a main server to local servers

[darkxceed]

Hello,

My situation is this, I have a main server and local servers.

The software on the local server have to be updated when new updates are made for the local servers.

What is the best way to do this.

The software which has to be updated are made with NI software.

I have attached picture visually.

gr,

Bart

[mikeporter]

A source control system like SVN might be able to do it. An advantage of that approach would be that you wouldn't need all the "local  servers". Each user would grab a working copy of the shared code directly from the "Main Server".

Alternately, I would think that there are at least a couple hundred people selling "synchronization" software/services that could handle the file copying for you.

Mike...

[darkxceed]

Thank you for your fast responce.

In my situation I don't want to be dependent of the net work.

Best situation would be some sort of sychronise software which keeps the software up to date on all pc's.

Problem maybe is that the software will get big in size and amount, but the changes will be minor.

It's not very clear to me how this works, can I synchronise a folder to the test pc's?

[mikeporter]

The beauty of using a SCC package like SVN to handle this is that when you check out a working copy the files are copied to the user's computer so the network isn't needed unless they either want to commit changes that they to the controlled files, or they want to update their working copy to obtain changes that other developers made.

Mike...

[crossrulz]

As has been said, a source control software like SVN is definately the way to go.

What I've done for a set of test systems that were all being integrated with at the same time was have then networked together amonst themselves (didn't see the company network or the internet).  I then added an additional computer to act as the "server".  Set up Tortoise SVN on all of the machines and put the repository on the "server" computer.  So everybody did a check out and each of them now has a latest working copy.  As updates were made, the changes were committed to the repository on the "server" and then also performed an update after the commit.  This way we ensure all of the systems had the exact same code.  Before implementing this, I would spend half of my Fridays just comparing file modified dates trying to figure out which files were the latest and what not.  And I always messed up somebody's code when I did my manual synchronization.  TSVN gave me my Fridays back and kept everybody in synch better than I could manually.  You just have to make sure people are good at committing their code at night and then doing the update in the morning.

[Dave_Brandt]

You can also create a launch Vi that is run first on your local servers. This can check the server revision and see if it is newer than the local version. If it is you can archive your older revision on your local server and then copy the new revision to the local server. Then start the new revision. Remember your vi or .exe can not be running when you copy the new revision to the local. Then use vi server to start the new revision.  To determin a vi revision see https://decibel.ni.com/content/docs/DOC-11111