4 ms·

I can vouch for Odoo and its Builder module. Odoo itself is open source, but there's a paid support model. We implemented an open source version for one of my c

I can vouch for Odoo and its Builder module. Odoo itself is open source, but there's a paid support model. We implemented an open source version for one of my clients and for business/production/inventory/accounting I'd say it's second to none. The free modules cover maybe 90% of common business cases, and the 10% left can be handled by duplicating one of the free modules and customizing it in Builder. Odoo is actively updated by large team in Belgium if I remember correctly, and their paid support is quite good. Odoo is Python atop Postgres, and uses a simple HTML/CSS/js for the frontend. Quite customizable, and can be a no-code solution if one uses Builder, which covers most use cases.

sirwitti 5y ago
Slighlty offtopic: Having shipped an Odoo project this year, how is the developer experience for you? It seems like Odoo forces developers into time consuming and frustrating workflows (for example using xpath + upgrade modules + possibly reload the server) that make developing for it a pain. Or I might be missing something?
- the_angry_angel 5y ago
  You are missing stuff. In development mode with inotify you get python hot code reloading. In development mode the XML (with a handful of exceptions regarding menus, and ir.actions) will be read from disk on refresh. At work we use Dockerized Odoo based on a [Doodba](https://github.com/Tecnativa/doodba https://github.com/Tecnativa/doodba). We use [click-odoo](https://github.com/acsone/click-odoo https://github.com/acsone/click-odoo) to manage module upgrades (amongst other things). Dev workflow is largely managed through [invoke](https://www.pyinvoke.org/ https://www.pyinvoke.org/) tasks. I do wish there was hot code reloading for the views (xml), but realistically if you’re making an app of any complexity the views in the backend are the small part and likely not where you are spending the majority of your time. Website stuff is absolutely 100% stuck in the past at the moment, imho.
  - sirwitti 5y ago
    Thank you! I will check these out!

sirwitti 5y ago

Slighlty offtopic: Having shipped an Odoo project this year, how is the developer experience for you? It seems like Odoo forces developers into time consuming and frustrating workflows (for example using xpath + upgrade modules + possibly reload the server) that make developing for it a pain. Or I might be missing something?

the_angry_angel 5y ago
You are missing stuff. In development mode with inotify you get python hot code reloading. In development mode the XML (with a handful of exceptions regarding menus, and ir.actions) will be read from disk on refresh. At work we use Dockerized Odoo based on a [Doodba](https://github.com/Tecnativa/doodba https://github.com/Tecnativa/doodba). We use [click-odoo](https://github.com/acsone/click-odoo https://github.com/acsone/click-odoo) to manage module upgrades (amongst other things). Dev workflow is largely managed through [invoke](https://www.pyinvoke.org/ https://www.pyinvoke.org/) tasks. I do wish there was hot code reloading for the views (xml), but realistically if you’re making an app of any complexity the views in the backend are the small part and likely not where you are spending the majority of your time. Website stuff is absolutely 100% stuck in the past at the moment, imho.
- sirwitti 5y ago
  Thank you! I will check these out!