About ]po[ Installers

­There are several ways to install and use ]­pr­oject-open[, each with specific advantages and disadvantages. Below is a list of possible options, in order of increasing ­tech­nical difficulty.  Each entry on this page is only a brief discussion of the option, with a link to forward you to a page with a more in-depth examination of the installation.

• Demo Server:
  Demo Server - If y­ou are just curious about ]project-open[ or would like to quickly evaluate/test our software with little investment of time or hassle, try on our online demo-server for a quick walk through.
  
  
• SaaS:
  Software as a Service (SaaS) - The most hassle free way to get your company up and running with ]project-open[. You need only an internet connection, a few hours of preparation and you're ready to go.
  
  
• Native Installers:
  Please choose your operating system and install ]project-open[. Please see the system requirements below.
  

• Debian
• Red Hat Enterprise Linux 5/CentOS 5
• Ubuntu
• Windows
  
  

• ]po[ Virtual Machine
  Our VMware appliance includes a complete ]project-open[ installation on CentOS Linux configured for production use. VMware  players  are available for Windows and Linux platforms.
   

• CVS
  To load additional modules or update your local installations, a CVS server is at your disposal at anonymous@cvs.project-open.net:/home/cvsroot  (no PW)
  

Developer Version ]po[ 4.0

For a sneak preview of Version 4.0 please download our VM at sourceforge.net  and consider running the update files you find in the same folder.
Provide feedback and inquire for community support of this installer in this sourceforge forum thread.  

Services Offered

Please contact us if you are going to use ]project-open[ in production. Most customers will need at least a few hours of configuration and training services  before a go-live, in order to take full advantage of the application's options. Also­, we can provide organizations with help on project definition, scoping and change management.­

Demo Server

To evaluate the functionality of ]project-open[ you can use our demo server:

• http://demo.project-open.net  (Version 3.4)
  The disadvantage of the demo servers is that you can not log-in as an Administrator for security reasons.  The Demo Server is pre-configured with several fictitious users and sample companies mimicking real life scenarios that ]project-open[ is designed to work for.         ­

Software as a Service (SaaS)

SaaS allows a company to use ]project-open[ without committing itself to the technical details of installation and maintenance.  By paying a monthly subscription, companies gain access to their own private online server with full ]project-open[ admin privileges which is maintained by the ]project-open[ team. This is ideal for companies without internal IT staff or do not wish to make the full investment of an on-site ]project-open[ installation. For additional information please refer to http://www.project-open.com/en/services/project_open_hosting_saas.html .

System Requirements 

Before attempting to run ]project-open[ locally on your machine make sure your hardware complies with these minimum prerequisites. 

• A computer running Windows or Linux
• At least 1GHz AMD or Intel processor
• At least 1GByte RAM
• At least 20GByte of free disk space

Those are the minimum requirements.  However, to run ]project-open[ in production we recommend:

• A server running Windows or Linux
• 2GHz AMD or Intel processor
• 4GByte RAM
• 50GByte of free disk space
• aDSL Internet connection

Installation in restricted environments (Linux only)

In restricted environments installation tasks might be shared btw. two teams:  

Step 1:
Client/Service Provider provides a pre-configured installation of OS, DB, etc. in form of a Linux server (preferable CentOS 5.x/6.x) with the following packages pre-installed: 

• cvs
• wget
  
• PostgreSQL 
• postgresql-8.4.xx.x
  
• postgresql-contrib-8.4.xx.x
  
• postgresql-server-8.4.xx.x
  
• postgresql-libs-8.4.xx.x
• imageMagick
• gcc
  
• graphviz
• git-core
  

Other configuration steps that can be performed during this stage:

• Creating a linux group and user 'projop'
• Creating a DB user 'projop'
• Creating a DB 'projop' (owner: projop)
  

Step 2: ]po[ Core Team or Partner installs ]po[ and AOLServer

• Core team or Partner requires: 
  
• Temporary root access to finetune configuration settings
  
• Fully working cvs/wget (ports 80 and 22 to be open during installation)
  

Proxy Configuration

• cvs access is mandatory. If the cvs port is blocked, it should be assured that access can be established through a HTTP Proxy.
• To make wget set up ~/.wgetrc accordingly.
  
  Example:  
  

    http_proxy=http://[IP]:[PORT]/
    use_proxy=on
    wait=15
   

References:

• Installation FAQ