The document provides recommendations for configuring an Odoo cloud platform hosted on odoo.sh including recommended hardware resources based on number of users and visitors. It outlines the process for creating a project on odoo.sh including selecting the git repository, Odoo version, and hosting location. It also describes how to use different branches for development, staging, and production environments and the limitations of each. The document emphasizes using good git branch naming conventions and outlines some benefits of using Odoo like code flexibility and continuous integration. It concludes by inviting any questions.

1. Odoo.sh
Benjamin AKBOKA APENGU • Developer
For project managers and developers
2019
EXPERIENCE

2. The odoo cloud platform
Developer first
Thus a need for PMs to have some technical knowledge

3. How to configure odoo.sh?
● 1 worker per 25 users or
25000 daily visitors
● 1 GB for 1 users (except
for ecommerce)
● At least one staging
branch. More
explanation later

4. Create project
● Choose the git repository
● Choose odoo version
● Enter the subscription code
● Choose hosting location
Replace by example on sh

5. Credit : medium.com

6. Development Staging
Data Demo Production
Branches Unlimited Limited
Garbage collection All All but latest
Database import Impossible Possible
Tests All unit tests Only module tests

7. How to use them
A guide to testing on sh
Production -> production branch (example 13.0)
Staging -> master branch + ticket specific branch
Smaller project : staging only for task requiring production data
Bigger project : a branch per task
Development -> all the others

8. Having a good
nomenclature will help you
a lot
www.odoo.com

9. Conclusion.
● Use of git enable better maintainability
● Code flexibility
● Use of python instead of xml
● Continuous integration (Talk on Friday about testing)

10. Thank you.
#odooexperience
2018
Any questions?
2019
EXPERIENCE