This page assumes you have already downloaded the Vesta files from Sourceforge as described on the "Getting Vesta" page of this site.
vsrun must be installed first. Open a command shell and change to the directory where you downloaded the Vesta files. These instruction assume that CPU architecture is amd64, .deb packages are being installed, and the user has sudo privileges.
sudo dpkg -i vsrun-1.6-1_amd64.deb
Next, install vesta-common. From the same command shell, execute the command:
sudo dpkg -i vesta-common_2.1.12-pre13-13-1_amd64.deb
If the Vesta user commands (vcheckin, vcheckout, ...) are to be installed locally, execute the command:
sudo dpkg -i vesta-user-tools_2.1.12-pre13-13-1_amd64.deb
The repository, cache, and runtool are part of the vesta-server package. Only install this package on the machine that will be hosting your repository. From the same command shell, execute the command:
sudo dpkg -i vesta-server_2.1.12-pre13-13-1_amd64.deb
Configuring the Vesta Servers
When installing from the packages, a setup script called /usr/sbin/vesta-setup is installed on the system. After the packages are installed, run this script with root privileges, and answer all of the questions asked. If you answer any of the questions wrong, you can rerun the script. Changes to the configuration settings can be manually applied by editing the file /var/lib/vesta/vesta.cfg. Review /var/lib/vesta/base.vesta.cfg for the different settings that can be placed in vesta.cfg.
Vesta Repository Server
After installation is complete, access to the Vesta repository is limited to the local machine. To allow other computers on the network access to the repository, the file /etc/vesta/repos.export must be modified. Immediately after installation, a typical repos.export file would contain something like:
server.example.com: allow unix, allow global example.com server: allow unix, allow global example.com 192.168.1.10: allow unix, allow global example.com 127.0.0.1: allow unix, allow global example.com
To allow machines on your network access to the repository, additional lines must be added to the repos.export files. The man pages provided describe the syntax. Entries similar to the following would need to be added to your copy of repos.export.
*.example.com: allow unix, allow global example.com 192.168.1.0/24: allow unix, allow global example.com
Mounting the Repository
Vesta exports its files through an NFS interface. Unfortunately it's still using NFSV2, This results in some long timeouts when running on a current GNU/Linux distribution. Many of the commands issues will stall for 30 or 60 seconds. This appears to be from the NFS interface. I've read that using the "nolock" option when mounting an NFSV2 server using an NFSV4 client will solve this problem. I haven't tested this yet.