Help test a new M³ version!

[mtdvlpr]

Dear users,

We are hard at work with a new version of M³. At the core of this new version is the migration of Nuxt 2 to Nuxt 3 which comes with a lot of under the hood improvements which you will mostly notice in the performance boost. This migration seemed like the perfect moment to completely review the current UI and revamp it. You can find a roadmap of this revamp here.

To migrate, every piece of code had to be rewritten, so to make sure that nothing breaks in the official release, we are going to release several test versions to ensure a smooth transition.

If you want to help with this process, we would very much appreciate it if you could take the time to use these test versions extensively and report back any questions, bugs or other useful information. You can find the latest test version here. The test version will automatically be updated, just like M³ itself. Anything related to this migration can be posted in this discussion.

Important notice: Although we've tested it ourselves, it remains a test version and therefore it's not advised to be used during actual meetings. You current M³ settings will be used in the test version and any settings you change in the test version, you also change in your own M³ instance. It is advised to create a new congregation for testing purposes to avoid messing with your own settings.

Thanks in advance for your efforts and willing spirits!

[e-Feitosa]

Is the project still receiving updates?
I stopped testing because the Koofr server was not working.

[sircharlo]

Yes, but we're mostly working on the refactored version. It's pretty functional at the moment but is still missing a few key features. Once those features are implemented, this version will be released (probably some time later this year).

As it stands, the WebDAV server integration is however on life support. We'll be switching to a different congregation synchronization methodology soon, as detailed here.
The change, once implemented, will mean that the actual congregation sync will no longer take place inside of M³, but rather be taken care of by whatever sync app you have set up on the computer (Dropbox/Google Drive/Box/Rclone/etc.)
This will simplify development greatly, as M³ will no longer be responsible for connecting to various sync providers that all work differently. M³ will simply apply whatever changes need to be made based on the contents of the synced folder to which it's pointed.

[e-Feitosa]

Thank you for the informations. Before using the koofr server, I already used Google Drive, I still keep it as a second option in case of failure of the current server, but some problems happen with Google Drive, for example: When sending media to a meeting, on KH's PC he often deletes everything in the folder and downloads the media (as I reported in another post), I believe this is because the M3 opens first than Google Drive. But I'm going to test ASAP those other options you mentioned. As a suggestion, if possible, I would leave this server option disabled, and anyone who wished could activate it, and would only kill the koofr server, if this was not going to take additional work.

[github-actions[bot]]

This discussion has automatically been closed due to inactivity.