Setup guide¶

Depending on the intended use case, there are multiple ways to install Odoo. For developers of the Odoo community and Odoo employees alike, the preferred way is to perform a source install (running Odoo from the source code).

Adapt the environment for the tutorials¶

By now, you should have downloaded the source code into two local repositories, one for odoo/odoo and one for odoo/enterprise. These repositories are set up to push changes to pre-defined forks on GitHub. This will prove to be convenient when you start contributing to the codebase, but in the scope of following a tutorial, we want to avoid polluting them with training material. Let’s then push your changes in a third repository: odoo/tutorials. Like the first two repositories, it will be part of the addons-path that references all directories containing Odoo modules.

1. Following the same process as with the odoo/odoo and odoo/enterprise repositories, clone the odoo/tutorials repository on your machine with:

   $ git clone git@github.com:odoo/tutorials.git
   

2. Configure your fork and Git to push changes to your fork rather than to the main codebase. If you work at Odoo, configure Git to push changes to the shared fork created on the account odoo-dev.

   Link Git with your forkLink Git with odoo-dev

   1. Visit github.com/odoo/tutorials and click the Fork button to create a fork of the repository on your account.

   2. In the command below, replace <your_github_account> with the name of the GitHub account on which you created the fork.

      $ cd /TutorialsPath
      $ git remote add dev git@github.com:<your_github_account>/tutorials.git
      

That’s it! Your environment is now prepared to run Odoo from the sources, and you have successfully created a repository to serve as an addons directory. This will allow you to push your work to GitHub.

Run the server¶

Launch with odoo-bin¶

Once all dependencies are set up, Odoo can be launched by running odoo-bin, the command-line interface of the server.

$ cd $HOME/src/odoo/
$ ./odoo-bin --addons-path="addons/,../enterprise/,../tutorials" -d rd-demo

There are multiple command-line arguments that you can use to run the server. In this training you will only need some of them.

-d <database>¶

The database that is going to be used.

--addons-path <directories>¶

A comma-separated list of directories in which modules are stored. These directories are scanned for modules.

--limit-time-cpu <limit>¶

Prevent the worker from using more than <limit> CPU seconds for each request.

--limit-time-real <limit>¶

Prevent the worker from taking longer than <limit> seconds to process a request.

Log in to Odoo¶

Open http://localhost:8069/ on your browser. We recommend using Chrome, Firefox, or any other browser with development tools.

To log in as the administrator user, use the following credentials:

• email: admin

• password: admin

Enable the developer mode¶

The developer or debug mode is useful for training as it gives access to additional (advanced) tools. Enable the developer mode now. Choose the method that you prefer; they are all equivalent.

Extra tools¶

Useful Git commands¶

Here are some useful Git commands for your day-to-day work.

• Switch branches:

  When you switch branches, both repositories (odoo and enterprise) must be synchronized, i.e. both need to be in the same branch.

  $ cd $HOME/src/odoo
  $ git switch 18.0
  
  $ cd $HOME/src/enterprise
  $ git switch 18.0
  

• Fetch and rebase:

  $ cd $HOME/src/odoo
  $ git fetch --all --prune
  $ git rebase --autostash odoo/18.0
  
  $ cd $HOME/src/enterprise
  $ git fetch --all --prune
  $ git rebase --autostash enterprise/18.0
  

Code Editor¶

If you are working at Odoo, many of your colleagues are using VSCode, VSCodium (the open source equivalent), PyCharm, or Sublime Text. However, you are free to choose your preferred editor.

It is important to configure your linters correctly. Using a linter helps you by showing syntax and semantic warnings or errors. Odoo source code tries to respect Python’s and JavaScript’s standards, but some of them can be ignored.

For Python, we use PEP8 with these options ignored:

• E501: line too long

• E301: expected 1 blank line, found 0

• E302: expected 2 blank lines, found 1

For JavaScript, we use ESLint and you can find a configuration file example here.

Administrator tools for PostgreSQL¶

You can manage your PostgreSQL databases using the command line as demonstrated earlier or using a GUI application such as pgAdmin or DBeaver.

To connect the GUI application to your database we recommend you connect using the Unix socket.

• Host name/address: /var/run/postgresql

• Port: 5432

• Username: $USER

Python Debugging¶

When facing a bug or trying to understand how the code works, simply printing things out can go a long way, but a proper debugger can save a lot of time.

You can use a classic Python library debugger (pdb, pudb or ipdb), or you can use your editor’s debugger.

In the following example we use ipdb, but the process is similar with other libraries.

1. Install the library:

   pip install ipdb
   

2. Place a trigger (breakpoint):

   import ipdb; ipdb.set_trace()
   

   Example

   def copy(self, default=None):
       import ipdb; ipdb.set_trace()
       self.ensure_one()
       chosen_name = default.get('name') if default else ''
       new_name = chosen_name or _('%s (copy)') % self.name
       default = dict(default or {}, name=new_name)
       return super(Partner, self).copy(default)
   

Here is a list of commands:

h(elp) [command]¶

Print the list of available commands if not argument is supplied. With a command as an argument, print the help about that command.

pp expression¶

The value of the expression is pretty-printed using the pprint module.

w(here)¶

Print a stack trace with the most recent frame at the bottom.

d(own)¶

Move the current frame one level down in the stack trace (to a newer frame).

u(p)¶

Move the current frame one level up in the stack trace (to an older frame).

n(ext)¶

Continue the execution until the next line in the current function is reached or it returns.

c(ontinue)¶

Continue the execution and only stop when a breakpoint is encountered.

s(tep)¶

Execute the current line. Stop at the first possible occasion (either in a function that is called or on the next line in the current function).

q(uit)¶

Quit the debugger. The program being executed is aborted.