documentation/content/developer/tutorials/setup_guide.md

# 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
({dfn}`running Odoo from the source code`).

:::{important}
Follow the {ref}`contributing/development/setup` section of the contributing guide to prepare
your environment for pushing local changes to the Odoo repositories.
:::

## 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.

:::{note}
Depending on the tutorial that you are following, you might not need to install all the modules
that this repository contains.
:::

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

   ```console
   $ 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**.

   ```{eval-rst}
   .. tabs::

      .. tab:: Link Git with your fork

         #. Visit `github.com/odoo/tutorials <https://github.com/odoo/tutorials>`_ and click the
            :guilabel:`Fork` button to create a fork of the repository on your account.

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

            .. code-block:: console

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

      .. tab:: Link Git with odoo-dev

         .. code-block:: console

            $ cd /tutorials
            $ git remote add dev git@github.com:odoo-dev/tutorials.git
            $ git remote set-url --push origin you_should_not_push_on_this_repository
   ```

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.

:::{important}
**For Odoo employees only:**

1. Make sure to read very carefully {ref}`contributing/development/first-contribution`. In particular,
   your branch name must follow our conventions.

2. Once you have pushed your first change to the shared fork on **odoo-dev**, create a
   {abbr}`PR (Pull Request)`. Please put your quadrigram in the PR title (e.g., "abcd - Technical
   Training").

   This will enable you to share your upcoming work and receive feedback from your coaches. To ensure
   a continuous feedback loop, we recommend pushing a new commit as soon as you complete a chapter
   of the tutorial. Note that the PR is automatically updated with commits you push to **odoo-dev**,
   you don't need to open multiple PRs.

3. At Odoo we use [Runbot](https://runbot.odoo.com) extensively for our {abbr}`CI (Continuous
   Integration)` tests. When you push your changes to **odoo-dev**, Runbot creates a new build
   and test your code. Once logged in, you will be able to see your branches [Tutorials project](https://runbot.odoo.com/runbot/tutorials-12).
:::

:::{note}
The specific location of the repositories on your file system is not crucial. However, for the
sake of simplicity, we will assume that you have cloned all the repositories under the same
directory. If this is not the case, make sure to adjust the following commands accordingly,
providing the appropriate relative path from the `odoo/odoo` repository to the
`odoo/tutorials` repository.
:::

## 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.

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

There are multiple {ref}`command-line arguments <reference/cmdline/server>` that you can use to run
the server. In this training you will only need some of them.

```{eval-rst}
.. option:: -d <database>

   The database that is going to be used.
```

```{eval-rst}
.. option:: --addons-path <directories>

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

```{eval-rst}
.. option:: --limit-time-cpu <limit>

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

```{eval-rst}
.. option:: --limit-time-real <limit>

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

:::{tip}
- The {option}`--limit-time-cpu` and {option}`--limit-time-real` arguments can be used to prevent
  the worker from being killed when debugging the source code.

- You may face an error similar to 

  `AttributeError: module '<MODULE_NAME>' has no attribute
  '<$ATTRIBUTE'>`

  . In this case, you may need to re-install the module with 

  {command}`$ pip
  install --upgrade --force-reinstall <MODULE_NAME>`

  .

  If this error occurs with more than one module, you may need to re-install all the
  requirements with 

  {command}`$ pip install --upgrade --force-reinstall -r requirements.txt`

  .

  You can also clear the python cache to solve the issue:

  > ```console
  > $ cd $HOME/.local/lib/python3.8/site-packages/
  > $ find -name '*.pyc' -type f -delete
  > ```

- Other commonly used arguments are:

  - {option}`-i <odoo-bin --init>`: Install some modules before running the server
    (comma-separated list). This is equivalent to going to {guilabel}`Apps` in the user interface,
    and installing the module from there.
  - {option}`-u <odoo-bin --update>`: Update some modules before running the server
    (comma-separated list). This is equivalent to going to {guilabel}`Apps` in the user interface,
    selecting a module, and upgrading it from there.
:::

### Log in to Odoo

Open <http://localhost:8069/> on your browser. We recommend using [Chrome](https://www.google.com/intl/en/chrome/), [Firefox](https://www.mozilla.org/firefox/new/), 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. {ref}`Enable the developer mode <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.

  ```console
  $ cd $HOME/src/odoo
  $ git switch {BRANCH}

  $ cd $HOME/src/enterprise
  $ git switch {BRANCH}
  ```

- Fetch and rebase:

  ```console
  $ cd $HOME/src/odoo
  $ git fetch --all --prune
  $ git rebase --autostash odoo/{BRANCH}

  $ cd $HOME/src/enterprise
  $ git fetch --all --prune
  $ git rebase --autostash enterprise/{BRANCH}
  ```

### Code Editor

If you are working at Odoo, many of your colleagues are using [VSCode](https://code.visualstudio.com), [VSCodium](https://vscodium.com) (the open source equivalent),
[PyCharm](https://www.jetbrains.com/pycharm/download/#section=linux), or [Sublime Text](https://www.sublimetext.com). 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](https://github.com/odoo/odoo/wiki/Javascript-coding-guidelines#use-a-linter).

### 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](https://www.pgadmin.org/download/pgadmin-4-apt/) or [DBeaver](https://dbeaver.io/).

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](https://docs.python.org/3/library/pdb.html),
[pudb](https://pypi.org/project/pudb/) or [ipdb](https://pypi.org/project/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:

   ```console
   pip install ipdb
   ```

2. Place a trigger (breakpoint):

   ```python
   import ipdb; ipdb.set_trace()
   ```

   ```{eval-rst}
   .. example::

      .. code-block:: python
         :emphasize-lines: 2

         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:

```{eval-rst}
.. option:: 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.
```

```{eval-rst}
.. option:: pp expression

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

```{eval-rst}
.. option:: w(here)

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

```{eval-rst}
.. option:: d(own)

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

```{eval-rst}
.. option:: u(p)

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

```{eval-rst}
.. option:: n(ext)

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

```{eval-rst}
.. option:: c(ontinue)

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

```{eval-rst}
.. option:: 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).
```

```{eval-rst}
.. option:: q(uit)

   Quit the debugger. The program being executed is aborted.
```