Forem: Abraham

Odoo Docker fix print bug

Abraham — Sat, 19 Jul 2025 10:28:12 +0000

If you've followed my previous tutorial on how to install Odoo 17 using Docker, you might have encountered an issue where wkhtmltopdf doesn't work properly. This is a common problem many face during PDF generation, and it’s caused by a wkhtmltopdf bug when running inside certain Docker environments.

The Problem

When generating PDFs in Odoo (e.g., for invoices or reports), the result might look broken — not only is the header missing, but also the CSS and overall styling fail to load properly. This typically happens because wkhtmltopdf cannot access the correct internal URLs or assets during rendering in a Docker container.

Broken PDF example:

The Solution

To fix this issue, you just need to add a system parameter in Odoo's settings:

Navigate to Settings → Technical → Parameters → System Parameters.
Add the following parameter:

💡 If you don’t see the "System Parameters" menu, make sure you have activated developer mode.

Fixed PDF

While wkhtmltopdf bugs can be frustrating, this quick fix will save you hours of troubleshooting. Once you set the report.url parameter, your reports should render perfectly with the correct headers, styles, and layout. This is especially important because printing is deeply integrated across many Odoo modules from quotations to logistics.

Odoo Developer 101: OOP

Abraham — Sat, 12 Jul 2025 12:43:15 +0000

OOP Definitions

OOP(Object Oriented Programming) is a programming paradigm not only in Odoo but in the overall programming world. To better understand this OOP you can use blueprint analogy. Imagine we're building a car.

A car consists of various parts tires, chassis, and body. Each has its own purposes and properties(e.g., a tire has material, size, and tread pattern).

In programming, these components can be modeled as classes, which act as blueprints for creating objects. This approach allows developers to break down a complex system into manageable, reusable components.

OOP in Odoo

Odoo is built entirely around OOP principles. When you create a new model (e.g., res.partner), you're creating a class that inherits from a base class (models.Model).

This allows for:

Code reuse
Extensibility
Better organization
Easier debugging and maintenance

Advantages of OOP in Odoo

1. Modularity & Maintainability

Each component or class handles one responsibility, as a developer we can be more focused when developing or debugging the code.

For example a login system can be divided into component like this:

Database Access - manage reading/writing user data
Authentication - handle login validation
UI Handling - manage user interaction and input flow

2. Inheritance (Blueprint Functionality)

Previously I said that OOP is like a blueprint in a big system. This mean a blueprint can be extended or used in creating a specified system.

Example:

class BaseModel(models.Model):
    _abstract = True
    create_date = fields.Date()
    write_date = fields.Date()

class User(BaseModel):
    name = fields.Char()

class Car(BaseModel):
    model_type = fields.Char()

Here, User and Car both inherit the fields create_date and write_date from BaseModel. This prevents code duplication.

ℹ️ In OOP terms, BaseModel is the parent class, while User and Car are child classes.

3. Overriding

As we discussed earlier, inheritance allows a child class to reuse methods from its parent class. However, sometimes we don’t want to use the inherited version of a method because it doesn’t suit the specific behavior we need. So overriding can be used for this issue.

Example:

class BaseModel(models.Model):
    def print_info(self):
        print("This is a base model")

class User(BaseModel):
    def print_info(self):
        print("This is a user model")

class Car(BaseModel):
    def print_info(self):
        print("This is a car model")

Now, calling print_info() on a User or Car instance will execute their specific version, not the one from BaseModel.

🔸 In Odoo and Python, the child class method always overrides the parent if they share the same method name.

4. Method Extension

Previously we override the whole method removing the parent method. In some cases, we only want to add extra behavior to a method but still keep the original functionality. Instead of completely overriding the method, we can extend it using Python’s super() function. The principle is simple we will called the previous method and add our piece of code.

Example:

class BaseModel(models.Model):
    def write(self, vals):
        print("Base write logic")
        return super(BaseModel, self).write(vals)

class User(BaseModel):
    def write(self, vals):
        res = super(User, self).write(vals)
        print("Additional logic after writing User")
        return res

class Car(BaseModel):
    def write(self, vals):
        print("Custom logic before writing Car")
        res = super(Car, self).write(vals)
        return res

This pattern is common in Odoo when you want to:

Call the original logic (super())
Add logging, triggers, or other custom behaviors

Closing

Understanding Object-Oriented Programming is essential for every Odoo developer, as it forms the foundation of how Odoo is built and extended. Concepts like inheritance, overriding, and method extension enable you to write clean, modular, and maintainable code while leveraging the full power of the Odoo framework. Whether you're creating new models or customizing existing ones, thinking in terms of objects will help you build scalable solutions and contribute more effectively to any Odoo project.

Odoo 101: View

Abraham — Thu, 26 Jun 2025 07:56:33 +0000

If you're just starting with Odoo development, understanding how views, menus, and UI logic work is essential. In this guide, we’ll walk through the basics of creating views, linking them to menus and actions, understanding different view types, and how to extend existing views from other modules.

📁 1. How to Create a View

🔹 View Directory Structure

In your custom module, organize the views like this:

your_module/
├── __init__.py
├── __manifest__.py
├── models/
├── views/
│   └── library_book_views.xml

🔹 Define XML View

Example of a basic form and tree view:

<odoo>
    <!-- Tree View -->
    <record id="view_library_book_tree" model="ir.ui.view">
        <field name="name">library.book.tree</field>
        <field name="model">library.book</field>
        <field name="arch" type="xml">
            <tree>
                <field name="name"/>
                <field name="author"/>
            </tree>
        </field>
    </record>

    <!-- Form View -->
    <record id="view_library_book_form" model="ir.ui.view">
        <field name="name">library.book.form</field>
        <field name="model">library.book</field>
        <field name="arch" type="xml">
            <form string="Library Book">
                <group>
                    <field name="name" readonly="1"/>
                    <field name="author" invisible="state == 'draft'"/>
                </group>
            </form>
        </field>
    </record>
</odoo>

🔹 Register View in Manifest

In __manifest__.py:

'data': [
    'views/library_book_views.xml',
],

⚠️ Important Note: Order of XML Files in Manifest

When adding XML files to the data section of your manifest.py, make sure that any files defining record IDs that will be referenced later (like menus, views, or actions) are listed first.

For example, if a view references a menuitem or action by id, the XML file containing that referenced record must appear above the current file in the list.

'data': [
    'views/menu.xml',             # Defines menuitem IDs
    'views/library_book_views.xml',  # Uses menuitem/action/component IDs defined above
],

If you reverse the order and library_book_views.xml tries to attach to a menuitem that hasn't been defined yet, Odoo will raise a ValueError because it cannot find the referenced ID.

🧭 2. Menu Items and Submenus

Menus in Odoo follow a hierarchy and sequence.

<!-- Root Menu -->
<menuitem id="library_menu_root" name="Library" sequence="10"/>

<!-- Submenu -->
<menuitem id="library_menu_books" name="Books"
          parent="library_menu_root" sequence="20"/>

sequence: lower numbers show higher in the menu
parent: defines nesting (submenu)

⚙️ 3. Actions and View Types (`act_window`)

To make a menu open a specific model/view, define an action:

<record id="action_library_book" model="ir.actions.act_window">
    <field name="name">Books</field>
    <field name="res_model">library.book</field>
    <field name="view_mode">tree,form</field>
</record>

<menuitem id="library_menu_books" name="Books"
          parent="library_menu_root" action="action_library_book"/>

👓 4. View Types in Odoo

📄 tree (List View)

Displays a list of records. Can include:

<tree editable="bottom">
    <field name="name"/>
</tree>

📝 form

Used for creating or editing a record.

Tips:
When we use many2many, one2many we can display them using tree.

<form>
    <field name="name"/>
    <field name="line_ids">
        <tree editable="bottom">
            <field name="product_id"/>
            <field name="quantity"/>
        </tree>
    </field>
</form>

🧱 kanban

Used for stage-based workflows (like CRM pipelines).

<kanban>
    <templates>
        <t t-name="kanban-box">
            <div><strong><field name="name"/></strong></div>
        </t>
    </templates>
</kanban>

🔍 search

Adds filters and group-by options.

<search>
    <field name="name"/>
    <filter name="draft" string="Draft" domain="[('state','=','draft')]"/>
</search>

🎛️ 5. Widgets

Widgets control how a field appears in the UI:

<field name="priority" widget="priority"/>
<field name="image" widget="image"/>
<field name="tags" widget="many2many_tags"/>

List of widgets here

🔁 6. Inheritance from Other Module

You can inherit and modify views using inherit_id and xpath. You can use inherit component when you want to modify component attributes or replacing component.

<record id="view_partner_form_inherit" model="ir.ui.view">
    <field name="name">res.partner.form.inherit</field>
    <field name="model">res.partner</field>
    <field name="inherit_id" ref="base.view_partner_form"/>
    <field name="arch" type="xml">
        <xpath expr="//field[@name='phone']" position="after">
            <field name="x_loyalty_points"/>
        </xpath>
    </field>
</record>

🧩 7. QWeb Sneak Peek (Teaser)

QWeb is used for:

PDF reports
Kanban customization
Client-side rendering

A teaser example:

<t t-name="MyCustomTemplate">
    <div class="my-box">
        <t t-esc="doc.name"/>
    </div>
</t>

📌 More of QWeb will be covered in Odoo 101: QWeb

✅ Final Tips

Enable developer mode to inspect view IDs and structure
Always test your views with real data for usability

Odoo CE: Automatic Inventory Valuation

Abraham — Sat, 14 Jun 2025 09:01:14 +0000

What is Odoo Automatic Inventory Valuation?

Automatic Inventory Valuation in Odoo allows stock movements (such as receipts, deliveries, and internal transfers) to automatically generate corresponding accounting journal entries. This ensures that your inventory valuation is always accurate and reflects in your financial reports in real-time.

Previously, this feature was restricted to the Odoo Enterprise Edition. However, starting with Odoo 17, the Community Edition now supports automatic valuation technically — although it still lacks the full UI to enable it directly. With some manual setup, you can fully use this feature without paying for Enterprise.

📖 Read more in the official Odoo documentation:

Inventory Valuation Configuration — Odoo 17.0 Docs

How to Enable Automatic Inventory Valuation in Odoo Community

Since the interface to toggle this feature is hidden in Community, you must manually enable the required groups and permissions.

Step-by-step Instructions

1. Activate Stock Accounting Automatic for the user:

Navigate to: Settings > Users & Companies > Users
Select a user (e.g., admin).
Under the Technical tab, manually enable the group: Stock Accounting Automatic

2. Show Accounting Features in Inventory Settings:

Navigate to: Settings > Users & Companies > Groups
Search for: "Show Accounting Features - Readonly"
Add the previously selected user to this group.

3. Configure Product Category for Automated Valuation:

Navigate to: Inventory > Configuration > Product Categories
Select or create a product category.
Under the Inventory Valuation section:
- Set Inventory Valuation to: Automated
- Set Costing Method: Standard, FIFO, etc.
- Choose the appropriate:
  - Inventory Valuation Account
  - Stock Input/Output Accounts
  - Inventory Journal

Additional Notes

🧩 Enable Full Accounting in Odoo Community

Odoo Community Edition comes with limited accounting features by default. To unlock full accounting functionality (like journals, budgets, P&L reports, and more), consider installing this excellent community module:

🔗 Base Accounting Kit

https://apps.odoo.com/apps/modules/17.0/base_accounting_kit

This module enhances Community Edition with much of the functionality typically found in Enterprise, making it ideal for real-world business use.

Conclusion

With a few manual steps, Odoo Community Edition can now support automatic inventory valuation — a significant feature for accurate, real-time stock accounting. This makes Odoo Community much more powerful for SMEs that require integrated inventory and accounting without paying for Enterprise Edition.

Odoo 101: Create a Module

Abraham — Sun, 01 Jun 2025 12:41:02 +0000

Introduction

Hello everyone today I want to share about Odoo Development. In this tutorial I will cover about creating module, and install it on your local Odoo.

Creating a new module

1. Create module dir

In this steps we must create a dir file in the addons directory.

Requirement:

Lowercase only, Example: sale_order, not SaleOrder or Sale-Order.
Underscores for separation, Use underscores (_) to separate words instead of dashes or camelCase. Example: helpdesk_repair, product_warranty.
Avoid special characters Only use letters, numbers, and underscores. Avoid spaces, dashes, dots, or other symbols.
Unique across the Odoo instance

ps: addons directory can be seen on odoo.conf

tips: dir name is very important because it will be used when a module is being depend on.

2. Create Manifest file

In this steps we will add __manifest__.py file in the root of the module directory.

Example:

sale_dashboard
|
└── __manifest__.py

Below is manifest example

{
    'name': <Application Name(str)>,
    'version': <Application Version(str)>,
    'summary': <Application Summary(str)>,
    'description': <Application Description(str)>,
    'author': <Author(str)>,
    'depends': <Dependency(list(str))>,
    'category': <Application Category(str)>,
    'data': <Data File(list(str))>, 
    'assets': <Static asset(dict(str))>,
    'license': <Application License(str)>,
    'application': <Is this application or technical app(Bool)>,
}

depends: Specify dependency modules of the current module. When the module is installed, the depend module will automatically installed.
license: Specify license for the module. Supported license: AGPL-3, GPL-3, LGPL-3, OPL-1, Other OSI approved licence, Other proprietary, OEEL-1. More information here.

3. Install module into Odoo

Firstly, we must open the Odoo in your web browser. In my case I use http://localhost:10017/web

Secondly, we activate the debug mode. Debug mode can be activated by adding ?debug=1 in the url. After activating debug mode, we can now see Update App List button.

After clicking Update App List, a window will be opened and we can update the app list.

Updating app list could be used to insert new added app into Odoo app.

Finally, we can search the app by using the search bar.

When searching odoo module we can use the name from module directory or the name from manifest file.

Final Words

This is the end of tutorial, there are still a lot of things to covers for example creating a view, adding icons, creating models, wizard, depending on other module, Qweb, uploading module to Odoo store, etc. I will continue about Odoo tutorial in the next article.

Odoo Introduction

Abraham — Sat, 31 May 2025 04:18:05 +0000

Unlocking Business Potential: A Comprehensive Introduction to Odoo

In today's fast-paced business landscape, integrated management solutions are no longer a luxury but a necessity. Companies are constantly seeking ways to streamline operations, enhance efficiency, and gain a holistic view of their processes. Enter Odoo, a powerful suite of open-source business management software that has rapidly gained traction worldwide. This article delves into the core of Odoo, exploring its definition, key features, how it stacks up against competitors, and what to expect regarding its learning curve.

What is Odoo?

Odoo, originally known as OpenERP, stands for "On-Demand Open Object." It is an all-in-one business management software that offers a comprehensive suite of integrated applications to manage various business processes. Unlike traditional siloed software, Odoo operates on a unified platform, allowing seamless data flow and communication across different departments.

At its heart, Odoo's philosophy revolves around providing a modular yet fully integrated system. Businesses can select and implement only the applications (or "modules") they need, ranging from customer relationship management (CRM) and accounting to manufacturing, inventory, human resources, and e-commerce. This modularity ensures flexibility and scalability, allowing companies to start small and expand their Odoo implementation as their needs evolve.

Odoo is available in two main editions:

Odoo Community: The open-source, free edition that provides core functionalities and is maintained by the Odoo community.
Odoo Enterprise: A proprietary, paid edition that offers additional features, mobile app access, dedicated support, and hosting options, catering to larger businesses with more complex requirements.

Key Features and Modules

Odoo's strength lies in its extensive range of integrated applications, each designed to address specific business needs. Here's a glimpse into some of its most prominent modules:

These modules work synergistically, eliminating data redundancy and providing real-time insights across the organization. For instance, a sales order placed in the Sales module can automatically trigger inventory updates, accounting entries, and manufacturing orders if needed.

Odoo in Comparison: Standing Against the Giants

Odoo operates in a competitive landscape, vying with established Enterprise Resource Planning (ERP) solutions. Here's a comparison with some of its prominent competitors:

SAP Business One:
- Focus: Geared towards small and medium-sized enterprises (SMEs), offering a comprehensive suite for various business functions.
- Strengths: Industry-specific solutions, robust financial management, strong global presence.
- Weaknesses: Can be costly, requires significant implementation expertise, less flexible for deep customization compared to Odoo's open-source nature.
- Odoo vs. SAP B1: Odoo generally offers more flexibility due to its open-source nature and a lower entry cost, especially with the Community edition. SAP B1 is often seen as more complex to implement and maintain, but provides deep industry-specific functionalities out-of-the-box.
NetSuite (Oracle NetSuite):
- Focus: Cloud-based ERP for businesses of all sizes, known for its strong financial and e-commerce capabilities.
- Strengths: Highly scalable, powerful reporting, robust financial management, extensive e-commerce features.
- Weaknesses: High cost, complex implementation, can be overkill for smaller businesses.
- Odoo vs. NetSuite: NetSuite is a premium cloud-native solution with a higher price tag. Odoo provides a more cost-effective alternative with greater customization potential and a more flexible deployment model (on-premise or cloud).
Microsoft Dynamics 365:
- Focus: A suite of modular cloud-based business applications, combining ERP and CRM functionalities.
- Strengths: Seamless integration with other Microsoft products (Office 365, Power BI), strong analytics, familiar user interface for Microsoft users.
- Weaknesses: Can be complex and costly, requires significant customization for specific business needs, licensing can be intricate.
- Odoo vs. Dynamics 365: Odoo offers a more unified and typically less expensive solution for end-to-end business management. Dynamics 365 excels in deep integration within the Microsoft ecosystem, but its modular nature can lead to higher cumulative costs and integration challenges if not managed carefully.
ERPNext:
- Focus: Another open-source ERP solution, often seen as a direct competitor to Odoo in the open-source space.
- Strengths: User-friendly interface, comprehensive features for SMEs, active community.
- Weaknesses: Smaller ecosystem of third-party apps compared to Odoo, less widespread adoption.
- Odoo vs. ERPNext: Both are excellent open-source choices. Odoo often has a larger community, more third-party apps, and a slightly more polished interface, while ERPNext is praised for its simplicity and ease of use.
Zoho One:
- Focus: A comprehensive suite of over 40 business applications, primarily targeting small and medium-sized businesses.
- Strengths: Affordable, vast array of integrated apps, good for businesses seeking an all-in-one suite without extensive customization.
- Weaknesses: Not a true ERP, more of a collection of business apps, deep customization is limited compared to Odoo.
- Odoo vs. Zoho One: Odoo is a true ERP system designed for integrated process management, offering deeper customization and scalability for complex workflows. Zoho One is a strong contender for businesses needing a broad set of integrated tools at an attractive price point, but it may lack the depth of an ERP.

Key Differentiators for Odoo:

Open-Source Advantage: Offers unparalleled flexibility, transparency, and a vibrant community for support and development.
Cost-Effectiveness: The Community edition is free, and the Enterprise edition is generally more affordable than comparable proprietary solutions.
Modularity & Scalability: Allows businesses to grow into the system, adding modules as needed.
Customization: Highly customizable to fit unique business processes.
Integration: Designed for seamless integration between its own modules, and with external systems.

The Odoo Learning Curve

While Odoo boasts a user-friendly interface for basic operations, mastering its full potential requires dedication. The learning curve can vary significantly depending on the user's technical aptitude, the complexity of the desired implementation, and the specific modules being utilized.

Common Challenges:

Initial Setup and Configuration: Setting up Odoo to perfectly align with specific business workflows can be intricate, requiring a clear understanding of business processes and Odoo's capabilities.
Customization Complexity: While highly customizable, deep customizations often require technical expertise in Python and Odoo's XML-based development framework.
Varying Quality of Third-Party Apps: The Odoo App Store offers a plethora of third-party modules, but their quality and compatibility can vary.
Understanding Business Flows: Users need to understand how different modules interact and how data flows through the system to leverage Odoo effectively.

Advantages that Ease the Learning:

Intuitive User Interface: Odoo's modern and clean interface makes basic navigation and data entry relatively straightforward.
Modularity: Users can learn one module at a time, gradually expanding their knowledge.
Comprehensive Documentation: Odoo provides extensive official documentation and guides.
Vibrant Community Support: A large and active community offers forums, discussions, and shared solutions.
Online Resources: Numerous tutorials, videos, and blogs are available from both Odoo and third-party experts.
Scalability: The ability to start with core modules and gradually expand reduces the initial learning burden.

Odoo Learning Resources

To navigate the Odoo learning curve effectively, a wealth of resources is available:

Official Odoo Documentation: Comprehensive guides covering installation, configuration, and module functionalities.
Odoo eLearning and Certifications: Odoo offers official training programs and certifications for various roles (functional, technical).
Odoo Community Forum: An active platform where users and developers can ask questions, share knowledge, and find solutions.
Odoo YouTube Channel: Provides video tutorials and demonstrations of various features.
GitHub Repository: For developers, the source code is available on GitHub, allowing for deeper understanding and contributions.
Third-Party Blogs and Tutorials: Many Odoo partners and enthusiasts publish helpful articles, how-to guides, and video series.
Odoo Partners and Consultants: For businesses seeking professional assistance, Odoo partners offer implementation, customization, and training services.

Conclusion

Odoo stands as a compelling solution for businesses looking to unify and optimize their operations. Its open-source nature, modular design, and comprehensive suite of applications provide unparalleled flexibility and cost-effectiveness. While the learning curve requires dedication, the extensive array of available resources, coupled with a supportive community, makes mastering Odoo an achievable goal. By embracing Odoo, companies can unlock significant business potential, fostering greater efficiency, collaboration, and informed decision-making in the digital age.

Tricks for Efficient Odoo Development

Abraham — Thu, 19 Dec 2024 15:51:13 +0000

Developing custom modules, widgets, or features in Odoo can be streamlined with the right tools and techniques. Here are some proven tricks that can make your development process more efficient and insightful:

Use the Search Feature in VSCode

When working on Odoo development, the search functionality in VSCode or Other IDE can be invaluable for exploring the source code and understanding how things work under the hood.

Tips:

Activate Debug Mode
- Use Odoo's debug mode to identify key information such as IDs, record names, or registry keys.
Search the Source Code
- Search for relevant keywords in the source code to locate models, view IDs, or registry names.
- For instance, if you're working on a custom widget, you can refer to existing widgets as examples.

Example:
Suppose you're developing a custom widget. To learn from the color widget, you can search for the following code in VSCode:

category("fields").add("color"

This search will reveal the implementation of the color widget, allowing you to understand its structure and apply similar techniques to your widget.

Use ChatGPT or Other Large Language Models (LLMs)

LLMs like ChatGPT are powerful tools for Odoo developers, offering quick guidance and examples to solve problems or implement new features.

How to Leverage LLMs:

Ask for sample code snippets or explanations for a feature you're trying to build.
Use the responses as a reference or starting point for your implementation.

Example:
When building a feature to search for customers by phone number, you might receive a snippet like this:

from odoo import models, fields, api

class ResPartner(models.Model):
    _inherit = 'res.partner'

    @api.model
    def name_search(self, name, args=None, operator='ilike', limit=100):
        args = args or []
        if name:
            partners = self.search([
                '|', '|',
                ('name', operator, name),
                ('phone', operator, name),
                ('mobile', operator, name)
            ] + args, limit=limit)
        else:
            partners = self.search(args, limit=limit)
        return partners.name_get()

Then while exploring, you might realize that Odoo uses _name_search instead of name_search. This insight, combined with LLM guidance, significantly speeds up development.

Learn from Webs and Forums

Online resources like the Odoo forums or dedicated blogs (e.g., Cybrosys) are treasure troves of knowledge. These platforms provide:

Real-world solutions to common problems.
Tutorials for building a strong foundation in custom module development.
Insights into debugging and performance optimization.

Read Logs for Debugging

Logs are a developer’s best friend when identifying and fixing issues in custom modules. Odoo provides logs for the user, the logs path can be seen from the odoo.conf.

Tips for Reading Logs:

QWeb and JavaScript Issues
- Errors in QWeb templates or JavaScript will typically appear in the browser’s developer console.
Python Errors
- Check the logs file to identify backend issues like missing fields or incorrect method calls.

By analyzing logs, you can pinpoint errors quickly, reducing debugging time and effort.

Explore and Replicate Existing Features

Rather than starting from scratch, study how similar features are implemented in the Odoo source code.

Search for widget implementations, controllers, or method overrides.
Modify existing patterns to suit your custom requirements.

By combining these techniques, you can navigate Odoo’s complexities with ease, build robust customizations, and enhance your development workflow.

Odoo17: Installation Docker

Abraham — Mon, 02 Sep 2024 15:50:21 +0000

Introduction

Hello Everyone, I want to share with you guys about my experience in Odoo Development. In this article i will specifically share about the installation process for odoo17 in docker so we doesn't need to install too much dependencies.

Advantage and disadvantages using odoo docker

Advantage:

Simple installation progress.

Without docker we need to install a lot of dependencies, setting user, etc.

Disadvatage:

Hard to change the dependencies.

In docker it is hard for us to change the dependencies. For example in Odoo 17.0 docker version it uses wkhtmltopdf v0.12.6 but it has bug where the header for invoice is invisible So we must downgrade it to wkhtmltopdf v0.12.5.

Create the docker compose file

First we need to create the compose.yml file in the root folder. We need to first configure the odoo docker image version according to available versions from this documentation. In this tutorial I am using odoo:17.0 and make the odoo forward the port to 10017. Because Odoo is using postgreSQL as their db we can also add postgre db to the compose file.

Here is the example compose.yml code:

version: '3.1'
services:
  web:
    image: odoo:17.0 # Configure docker image version
    user: root
    depends_on:
      - db
    tty: true
    ports:
      - "10017:8069"
    volumes: # Configure Volumes
      - ./logs:/etc/odoo-logs/
      - ./config:/etc/odoo/ # Odoo Config Path
      - ./odoo_github/addon_custom:/mnt/extra-addons
    environment:
      - HOST=db
      - USER=odoo
      - PASSWORD=strongpassword # Should be the same as PG DB
  db:
    image: postgres:16
    environment: # Configure DB
      - POSTGRES_USER=odoo
      - POSTGRES_PASSWORD=strongpassword
      - POSTGRES_DB=postgres
      - PGDATA=/var/lib/postgresql/data/pgdata
    ports:
      - "5432:5432"
    volumes:
      - odoo-db-data:/var/lib/postgresql/data/pgdata
volumes:
  odoo-web-data:
  odoo-db-data:

Create the `odoo.conf` File

We should also create the odoo.conf file for odoo configuration. For the conf file location should be placed according to the compose file, if you follow this tutorial the location will be on config/odoo.conf. This file is used to configure the Odoo setting for example the master password, odoo app port, addons path, log path, etc. For more information about odoo configuration file you can check this out.

Here is the example odoo.conf:

[options]
data_dir = /etc/odoo
admin_passwd = easypassword

dev_mode = reload

xmlrpc_port = 8069

logfile = /etc/odoo-logs/odoo-server.log
addons_path = /mnt/extra-addons

Running the docker

To run the docker we can simply run the code below.

docker compose up -d

After running the docker you can go to the browser and enter http://localhost:10017. If everything is okay you should be able to see this page below.

Project Path

Below is the project path for this entire tutorial.

root
|
├── compose.yml
|
├── config
|    └── odoo.conf
|
└── logs
     └── odoo-server.log

Final words

This is the end of odoo docker installation tutorial. If you want the git code base you can get it here. I will continue the tutorial in the next article about getting started in odoo.

Forem: Abraham

Odoo Docker fix print bug

The Problem

Broken PDF example:

The Solution

Fixed PDF

Odoo Developer 101: OOP

OOP Definitions

OOP in Odoo

Advantages of OOP in Odoo

1. Modularity & Maintainability

2. Inheritance (Blueprint Functionality)

3. Overriding

4. Method Extension

Closing

Odoo 101: View

📁 1. How to Create a View

🔹 View Directory Structure

🔹 Define XML View

🔹 Register View in Manifest

🧭 2. Menu Items and Submenus

⚙️ 3. Actions and View Types (act_window)

👓 4. View Types in Odoo

📄 tree (List View)

📝 form

🧱 kanban

🔍 search

🎛️ 5. Widgets

🔁 6. Inheritance from Other Module

🧩 7. QWeb Sneak Peek (Teaser)

✅ Final Tips

Odoo CE: Automatic Inventory Valuation

What is Odoo Automatic Inventory Valuation?

How to Enable Automatic Inventory Valuation in Odoo Community

Step-by-step Instructions

Additional Notes

Conclusion

Odoo 101: Create a Module

Introduction

Creating a new module

Final Words

Odoo Introduction

Unlocking Business Potential: A Comprehensive Introduction to Odoo

What is Odoo?

Key Features and Modules

Odoo in Comparison: Standing Against the Giants

The Odoo Learning Curve

Odoo Learning Resources

Conclusion

Tricks for Efficient Odoo Development

Use the Search Feature in VSCode

Tips:

Use ChatGPT or Other Large Language Models (LLMs)

Learn from Webs and Forums

Read Logs for Debugging

Explore and Replicate Existing Features

Odoo17: Installation Docker

Introduction

Advantage and disadvantages using odoo docker

Advantage:

Disadvatage:

Create the docker compose file

Create the odoo.conf File

Running the docker

Project Path

Final words

⚙️ 3. Actions and View Types (`act_window`)

Create the `odoo.conf` File