onShore TimeSheet uses a variety of utilities and tools, such as the Perl interpreter and PostgreSQL relational database management system, which should run on most flavors of unix and hardware platforms. However, since the onShore TimeSheet is in the beginning stages of wide-spread distribution, we are going to list what things are certified to work because they are what has already been used in production and extensive testing.
The general rule for hardware configuration is that whatever you feel comfortable with for decent web and database performance is an ideal configuration for onShore TimeSheet Any machine that Linux will run on will work, but keep in mind that the main components are a web server and a database back-end. The more memory you throw at both of those things, in general, the better they will perform. Also, since databases are usually pretty disk intensive, putting the database on a dedicated or less-used drive, separate from the web server and operating system will help performance. Here is what we certify will work:
Pentium 133 or above, 64 Megs+ memory, at least 2 drives. PostgreSQL's data storage should be on its own spindle and preferable spread across several different spindles using a RAID striping for maximum performance boost.
The following should generally work, in theory but are considered mostly untested and uncertified to work properly without more extensive testing:
Sun Solaris 2.6
Sparc 20, narrow SCSI disk array
To run onShore TimeSheet you must have a HTTP server capable of basic authentication and CGI scripting. Any web server should work in theory. The database back-end currently must be PostgreSQL, but we hope to enable onShore TimeSheet to plug into any relational, SQL-compliant relational database management system. Here is a list of certified software to run onShore TimeSheet:
Apache HTTP Server version 1.3 and above
Perl version 5.004_04 and above
PostgreSQL version 6.4.2 and above. 6.3.x should work on most systems, but we recommend you upgrade to 6.4.2 as there are some issues with 6.3.x and creating users with "-" in the username, as some HTTP servers such the one in Debian's Apache distribution, configure the HTTP server to run as the userid "www-data", which createuser will error out on trying to create as a PostgreSQL user in 6.3.x; this can be worked around, but it is easier to just upgrade, especially as the PostgreSQL site itself recommends upgrading to 6.4.2 because of bugs in previous versions.
You need to make sure that you also have the PostgreSQL/Perl modules, Pg.pm installed and on the standard Perl path.