I’m happy to announce that I successfully upgraded Moqui within growerp.com by simply applying the breaking changes outlined in the release documentation.
Thank you to everyone involved in this upgrade—great job!
Previously, I copied the entire Moqui system into the project. This time, I took the opportunity to switch to using a Git submodule instead. This approach is well supported in both the Antigravity and VS Code IDEs.
As a result, it’s now much easier to stay in sync with Moqui updates, and contributing back has become simpler as well. I’ve already submitted a small pull request to get started.
I was also expecting at least an announcement, but I didn’t see anything. I also managed to update successfuly and I want to thanks to all contributors who made it possible.
By the way Hans, I saw that you have a chat module in your grow erp based on the websockets in Moqui if I’m not wrong. Have you used that with a bunch of clients in production and is it reliable?
So the major work in moqui4 was mostly revolving around the code, which is thankfully out. But we still have work to update the documentation and website to catch up. We were discussing in community switching away from DB documentation into more source controlled documentation to ease contribution.
I was also thinking of a framework that is extensible so that documentation is spread across the different repos / components, instead of centralized, and then the build system would bring everything together. Naturally this stuff took time, as the bulk of moqui4 took me around 3 months or so.
Maybe also @michael has some input on this topic. But I think it’s just a matter of time before we get everything updated to catch up.