Create Odoo 18 configuration

Author: m3r3nix

.devcontainer/Dockerfile

@@ -1,4 +1,4 @@
-FROM ubuntu:jammy
+FROM ubuntu:noble
 MAINTAINER Odoo S.A. <[email protected]>
 
 SHELL ["/bin/bash", "-xo", "pipefail", "-c"]
@@ -17,7 +17,6 @@ RUN apt-get update && \
         curl \
         dirmngr \
         fonts-noto-cjk \
-        git \
         gnupg \
         libssl-dev \
         node-less \
@@ -53,7 +52,7 @@ RUN apt-get update && \
     && rm -rf /var/lib/apt/lists/* wkhtmltox.deb
 
 # Install latest postgresql-client
-RUN echo 'deb http://apt.postgresql.org/pub/repos/apt/ jammy-pgdg main' > /etc/apt/sources.list.d/pgdg.list \
+RUN echo 'deb http://apt.postgresql.org/pub/repos/apt/ noble-pgdg main' > /etc/apt/sources.list.d/pgdg.list \
     && GNUPGHOME="$(mktemp -d)" \
     && export GNUPGHOME \
     && repokey='B97B0AFCAA1A47F044F244A07FCC7D46ACCC4CF8' \

.devcontainer/URL.conf

@@ -1 +1 @@
-https://nightly.odoo.com/17.0/nightly/deb/odoo_17.0.latest_all.deb
+https://nightly.odoo.com/18.0/nightly/deb/odoo_18.0.latest_all.deb

.devcontainer/devcontainer.json

@@ -5,7 +5,7 @@
     "workspaceFolder": "/workspace/custom",
     "remoteUser": "root",
     "forwardPorts": [8069],
-    "postCreateCommand": "ln -s /workspace/.vscode /workspace/custom/.vscode || true",
+    "postCreateCommand": "[ \"$CODESPACES\" = \"true\" ] && ln -s /workspaces/${localWorkspaceFolderBasename}/.vscode /workspace/custom/.vscode || ([ -z \"$CODESPACES\" ] && ln -s /workspace/.vscode /workspace/custom/.vscode || true)",
     "shutdownAction": "stopCompose",
     "customizations": {
         "vscode": {

.devcontainer/docker-compose.yml

@@ -1,6 +1,6 @@
 services:
   odoo:
-    image: "ghcr.io/m3r3nix/odoo-v17-community:latest"
+    image: "ghcr.io/m3r3nix/odoo-v18-community:latest"
     depends_on:
       - db
     ports:
@@ -9,7 +9,7 @@ services:
       - ../:/workspace
       - ../custom:/mnt/extra-addons
   db:
-    image: postgres:15
+    image: postgres:16
     environment:
       - POSTGRES_DB=postgres
       - POSTGRES_PASSWORD=odoo

.vscode/tasks.json

@@ -7,6 +7,12 @@
             "label": "Odoo Server Log",
             "type": "shell",
             "command": "tail -f /var/log/odoo/odoo-server.log",
+            "problemMatcher": [],
+            "isBackground": true,
+            "presentation": {
+              "reveal": "always",
+              "panel": "dedicated"
+            }
         }
     ]
 }

README.md

@@ -1,12 +1,12 @@
-[![Build and Push Odoo Dev Container](https://github.com/m3r3nix/odoo-dev-container/actions/workflows/docker-publish.yml/badge.svg?branch=v17)](https://github.com/m3r3nix/odoo-dev-container/actions/workflows/docker-publish.yml)
+[![Build and Push Odoo Dev Container](https://github.com/m3r3nix/odoo-dev-container/actions/workflows/docker-publish.yml/badge.svg?branch=v18)](https://github.com/m3r3nix/odoo-dev-container/actions/workflows/docker-publish.yml)
 
-# Odoo Development Container for GitHub Codespaces
+# Odoo Development Container for GitHub Codespaces and Visual Studio Code on Desktop
 
-You can spin up a development-ready environment in just 4 simple steps:
+Spin up a development-ready environment in just 4 simple steps:
 1. Fork this repository or use it as a template and make it private (particularly if you intend to work with the Enterprise Edition).  
    Ensure that during this process, all branches are copied, not just the default one, if you aim to work with older Odoo versions as well.
 2. Go to GitHub Actions and wait for all build processes to complete successfully. (Should you encounter any issues, please refer to the `Troubleshooting` section.)
-3. Select the branch corresponding to the Odoo version you wish to develop for and initiate a Codespace. (First boot takes about 2 mins.)  
+3. Select the branch corresponding to the Odoo version you wish to develop for and initiate a Codespace. (The first boot takes about 2 minutes, be patient)  
     NOTE: If your work involves the Enterprise Edition, please adhere to the instructions in `Create/Update an Enterprise based image`.
 4. Within the new VS Code instance, select the `Ports` tab. Then, right-click on port `8069` and choose `Open in Browser`. It will launch your new Odoo instance in your web browser.
 
@@ -15,39 +15,39 @@ You can spin up a development-ready environment in just 4 simple steps:
 - Your custom addons must be located in the `/custom` directory of the repository. However, within the Codespaces VS Code editor, this directory will serve as your root folder. See `estate-demo-addon`.
 - The build action is triggered by any change to the `.devcontainer/URL.conf` file. However, if you already have the latest Community URL in place and simply need a new build based on the most recent `latest_all.deb` package, you can go to GitHub Actions and trigger the action manually.
 - After forking this repository, update the GitHub Actions Badge URL at the top of the `README.md` file to reflect your own build processes. Otherwise, it will always display `no status`.
-- Images are tagged not only with `latest` but also with the version number of the downloaded Debian Odoo installer package. This approach allows you to spin up a Codespace with a previous build version in case the latest Odoo version has a serious bug. Simply select an image, for example, `odoo-v17-community`, and look for available tags like `17.0.20240202` in your Container Registry. Then, adjust the tag in `docker-compose.yml` accordingly.
+- Images are tagged not only with `latest` but also with the version number of the downloaded Debian Odoo installer package. This approach allows you to spin up a Codespace with a previous build version in case the latest Odoo version has a serious bug. Simply select an image, for example, `odoo-v18-community`, and look for available tags like `18.0.20240202` in your Container Registry. Then, adjust the tag in `docker-compose.yml` accordingly.
 
 ## How to create/update the development Docker image?
 
 ### Create/Update a Community based image
 
 1. Update the current URL in `.devcontainer/URL.conf` to the latest Community version:  
-    <https://nightly.odoo.com/17.0/nightly/deb/odoo_17.0.latest_all.deb>  
+    <https://nightly.odoo.com/18.0/nightly/deb/odoo_18.0.latest_all.deb>  
     Alternatively, select a specific build date from the following link and insert its corresponding URL into the file:  
-    <https://nightly.odoo.com/17.0/nightly/deb>
-2. If required, update the image name/tag in the `docker-compose.yml` file accordingly, for example `odoo-v17-community:latest`.
+    <https://nightly.odoo.com/18.0/nightly/deb>
+2. If required, update the image name/tag in the `docker-compose.yml` file accordingly, for example `odoo-v18-community:latest`.
 3. Commit and push your changes. This will automatically trigger a new build for the Docker image in GitHub Actions.
 4. Look for any errors in the build process. If it's green, then we are fine, you can open a Codespace.
 
 ### Create/Update an Enterprise based image
 
 1. Obtain the download link for the latest Odoo Enterprise Debian installation package:  
     <https://www.odoo.com/page/download>  
-    After providing your Odoo Enterprise subscription code, a new page will appear.  
+    After filling the form, click on Download (Ubuntu/Debian) and a "Congratulations! The download is starting" page will appear.  
     Right-click on `Click here` and select `Copy link` from your browser's dropdown menu.  
     This will give you a temporary download link, valid for approximately 30 minutes.   
 2. Replace the URL in `.devcontainer/URL.conf` with the new one you have copied to the clipboard.
-3. If required, update the image name/tag in the `docker-compose.yml` file accordingly, for example `odoo-v17-enterprise:latest`.
+3. If required, update the image name/tag in the `docker-compose.yml` file accordingly, for example `odoo-v18-enterprise:latest`.
 4. Commit and push your changes. This will automatically trigger a new build for the Docker image in GitHub Actions.
 5. Look for any errors in the build process. If it's green, then we are fine, you can open a Codespace.
 
 ## In case of a new Odoo main release
 
-1. The default branch should always contain the latest version. Therefore, create a new branch named after the latest version (e.g., `v18`) before making any changes.
+1. The default branch should always contain the latest version. Therefore, create a new branch named after the latest version (e.g., `v19`) before making any changes.
 2. Update the `Dockerfile` to reflect the current version from the official repository: <https://github.com/odoo/docker>
 3. Attempt to build it and check for any errors.
 4. Change the image tag in `docker-compose.yml` if necessary.
-5. Update demo addon version number
+5. Update demo addon version number in manifest.py
 6. Update README.md
 
 ## Possible improvements
@@ -65,11 +65,11 @@ You can create a pre-built Codespace template to speed up the initial boot proce
 ## Troubleshooting
 
 - Forking the repository initiates a build process for all available Odoo versions simultaneously. Due to these parallel builds, the GitHub Container Registry might face permission limitations. If this occurs, wait until all builds are complete. Then, identify any failed build and select `Re-run failed job`.
-- If you're forking or using this repository as a template more than once, you may encounter a permission issue during the docker image push process. This typically happens because an image with the same name (e.g. `odoo-v17-community`) already exists in your Container Registry, created by a different repository, which means the new repository lacks rights to update the image.  
-  `Error: buildx failed with: ERROR: failed to solve: failed to push ghcr.io/YOURNAME/odoo-v17-community:17.0.20240202: unexpected status from POST request to https://ghcr.io/v2/YOURNAME/odoo-v17-community/blobs/uploads/: 403 Forbidden`  
+- If you're forking or using this repository as a template more than once, you may encounter a permission issue during the docker image push process. This typically happens because an image with the same name (e.g. `odoo-v18-community`) already exists in your Container Registry, created by a different repository, which means the new repository lacks rights to update the image.  
+  `Error: buildx failed with: ERROR: failed to solve: failed to push ghcr.io/YOURNAME/odoo-v18-community:18.0.20240202: unexpected status from POST request to https://ghcr.io/v2/YOURNAME/odoo-v18-community/blobs/uploads/: 403 Forbidden`  
   To resolve this issue:
   - Navigate to `Packages` and remove the search filter to display all available images in your Container Registry.
-  - Select `odoo-v17-community`, proceed to `Package settings`, and under `Manage Actions access`, add your current repository with write access.
+  - Select `odoo-v18-community`, proceed to `Package settings`, and under `Manage Actions access`, add your current repository with write access.
   - Afterwards, re-run the failed job.
 
 ## More info and credits

custom/estate-demo-addon/__manifest__.py

@@ -3,7 +3,7 @@
     "depends": [
         "base",
     ],
-    "version": "17.0.0.1",
+    "version": "18.0.0.1",
     "application": "True",
     "category": "Sales",
     "description": "Manage real estate offerings",

custom/estate-demo-addon/models/estate_property.py

@@ -6,22 +6,23 @@ class EstateProperty(models.Model):
     _description = "Real Estate Property details"
 
     name = fields.Char('Name', required=True)
-    description = fields.Text()
-    postcode = fields.Char()
-    date_availability = fields.Date(default=fields.Date.today() + relativedelta(months=3), copy=False)
-    expected_price = fields.Float(required=True)
-    selling_price = fields.Float(readonly=True, copy=False)
-    bedrooms = fields.Integer(default=2)
-    living_area = fields.Integer()
-    facades = fields.Integer()
-    garage = fields.Boolean()
-    garden = fields.Boolean()
-    garden_area = fields.Integer()
+    description = fields.Text('Description')
+    postcode = fields.Char('Postcode')
+    date_availability = fields.Date('Available From', default=fields.Date.today() + relativedelta(months=3), copy=False)
+    expected_price = fields.Float('Expected Price', required=True)
+    selling_price = fields.Float('Selling Price', readonly=True, copy=False)
+    bedrooms = fields.Integer('Bedrooms', default=2)
+    living_area = fields.Integer('Living Area (m²)')
+    facades = fields.Integer('Facades')
+    garage = fields.Boolean('Garage')
+    garden = fields.Boolean('Garden')
+    garden_area = fields.Integer('Garden Area (m²)')
     garden_orientation = fields.Selection(
-        string='Orientation',
+        string='Garden Orientation',
         selection=[('north', 'North'),('south', 'South'),('east', 'East'),('west', 'West')])
     state = fields.Selection(
         string='Status',
         selection=[('new', 'New'), ('offer_received', 'Offer Received'), ('offer_accepted', 'Offer Accepted'), ('sold', 'Sold'), ('canceled', 'Canceled')],
         default='new')
     active = fields.Boolean(default=True)
+    

custom/estate-demo-addon/views/estate_property_views.xml

@@ -3,6 +3,84 @@
     <record id="properties_model_action" model="ir.actions.act_window">
         <field name="name">Properties</field>
         <field name="res_model">estate.property</field>
-        <field name="view_mode">tree,form</field>
+        <field name="view_mode">list,form</field>
     </record>
+
+    <record id="property_view_list" model="ir.ui.view">
+        <field name="name">estate.property.list</field>
+        <field name="model">estate.property</field>
+        <field name="arch" type="xml">
+            <list string="Properties">
+                <field name="name"/>
+                <field name="postcode"/>
+                <field name="bedrooms"/>
+                <field name="living_area"/>
+                <field name="expected_price"/>
+                <field name="selling_price"/>
+                <field name="date_availability"/>
+            </list>
+        </field>
+    </record>
+
+    <record id="property_view_form" model="ir.ui.view">
+        <field name="name">estate.property.form</field>
+        <field name="model">estate.property</field>
+        <field name="arch" type="xml">
+            <form string="Property">
+                <sheet>
+                    <div class="oe_title">
+                        <h1 class="mb32">
+                            <field name="name" placeholder="Expensive" class="mb16"/>
+                        </h1>
+                    </div>
+                    <group>
+                        <group>
+                            <field name="postcode"/>
+                            <field name="date_availability"/>
+                        </group>
+                        <group>
+                            <field name="expected_price"/>
+                            <field name="selling_price"/>
+                        </group>
+                    </group>
+                    <notebook>
+                        <page string="Description">
+                            <group>
+                                <group>
+                                    <field name="description"/>
+                                    <field name="bedrooms"/>
+                                    <field name="living_area"/>
+                                    <field name="facades"/>
+                                    <field name="garage"/>
+                                    <field name="garden"/>
+                                    <field name="garden_area"/>
+                                    <field name="garden_orientation"/>
+                                </group>
+                            </group>
+                        </page>
+                    </notebook>
+                </sheet>
+            </form>
+        </field>
+    </record>
+
+    <record id="property_view_search" model="ir.ui.view">
+        <field name="name">estate.property.search</field>
+        <field name="model">estate.property</field>
+        <field name="arch" type="xml">
+            <search string="Properties">
+                <field name="name"/>
+                <field name="postcode"/>
+                <field name="expected_price"/>
+                <field name="bedrooms"/>
+                <field name="living_area"/>
+                <field name="facades"/>
+                <filter string="Available" name="available" domain="['|',('state','=','new'), ('state', '=', 'offer_received')]" help="Properties available for sale"/>
+                <group expand="1" string="Group By">
+                    <filter string="Postcode" name="postcode" context="{'group_by':'postcode'}"/>
+                </group>
+            </search>
+        </field>
+    </record>
+
 </odoo>