This is the documentation for older versions of Odoo (formerly OpenERP).

See the new Odoo user documentation.

See the new Odoo technical documentation.


Two configuration files are available:

  • one for the client: ~/.openerprc

  • one for the server: ~/.openerp_serverrc

Those files follow the convention used by python's ConfigParser module.

Lines beginning with "#" or ";" are comments.

The client configuration file is automatically generated upon the first start. The one of the server can automatically be created using the command: -s

If they are not found, the server and the client will start with the default configuration.

Server Configuration File

The server configuration file .openerp_serverrc is used to save server startup options. Here is the list of the available options:


Address to which the server will be bound


Port the server will listen on


Name of the database to use


Username used when connecting to the database


File used to translate OpenERP to your language


File used to export the language OpenERP use


Use this language as the language of the server. This must be specified as an ISO country code, as specified by the W3C.


Enable debug output


init a module (use "all" for all modules)


update a module (use "all" for all modules)


Upgrade/install/uninstall modules


specify the database name


specify the database user name


specify the database password


specify the pg executable path


specify the database host


specify the database port


Specify modules to export. Use in combination with --i18n-export

You can create your own configuration file by specifying -s or --save on the server command line. If you would like to write an alternative configuration file, use -c <config file> or --config=<config file> Here is a basic configuration for a server:

verbose = False
xmlrpc = True
database = terp
update = {}
port = 8069
init = {}
interface =
reportgz = False

Full Example for Server V5.0

path = none
softpath_html = none
preview = True
softpath = none

output = stdout
logger =
verbose = True
level = error

index =
context =

autosave = False
toolbar = True

recipient =
support_id =

position = 0
autostart = False

lang = en_US
default_path = /home/user
filetype = {}
theme = none
toolbar = icons
form_tab_orientation = 0
form_tab = top

position = 3

pixmaps = /usr/share/pixmaps/openerp-client/
share = /usr/share/openerp-client/

db = eo2
login = admin
protocol = http://
port = 8069
server = localhost

GTK-Client Configuration

login section


login name to use to connect to OpenERP server


address used by the server


port used by the server

path section


path used to find OpenERP shared files


path used to find OpenERP pixmaps files

tip section


Should the client display tips at startup


Tip number the client will display

form section


The client will automatically save the change you made to a record

printer section


Preview report before printing


Path to the pdf previewer


Path to the html previewer


Command used to print

logging section


log channels to display. List values are: @common@, @common.message@, @view@, @view.form@, @common.options@, @rpc.request@, @rpc.result@, @rpc.exception@


logging level to show


file used by the logger


set the log level to INFO

client section


Default path used by the client when saving/loading data.

Default values:

login = admin
port = 8069
server =

path = none
preview = True
softpath = none

output = stdout
logger =
verbose = True
level = ERROR

autosave = False

default_path = /home/user

Web Client Configuration

Full Example for web Client Configuration

# Some server parameters that you may want to tweak
server.socket_host = ""
server.socket_port = 8080

# Sets the number of threads the server uses
server.thread_pool = 10

server.environment = "development"

# Simple code profiling
server.profile_on = False
server.profile_dir = "profile"

# if this is part of a larger site, you can set the path to the TurboGears instance here
server.webpath = ""

#log.access_file = "/var/log/openerp-web/access.log"
#log.error_file = "/var/log/openerp-web/error.log"

# OpenERP Server
host = 'localhost'
port = '8070'
protocol = 'socket'

# Web client settings
# filter dblists based on url pattern?
# NONE: No Filter
# EXACT: Exact Hostname
# UNDERSCORE: Hostname_
# BOTH: Exact Hostname or Hostname_

dblist.filter = 'NONE'

# whether to show Databases button on Login screen or not
dbbutton.visible = True

# will be applied on company logo
company.url = ''

# options to limit data rows in M2M/O2M lists, will be overriden
# with limit="5", min_rows="5" attributes in the tree view definitions
child.listgrid.limit = 5
child.listgrid.min_rows = 5

Get a clone of each repository:

bzr clone lp:~openerp/openobject-server/trunk server
bzr clone lp:~openerp/openobject-client/trunk client
bzr clone lp:~openerp/openobject-client-web/trunk client-web
bzr clone lp:~openerp/openobject-addons/trunk addons

If you want to get a clone of the extra-addons repository, you can execute this command:

bzr clone lp:~openerp-commiter/openobject-addons/trunk-extra-addons extra-addons

run the setup scripts in the respective directories:

python2.5 build
sudo python2.5 install

Currently the initialisation procedure of the server parameter --init=all to populate the database seems to be broken in trunk.

It is recommended to create a new database via the gtk-client. Until then the web-client will not work.

Start OpenERP server like this:

./ --addons-path=~/home/workspace/stable/addons

The bin/addons will be considered as default addons directory which can be overriden by the ~/home/workspace/stable/addons. That is if an addon exists in bin/addons as well as ~/home/workspace/stable/addons (custom path) the later one will be given preference over the bin/addons (default path).