Hi,
Is there a way to duplicate the installation of Vault, for example, in order to maintain a QA environment and a production environment?
I'm curious because I'd like to keep one copy operational while keeping the other available for upgrade testing.
In the configuration options, there's a place to specify the sgvault connection string, but there's no way to specify the sgmaster connection.
Is there a way for this to be done?
Thanks.
Maintaining Two Copies of Vault Databases
Moderator: SourceGear
Vault doesn't support synchronization.
If you wanted to maintain a second server where users will have read-only access, then you can take a Vault backup and restore it to another server and just keep the developers only accessing one Vault database, and QA accessing the other, and each have their only set of licenses for their server. QA's server though would need a fresh restore and resetting up the users each time they need new data.
What some do is create a branch in the same repository for the QA people and give them access to only that folder. Then any changes can be merged over.
If you wanted to maintain a second server where users will have read-only access, then you can take a Vault backup and restore it to another server and just keep the developers only accessing one Vault database, and QA accessing the other, and each have their only set of licenses for their server. QA's server though would need a fresh restore and resetting up the users each time they need new data.
What some do is create a branch in the same repository for the QA people and give them access to only that folder. Then any changes can be merged over.
2 copies on same server?
Alright, so is there no way of keeping both installations on the same server other than branching the projects?
What if a project needs to be branched for another reason, could this interfere with the QA/Prod setup?
Thanks.
What if a project needs to be branched for another reason, could this interfere with the QA/Prod setup?
Thanks.
I wasn't talking about two installations. I'm talking one installation where you'd have a tree structure like so:
-Project Trunk - where development happens
-Branch release candidate 1.0 - can either finish development here or send to QA
-Any other branch from Trunk
Developers would have access to all, but QA would only have access to branches. This kind of security is set at the folder level in Vault.
I was looking back to your original question and it sounds like we might be talking about 2 different things, because I was thinking QA of your software instead of a QA on Vault itself. If you are wanting another copy only for upgrade testing of Vault, then yes, you can make a copy of the database and then install Vault on top of it on another server and test the upgrade from there. You just don't want to be putting changes into the database there, because they can't then be moved over to your live Vault database.
-Project Trunk - where development happens
-Branch release candidate 1.0 - can either finish development here or send to QA
-Any other branch from Trunk
Developers would have access to all, but QA would only have access to branches. This kind of security is set at the folder level in Vault.
I was looking back to your original question and it sounds like we might be talking about 2 different things, because I was thinking QA of your software instead of a QA on Vault itself. If you are wanting another copy only for upgrade testing of Vault, then yes, you can make a copy of the database and then install Vault on top of it on another server and test the upgrade from there. You just don't want to be putting changes into the database there, because they can't then be moved over to your live Vault database.