Subject: How to build Nextcloud server zip from source like official release to fix Collabora integration issues?
Post:
Hi Nextcloud community,
I’m currently working on building a custom Nextcloud server package from the official Nextcloud server GitHub repo, because we want to apply our own changes and work on a multi-tenant architecture.
What I did:
- Cloned the official Nextcloud server repo and installed Nextcloud from the source.
- Configured Collabora Online correctly, but encountered an issue where files are downloaded directly instead of opening in Collabora.
- Verified network packets and noticed that clicking on a file triggers a direct download link instead of opening in Collabora.
- Tested the exact same Collabora setup with the official Nextcloud Docker image and the official Nextcloud zip package, and it worked perfectly.
- This confirms that the problem is with the Nextcloud installation built directly from the cloned repo source, not with Collabora or our configuration.
- Our team’s changes applied to the official zip package work fine, so our custom code is not the problem.
What I need help with:
- How does the Nextcloud team build the official zip release from the source code?
- Is there a recommended way or script to build a Nextcloud server zip package from the GitHub repo that ensures all integrations (like Collabora) work as expected?
- Are there any build steps or packaging tasks I might be missing which affect the proper working of Collabora in the built version?
- Any advice on best practices for building Nextcloud from source for production use, especially with custom modifications and multi-tenant setups?
Any pointers, scripts, or documentation references would be highly appreciated!
Thanks in advance!