About OpenERP
-------------
OpenERP is an OpenSource/Free software Enterprise Resource Planning and
Customer Relationship Management software. More info at:
http://www.openerp.com
Installation on Debian/Ubuntu
-----------------------------
Add the the apt repository
deb http://nightly.openerp.com/6.1/deb/ ./
in your source.list and type:
$ sudo apt-get update
$ sudo apt-get install openerp
Or download the deb file and type:
$ sudo dpkg -i <openerp-deb-filename>
$ sudo apt-get install install -f
Installation on RedHat, Fedora, CentOS
--------------------------------------
Install the required dependencies:
$ yum install python
$ easy_install pip
$ pip install .....
Install the openerp rpm
$ rpm -i openerp-VERSION.rpm
Installation on Windows
-----------------------
Check the notes in setup.py
Installation on MacOSX
-----------------------
Setuping you first database
---------------------------
Point your browser to http://localhost:8069/ and click "Manage Databases", the
default master password is "admin".
Detailed System Requirements
----------------------------
The dependencies are listed in setup.py
For Luxembourg localization, you also need:
pdftk (http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/)
Olivier Dony
authored
Due to the multi-company record rule on gamification.goal, each access to the Goals menu and each opening of the Messaging menu (thus calling get_serialised_gamification_summary()) is extremely slow (with several thousands goals/users). Adding auto_join to the user_id FK on goals makes it much faster. However it causes crashes when reading the table because the _order of gamification.goal uses `create_date`, which becomes ambiguous after the auto_join with res_users. Solving this can be done by re-implementing _read_flat() in the ORM using the internal Query object, as in search(), which takes care of fully-qualifying all column names. Until this is fixed, a simple workaround is to use start_date in the _order instead of collision-prone `create_date`.