This page offers a brief installation recipe. Detailed instructions are available in other pages referenced from here.
- Create the Valet system user
- For the purposes of this document, we'll call the valet user valet-sys. Valet-sys should not have normal user privileges, but will own a directory used as a spool area and will run the Valet system programs.
- Create the Valet Program Files directory
- The program files directory - e.g. /usr/local/valet - is owned by root. This will be exported in the $VALET_BASE environment variable.
- Unpack Valet
- Unpack the tarball into the Program Files Directory.
- Create the Valet Workspace Directory
- The Workspace directory - e.g. /var/spool/valet - is owned by valet-sys.
- Select a Database Driver
- The database selected must of course be available on the system, and should be running at all times for Valet.
- Set up the Valet environment
- Ensure the Valet environment (as described in the environment page) is set whenever any of the Valet programs is run.
- Initialise the Database
- Run the setup script for your selected database (as the database administrator) to initialise the Valet database, tables and system privileges.
- Configure valetd
- The Valet daemon valetd shold be running (as valet-sys) at all times. Start it at the end of the boot sequence, when all networking is up and running.
- Configure Periodic Jobs
- Configure the cron jobs as described in the periodic jobs page
- Set up Users
- Set up an admin user, and other users as required (see the users page for details). Ensure that the users environment is set.
- Configure the System
- Start the Valet Client, and set up the general configuration, the MIMETypes and domains. These can of course be updated in future.
- Start valetd
- The spider will now start working. Note that (by design) it will work slowly at first, and it will some time - typically several hours - before there is sufficient data to be useful.
- Tell your users about it!
- Valet is now ready for your users to work with it using the Valet Client and/or Web Components.