A couple of weeks ago, I promised to create a step-by-step guide to setting up Vault on a WebHost4Life (WH4L). I've been stalling on this basically because for me to do an accurate, detailed step-by-step guide, it will involve setting it up again, so that I can record each and every step. Short of doing that, here's the general gist of what I did to get it setup.
Step 1
Run the install locally on my machine, using a local SQL instance. Test it, create your users etc.
Step 2
Create a new database called “sgvault“ on your WH4L account, your username should be “sgvaultuser“ NOTE: If someone has previously created this database on your shared SQL Server, you may be out of luck. Not sure this will work with a different DB Name. To do this, login to your WH4L control panel, and click on the “MS SQL“ link.
Step 3
Backup the “sgvalut” database on your local machine, you will need to restore this database on your WH4L SQL Server. First you'll have to FTP the “sgvault” backup to your WebHost4Life account, follow the instructions on the MS SQL page on your WH4L account for doing a DB restore.
Step 4
Create a directory on your WH4L account called VaultService, FTP the contents of your local “VaultSevice“ directory created in step 1. Should located on c:\\inetpub\wwwroot\VaultService or something like that.
Step 5
Give the ASPNET Account WR permissions to the VaultService directory on your WH4L account (Do this under the “File Permission“ link. You may be able to tighten security more, but this'll get you started.
Step 6
Create an IIS Application for the VaultService directory. Click the “Set IIS Application“ link and follow the on screen directions.
Step 7
Edit the web.config file in the VaultService directory, making two changes:
<add key="ConfigPath" value="c:\hosting\webhost4life\member\[WH4L ACCT NAME]\VaultService\Vault.config" />
<add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='false'; Server=[YOUR DB IP]; Database=sgvault; User ID=sgvaultuser; password=[YOUR PASSWORD]" />
Note that you're using a clear text password here. Vault uses a Machine hashed password if you're using the “pwd“ attribute for the line above. Short of having someone at WH4L running a program to gen this, I had to go with clear text.
That's about it. Launch your vault client and start controlling some source code! It's been working great for me!
-Brendan