Please, prepare packages/ports of community edition (server) and desktop edition for FreeBSD.
do you mean CommunityServer and DesktopEditors? there is portable version of editors. is it suitable for you?
The most interesting thing is DesktopEditors.
The portable version is built for Linux x64, not for FreeBSD. Maybe, using Linux x64 compatibility layer it could be run on FreeBSD 11. Certainly, it does not work on FreeBSD 10.3 (my workstation), probably because x64 ELF files cannot be run on this version of FreeBSD. Anyway, using Linux binaries on FreeBSD stays tricky, it is not intended for end user. I don't think that recompiling OnlyOffice DesktopEditors for FreeBSD could be really difficult, as it seems that all the components are available on FreeBSD.
So, please, recompile it for FreeBSD.
Or do the work necessary to get it into the ports system.
I'll give my own input (sorry for dramatic presentation, I've had some unhappy hours trying to make it work):
I've encountered a pretty viable scenario when I needed CommunityServer on FreeBSD. Here's why:
Some could say "You've picked a bad OS - not OO problem".
My position is - "Would you like to get FreeNAS users - make it work in jail".
@GaroRobe I think your comment is misplaced, it should be in https://github.com/ONLYOFFICE/DocumentServer/issues/79 or new issue in https://github.com/ONLYOFFICE/CommunityServer/issues if you really mean CommunityServer, not DocumentServer
Any news on this?
@pixel8383 Sorry, no news
We need ONLYOFFICE for *BSD, please.
+1
The reason is simple: OnlyOffice conveys a higher degree of compatibility with an Microsoft Office that diverts more and more from the OpenDocument Standard, so in a mixed collaborative environment OnlyOffice is better suited to interact smoothly with Microsoft Office users than LibreOffice - as much as I love to use LibreOffice, too!
I spent many hours trying to only compile the DocumentServer part of onlyoffice.
It was nearly a success before I discovered that onlyoffice needs some node.js packages which are obsolete, unmaintained and thus unavailable for FreeBSD.
Before that I had to update tens and tens of source code files, Makefiles etc. in order to get it compiling.
This work is really boring and can't be finished until OnlyOffice uses still maintained external packages.
Moreover I can't believe that someone will accept to do this job each time a new release of OnlyOffice is out.
The only solution would be that OnlyOffice accepts these patches in order to natively support FreeBSD.
Last but not least I tried many ways in order to use the linux binaries into FreeBSD through the compat layer. It does not works.
At the end there is two solution:
Happy to see that someone is trying to build it.
I'm surprised to know that OnlyOffice uses unmaintained node.js packages. I think that you can open an issue about the subject, as unmaintained=insecure, and it is not really good for a web application.
IMHO, we cannot know if OnlyOffice accepts FreeBSD compatibility patches if nobody sends them ;)
Yeah you're right @Peter2121. I stopped trying to work on it because of a lack of time and these node.js problems. It was the last summer.. Now I had to redo the job from the beginning..
I also sent a feature request to DocumentServer authors. I'll see their answer.
I won't be able to try it again before this summer.. It's definitely a big job to do.
Or I hope that someone else will do it :)
Most helpful comment
I'll give my own input (sorry for dramatic presentation, I've had some unhappy hours trying to make it work):
I've encountered a pretty viable scenario when I needed CommunityServer on FreeBSD. Here's why:
Some could say "You've picked a bad OS - not OO problem".
My position is - "Would you like to get FreeNAS users - make it work in jail".