In order to use PRepS, you must create at least one PRepS database. Each database can contain as many projects as you want, and you can create as many databases as you want. Before determining how many databases, you should ask yourself the following questions:
What different types of projects do I have?
Statuses, severities, and problem types are shared across all projets in a database. For that reason, you should group similar types of projects in the same database.
How much security do I need?
PRepS allows you to control access to the projects within the databases. The project leader must specify the users who are allowed to submit problem reports. The project leader must also specify the users who are allowed to update problem reports. However, you may have certain projects where you want to provide another level of security by separating projects into different databases, and using PostgreSQL GRANTs to determine database access.
create_prepsdb [-h | -v] [-d] [-o path] [-P path] [-p path] [-u username]
The create_prepsdb script is used to create new PRepS databases. The create_prepsdb script will create the database schema, insert the default data, and setup the database owner as the default PRepS administrator for that databse.
Note: The script will ask for an owner for the database. The user specified as the database owner must be setup as a PostgreSQL database user before this script is run.
To ensure proper operation, the create_prepsdb script must be run from the PostgreSQL super user account. The create_prepsdb script understands the following options.
-h : Display a simple help message and exit.
-v : Show the version information and exit.
-d : Use the default database name and description when creating the database. The default name is 'myprs'. The default description is 'Default PRepS Database'.
-o path : Allow the user to specify a writable directory that will be used for temp files, and for writing the log file.
-P path : Allow the user to supply the path to PL/pgSQL (plpgsql.so). Use this option if the script cannot find the PL/pgSQL library.
-p path : Allow the user to supply the path to the PostgreSQL tools. Use this option if the PostgreSQL bin directory is not in the PostgreSQL superuser's path.
-u username : Supply the owner of the resulting databse. If this option is not used, the script will ask for a user.