saltcorn VS doodba

Shameless plug for Saltcorn (https://saltcorn.com), which is the simplest and open sourceiest way of creating a database web application for when you want an upgrade from Excel with proper table with fields and relationships. Data viz, pivot table plugins available.

If that is not enough and you need more structure, you could use a no-code solution. I am the author of Saltcorn, an open source no-code platform and happy to help with your project.

Hi, author of Saltcorn here. Free as can be (MIT license), full stack (front end, back end, automation).

That was a good read - liked the balance, and agree with his description of the ideal product, which is very close to mine.

I'd add the option of commercial hosting and support to that list, which led me to Budibase - great product, although in the end I was left feeling "no code - but so many clicks!", although I have not gone back to look at v2. https://budibase.com/

The author might care to take a look at Saltcorn, which is in the "Goldilocks" zone for me - enough of everything, not too much of anything. I should write that up myself. https://saltcorn.com/

This is the most important part. Otherwise you will replace an undocumented mess with another unstructured documentation mess in no time. A wiki is a great place to prototype documentation concepts, but it's hard to keep it consistent if no rules are enforced. For more structured documentation/information, tools like https://saltcorn.com/ may be even more helpful.

Saltcorn [1] is worth a look. The back-end is Postgres, so integrations are simple. It seems to work how my mind works, it's fun to use, and I don't feel limited or locked in because the data and model are in Postgres.

[1] https://saltcorn.com/

Why the snark? I see value in no-code/low-code platforms for many people—integrating with "traditional" code to fill in the lack of domain-specific features and starting a strong FOSS alternative early on is critical. I just started reading and found these two projects that seem to be trying to accomplish just that [1][2] though they seem very early. I would love to see what other insights HN has and what they think about a FOSS alternative's potential.

[1] https://github.com/saltcorn/saltcorn

When we started the Odoo official container was a bag of shit. We standardised on https://github.com/tecnativa/doodba as a base instead. It's bundled with a whole bunch of tools that are helpful, but it's really opinionated on workflow, and may not work for you. There are a number of partners who have similar variations (camptocamp for example have https://github.com/camptocamp/docker-odoo-project) which add more and more tools which are useful overtime.

Check out Doodba - https://github.com/Tecnativa/doodba - which supports stuff like this.

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 reload.

At work we use Dockerized Odoo based on a [Doodba](https://github.com/Tecnativa/doodba). We use [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/) 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.