Given on 02/12/2026, this presentation covers the basics of debugging remote Odoo databases using VS Code. This is useful when you want to figure out exactly what a customer's custom modules are doing without running any third-party code locally. It's also especially useful when we simply can't interact with a database locally without these custom modules, such as when their custom code is deeply coupled with the UI, preventing normal use of Odoo without them.
You can find the presentation slides and recording here:
- Slides: <TODO update after presentation has been given>
- Recording: <TODO update after presentation has been given>
To follow along with the slides, you should have the following configured before the presentation.
- VS Code installed (or one of its forks).
- The remote debugging launch configuration from this repo should be placed in the
.vscode/launch.jsonfile of your usual Odoo workspace.- Note the
"localroot"key is looking for yoursrcfolder; this is the folder where you keepodoo,enterprise, etc. Change the path as needed to match your local setup.
- Note the
- (Optional) Configure the
copyBash function fromcopy.example.bashto work on your machine.- You can just copy-and-paste that function into your
.bashrcfile and then editdestination_pathlocal variable.
- You can just copy-and-paste that function into your
- Trial SH database created for Odoo 19.0.
- If you are following along after this presentation has already happened, ask FSRS for a trial SH code to use while you work through these slides.
- Custom module from this repo uploaded to your trial SH DB.
- Install the Sales app and create a few, fun products 🙂
- This remote debugging process was adapted from VS Code's documentation. You'll notice similar uses of
debugpyand port forwarding: