Odoo has invested a lot of time in the development of the Odoo.sh platform, and it is packed with features as a result. Let's have look at the features of Odoo.sh. Note that Odoo adds new features from time to time. In this section, I have mentioned the features that are available at the time of writing this book, but you might find some further features, as well:

• GitHub integration: This platform is fully integrated with GitHub. You can test every branch, pull, or commit here. For every new commit, a new branch will be pulled automatically. It will also run the automated test for the new commits. You can even create/merge branches from the Odoo.sh UI itself.
• Web shell: Odoo.sh provides the web shell in the browser for the current build (or production server). Here, you can see all the modules and logs.
• Web code editor: Just like the web shell, Odoo.sh provides the code editor in the browser. Here, you can access all of the source code and also get the Odoo interactive shell for the current build.
• External dependencies: You can install any Python packages. To do this, you just need to add requirement.txt in the root of your GitHub repository. Right now, you can only install the Python packages. It is not possible to install system packages (apt packages).
• Server logs: You can access the server log for each build from this browser. These logs are in real time and you can also filter the logs from here.
• Automated tests: Odoo.sh provides your own runbot, which you can use to perform a series of automated tests for your development. Whenever you add a new commit or a new development branch, Odoo.sh will automatically run all of the test cases and show the status of the test. You can access the full test log, which will help you find issues if a test case fails.
• Staging and development branches: Odoo.sh provides two types of branches: the development branch and the staging branch. In the development branch, you can test ongoing development with demonstration data. The staging branch is used when the development is finished and you want to test the feature before merging it into production. The staging branch does not load the demonstration data; instead, it uses a copy of the production server.
• Mail server: Odoo.sh automatically sets up a mail server for the production server. Just like Odoo online, Odoo.sh does not need any extra configuration for email, although it is possible to use your own mail server.
• Mail catcher: The staging branch uses a copy of your production database, so it has information about your real customers. Testing on such a database can make it possible to send emails to real customers. To avoid this issue, the email feature is only activated on production branches. Staging and development branches do not send real emails, but instead, they use a mail catcher so that you can test and see emails in the staging and development branch.
• Share the build: With Odoo.sh, you can share the development branches with your customer so they can test them before merging the feature into production.
• Faster deployment: As Odoo.sh is fully integrated with GitHub, you can merge and deploy the development branches directly from the browser with a simple drag and drop procedure.
• Backup and recovery: Odoo.sh keeps full backups for the production instance. You can download or restore any of these backups in just a few clicks. Refer to the Getting a backup of your instance recipe to learn more about backups.
• Community modules: You can test install any community module in a few simple clicks. You can also test free modules directly from the app store.