Congratulations, you have installed and started jCVSWeb.

Before you begin to do anything, you should be sure to perform the following steps to be sure to minimize your grief:

• Decide on where you want your files.
• Login as 'admin' (password 'admin') and change the password.
• Login as 'admin' and select 'Edit Config Dir' from the admin menu.
• Login as 'admin' and select 'Edit Config' from the admin menu.
• If you want to change the home page, edit 'WEB-INF/tiles/Home.jsp'.

You should change the configuration location. You do that with the 'Edit Config Dir' command in the admin menu (the red menu on the left side). The configuration location is the directory in which the 'jcvs-config.xml' file is stored, and where all of the other configuration files (project, user, permission, etc.) are located. It is a good idea to change this directory to one that is not located under the webapp's 'WEB-INF' directory. That way, whenever you upgrade jCVSWeb, the only thing you will have to do is change this location. Your previous configuration will then be picked up. If you do not change this directory, then anytime you upgrade, you will have to backup the configuration under the webapp's 'WEB-INF/conf' directory, then replace it after you have deployed the new jCVSWeb webapp.

Where do you want your files? The default distribution will place files, configuration files, logo files, working directories, and temp files, all under the 'WEB-INF' directory of the webapp. However, this may not be what you wish to do. Why? Because the next time you want to update jCVSWeb, those files will have to be moved to a temporary location to avoid being overwritten. Then they will have to be moved back into place under the newly deployed webapp's 'WEB-INF' directory.

Instead, you may wish to place all of those files under a separate directory, allowing you to update jCVSWeb without having to touch the files. You will simply edit the configuration to point to the directories you are using. This will greatly simplify life when it comes to upgrades. NOTE that you must make sure that your webapp server (Tomcat, for example) has read and write permission for the directories and files to which you point the configuration.

This page will be presented as the "Home" page until you edit and save the configuration. Afterward you may refer to this page using the link at the bottom of the home page.