Vault Upgrade

[behold]

We are preparing to upgrade Vault from 3.1.2 to 4.1.3. Are there any installation concerns we should be aware of? We also have several custom applications using the Vault API. IF there have been any changes, I will need some documentation so that these apps can be modified.

[Beth]

Upgrade first to Vault 3.1.9, then install Vault 4.1.3. Make sure you have a backup of your database before upgrading.

You will want to look at the examples in the section of the forum called Development. All of the material there uses the latest API.

[behold]

Currently we have the vault service running on a file server and the database installed on a separate server. There is talk about installing the upgrade on a web server. Do you have any recommendations or concerns with installing the Vault services on a web server?

[Beth]

Vault can go on a web server with no problem. If you have any problems with setup, just send me a note through support at sourcegear.com.

On the API again, I had some additional input.
The old API is still there, and it should be mostly the same ( some methods may have added parameters ).
The new API is going to be supported long term and will not change as much. It's also cleaner to program against. It's optional though.

[behold]

A question from our web team.

Should the web site be behind or outside the firewall? The answer effects where we may configure the web service.

[Beth]

If you have any other websites, I would suggest setting it up the same as those. The most secure would be behind the firewall. If you are very skilled with Active Directory, I would expect that one could use a DMZ also, but that really takes knowing what one is doing.