-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support FreeBSD #79
Comments
I'm willing to do some work on this. @oparoz (or anyone else for that matter) have you put much time into getting this to build? I personally only care about the server side, but getting the client to build would be awesome too. |
That would be great @beatgammit ! |
Some news on this ? |
Has there been any movement on this, everyone over at FreeNAS would be really happy. |
@ideal2545 Sorry, currently this is not a high priority task, so no any major progress |
I haven't had time to dig in, and I'll be using LibreOffice in the short term, so I'm likely not going to look at it anytime soon. I'm still interested though. |
I spent many hours trying to only compile the DocumentServer part of OnlyOffice. I would very happy to try to get it fully compiling and working natively and to send patches if one of the author accepts to integrate this work.. |
@Teetoow Hi, you can create PR with patches and if our dev team will approved them we'll merge them |
@ShockwaveNN then I'll try to find some time to do the job as soon as possible. |
@Teetoow Could you provide list of unmaintained packages or a way to know it? |
@ShockwaveNN I'll try to find it again. I was doing this work the last summer.. I didn't had time to continue the work.. In all cases I will retry the next summer (I won't have time before!) |
@ShockwaveNN I had trouble with PhantomJS (ariya/phantomjs#15344) |
@Teetoow As far as I remember PhantomJS used only in testing |
@Teetoow Also, latest commit in PhantomJS is 16 days ago, seems project is not unmaintained. Also I'm not sure how unmaintained nodejs project related with compilation on FreeBSD |
Does anybody have a full list of dependencies? It would be a good first step in order to determine what's actually needed. |
@tuxillo You can look at Dockerfile to determine that |
Ok so I tried to take some times to update my initial patch to the latest onlyoffice release. The core directory compiles without any trouble (I'll send the patch once everything will work). Since I don't really understand whether these packages are really needed for production or are needed for testing, I don't know what to do.. Maybe you can give me some hints or a solution to skip that part if it's for testing only? |
And everyone directly on FreeBSD :) |
Since the document server has 6 components (according to the README in the project root) I wonder if it would not be easier to bring each of those components together one by one, meaning one port, at least, for each one. |
Starting with core, the table below lists the common 3rd party software, although it will be outdated soon:
|
ok so all the documentserver compiles without any error with my Makefile, scripts and preprocessor modifications. The only trouble is that the v8 version of FreeBSD is too old (as @tuxillo mentioned) and compiling v8 under FreeBSD is just definitely too hard (first of all gclient/synth don't support FreeBSD)! The only idea I've got is to try to use the V8 version which comes with nodejs (which compiles perfectly under FreeBSD) and try to generate a shared library from it.. |
@tuxillo in order to not destroy the onlyoffice architecture source I think the best thing to do is to use the third party components brought with DocumentServer (except for v8 which is too hard to compile... and ICU since they are linked). |
@Teetoow if the goal is to just build DocumentServer in FreeBSD so that people can build themselves, then I guess it's okay just to use whatever comes with DS. However if the goal is to bring DS to freebsd ports, the process is going to need to be properly defined and split in parts to have a chance for it to be accepted. |
@tuxillo I understand. For the moment my only goal is to get DocumentServer running natively on FreeBSD without having a virtual machine running for that purpose (I unfortunately don't have enough time and FreeBSD ports knowledges for something else). But as I previously said this can only be achieved if a not-so-old v8 version can be compiled under FreeBSD.. As far as I understood and tried this is a VERY BIG deal.. (and managing an up-to-date v8 port for FreeBSD might be much harder than one for DocumentServer :s). |
Hi, Just a little message in order to let you know that I found a nice solution for the libv8 under FreeBSD (thanks to Fedora ^^) and now DocumentServer is compiling well! |
Almost everything is working well. I just encounter a bug in the x2t binary which returns 80 each time I finish to edit a file. Thus modifications cannot be submitted to nextcloud and are lost in the DocumentServer part somewhere.. Please find attached to this post the OnlyOffice DocumentServer patchs, a text file which describes the compilation and configuration steps for FreeBSD users and a patch of the FreeBSD www/node8 port in order to get the needed libv8. FreeBSD.txt |
@savegame I had to indicate the erlang-cookie with all other rabbitmq commands in the instructions in order to make it work. So, instead of using I used Now to learn how to setup Nginx as i only have experience with Apache. |
@MikaelUrankar Everything works if i manually change those lines to Is there any way to update the port to include these changes? Also, i'm trying to switch the onlyoffice service to https per the instructions on https://helpcenter.onlyoffice.com/installation/docs-community-https-linux.aspx but the file Is there a way to include this file in the next version of the port? In the meantime, do any of you know where can i find this |
I'll fix the path in the next port update. Keep in mind that the nginx conf files are installed as sample files and needs to be adjusted manually.
I don't know why it's missing, will look into it and update the port if it has some value.
It's available here https://github.com/ONLYOFFICE/document-server-package/blob/master/common/documentserver/nginx/ds-ssl.conf.tmpl.m4 You'll need to adjust a few variables. |
@MikaelUrankar |
@MikaelUrankar |
Good points! |
Can this be a little more explained? I'm can't see the package in jail. |
I fixed a few issues in the port. It'll be available in the pkg repo in a few days. |
I think that it's currently only in the main ports tree and not the quarterly one which you might have, it should be possible to switch to the main one on FreeBSD-stable but I'm still new to FreeBSD myself and learning more about it |
I suppose that there are some problems building the packages. Normally the logs of failed builds are sent to the port maintainer - mikael@FreeBSD.org. The logs should be analyzed to determine the source of failures. |
I've merged my fix to the quarterly branch. |
At https://www.freshports.org/www/onlyoffice-documentserver/ there are no builds... |
As I said, it'll take a few days for the package to be available. |
@MikaelUrankar is the a guide on how to set the server running? I've tried the steps after the installation but couldn't make it work. |
Do you have an error or something? |
It has to do more with the next steps after the installation, the addres only shows me the nginx welcome part and not the onlyoffice server. |
Can you send me your nginx configuration at my FreeBSD.org email address? |
There seem to be no updates in freshports |
It builds perfectly fine on my machine :) |
Not there though, so package is no longer available. Judging by logs it seem to compile, but not linking. |
Linking seem to be failing in FreeBSD 13 both AMD64 and Aarch64. But succeeding in FreeBSD 14 and 15. |
Even after https://cgit.freebsd.org/ports/commit/?id=81ddc72fda1f56d86dd0f4166edeb1ac8e331a6e ? |
Probably no. Will see. Most recent build seem to take previous commit, although after new was committed. I guess next attempt is on Saturday? |
Are there any plans for 8.0+? |
And are there any plans for 8.1? |
It's on my todo list |
Or 8.2? |
done |
Do you want to request a feature or report a bug?
FR
What is the current behavior?
Too many linuxisms is the scripts + compilation of unnecessary components which are already available via the ports system
What is the expected behavior?
Autodetection of the BSD platform and compilation of
core
The text was updated successfully, but these errors were encountered: