@polarathene go ahead and have a look :) I suggest you immediately apply feedback that you have 🚀

@beertje44 you can now already take a look at the preview we generate. Look out for comments from the github-actions bot, like this one.

Current preview of new docs page: https://pullrequest-4070--dms-doc-previews.netlify.app/examples/tutorials/dovecot-solr/

I have revised the PR a bit:

• There was some parts from earlier review that had not been addressed (notably naming convention from @casperklein and new line requirements from @georglauterbach ) , additionally some typos to correct.
• Other portions have been revised to be worded better, or restructured for better formatting for the reader to digest.
• Relevant links added for context. Especially the UID/GID reference.

There is no mention for the dovecot-solr package requirement. My understanding is that we are not bringing that back as it's missing support for ARM64 releases?

I'll add a new commit to advise on including the package and ARM64 caveat, then this should be good for merging.

Documentation preview for this PR is ready! 🎉

Built with commit: 4260233

Thanks everyone!

This guide seems to be missing some advice that was detailed by @erm967 in #4052 (comment) , is that not required for some reason?

I suspect that is one of the maintenance caveats to keep in mind as the external resource won't be tied to a specific DMS release (at least if this new doc page is not actively maintained across releases).

I've left the referenced feature request open, but I've also included a link on the new docs page for any interested users to express their interest in the package. I think we've covered why we no longer include the package and the workaround for Solr users is quite simple as covered in the docs.

Closing that feature request with this PR is acceptable. It can always be opened again in future if relevant.

Thanks everyone!

This guide seems to be missing some advice that was detailed by @erm967 in #4052 (comment) , is that not required for some reason?

I suspect that is one of the maintenance caveats to keep in mind as the external resource won't be tied to a specific DMS release (at least if this new doc page is not actively maintained across releases).

Simply including the right jars in a lib dir inside the solr core dir you have to create anyway is sufficient to make the dovecot schema work as is. Imho this is a better solution for most users then having to apply a patch that will change for every solr minor release. I've included a cp command in my tutorial.