xmysql VS saltcorn

How does this compare to NocoDB[0] which is already quite established?

[0]: https://github.com/nocodb/nocodb

But maybe something like nocodb would work for your needs.

Maybe you can use something like this https://github.com/nocodb/nocodb

📣   Github : https://github.com/nocodb/nocodb

I used to use FireflyIII as well and found the flexibility to be lacking just as you did. I've just started using Grist, although there is nocodb and baserow. Yes it's more spreadsheet like and sometimes more "hacky" but there will never be an out-of-the-box application that comes close to what, ostensibly, a spreadsheet like application is good at.

Nocodb: Open Source Airtable Alternative - turns any MySQL, Postgres database into a collaborative spreadsheet with REST APIs.

NocoDB then?

Also planning to check out NocoDB (Airtable/spreadsheet alternative): https://github.com/nocodb/nocodb

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